2 Understanding ORFM Implementation Checklists

This chapter discusses the prerequisites required for implementing ORFM. It also provides a checklist for standard implementation and for legacy systems.

The following topics are covered in this chapter:

Prerequisites
Implementation Checklist for Legacy Systems
Implementation Checklist for Standard Systems

Prerequisites

Ensure the following prerequisites are met before you use the ORFM application:

If Taxweb is the Tax Engine, then make sure RMS, ORFM, RTIL, and TaxWeb Tax Rules are installed successfully.
If Synchro is the Tax Engine, then make sure RMS, ORFM, and Synchro Tax Rules are installed successfully.
RIB Adapters (formerly e-ways) – In case ORFM is integrated with SIM and RWMS, verify that the RIB adapters are up and running. RIB adapters ensure interface of schedule and shipment details between ORFM and RWMS/SIM. For more information, see the Oracle Retail Integration Bus documentation set, including Integration Guide.
Localization Flex Attributes setup (LFAS) - Set up the localization flexible attributes for a set of books, transfer entity, country, store, warehouse, supplier, outside locations, external finishers, and for the item-country combination. Localization Flex Attributes facilitate linking of fiscal attributes to respective entities. For more information, see the Oracle Retail Merchandising System with Brazil Localization Installation Guide.

Implementation Checklist for Legacy Systems

Use the following checklist before you implement ORFM in a legacy environment:

Run the data conversion script to load the data from the legacy system. For more information, see the Oracle Retail Merchandising Data Conversion Operations Guide.
Ensure that the following are populated with correct values before making the TaxWeb Tax Rules calls. The script transform_br_future_cost.ksh populates the FUTURE_COST table if there is no record in future cost table.
- FUTURE_COST table
- CURRENCY_RATES table are populated with the EFFECTIVE_DATE prior to the transaction date
Refresh the mv_currency_conversion_rates materialized view.

Run the scripts manually in the following order as shown in Table 2-1.

Table 2-1 Shell Scripts

Script	Function
l10n_br_seed_extax_setup_cost.ksh	This module reviews all the valid item/supplier/origin country/location combinations in RMS. It determines the unique fiscal attribute groups that cover all the item/supplier/origin country/location combinations and puts the groups on the stage tables, L10N_BR_T_EXTAX_STG_COST (for TaxWeb) and L10N_BR_S_EXTAX_STG_COST (for Synchro).
l10n_br_seed_extax_process_cost.ksh	This module picks up the staged groups placed on L10N_BR_T_EXTAX_STG_COST (for TaxWeb), and L10N_BR_S_EXTAX_STG_COST (for Synchro) by l10n_br_seed_extax_setup_cost.ksh and calls the external tax provider with them. The results of these calls are placed on the L10N_BR_T_EXTAX_RES_COST (for TaxWeb), L10N_BR_S_EXTAX_RES_COST (for Synchro), L10N_BR_T_EXTAX_RES_COST_DET (for TaxWeb), and L10N_BR_S_EXTAX_RES_COST_DET (for Synchro) tables.
l10n_br_seed_extax_finish_cost.ksh	This module picks up the group level tax call results that l10n_br_seed_extax_process_cost.ksh placed on L10N_BR_T_EXTAX_RES_COST (for TaxWeb), L10N_BR_S_EXTAX_RES_COST (for Synchro), L10N_BR_T_EXTAX_RES_COST_DET (for TaxWeb), and L10N_BR_S_EXTAX_RES_COST_DET (for Synchro) and explodes them back to the item/supplier/origin country/location level. It then uses the item/supplier/origin country/location level information to write tax information to ITEM_SUPP_COUNTRY, ITEM_SUPP_COUNTRY_LOC, FUTURE_COST, ITEM_COST_HEAD, and ITEM_COST_DETAIL.
l10n_br_seed_extax_setup_retail.ksh	This module reviews all the valid item/location combinations in RMS. It determines the unique fiscal attribute groups that cover all the item/locations combinations and puts the groups on a stage table (L10N_BR_T_EXTAX_STG_RETAIL).
l10n_br_seed_extax_process_retail.ksh	This module picks up the staged groups placed on L10N_BR_T_EXTAX_STG_RETAIL (for TaxWeb) and L10N_BR_S_EXTAX_STG_RETAIL (for Synchro) by l10n_br_seed_extax_setup_retail.ksh and calls the external tax provider with them. The results of these calls are placed on the L10N_BR_T_EXTAX_RES_RETAIL (for TaxWeb), L10N_BR_S_EXTAX_RES_RETAIL (for Synchro), L10N_BR_T_EXTAX_RES_RETAIL_DET (for TaxWeb), and L10N_BR_S_EXTAX_RES_RETAIL_DET (for Synchro) tables.
l10n_br_seed_extax_finish_retail.ksh	This module picks up the group level tax call results that l10n_br_seed_extax_process_retail.ksh placed on L10N_BR_T_EXTAX_RES_RETAIL (for TaxWeb), L10N_BR_S_EXTAX_RES_RETAIL (for Synchro), L10N_BR_T_EXTAX_RES_RETAIL_DET (for TaxWeb), and L10N_BR_S_EXTAX_RES_RETAIL_DET (for Synchro) and explodes them back to the item/location level. It then uses the item/location level information to write tax information to GTAX_ITEM_ROLLUP and POS_MODS_TAX_INFO.
l10n_br_seed_extax_future_cost.ksh	This module obtains a list of fiscal attributes that have tax law changes scheduled against them. It then uses this information to determine what item/supplier/origin country/locations will be affected by those scheduled tax law changes. These item/supplier/origin country/location combinations are then used to create new cost changes on the date of their tax law changes. The normal cost change processes will then take care of updating RMS with the new tax law information when necessary.
l10n_br_seed_extax_future_setup_retail.ksh	This module obtains a list of fiscal attributes that have tax law changes scheduled against them. It then uses this information to determine what item/locations will be affected by those scheduled tax law changes. It determines the unique fiscal attribute groups that cover those item/locations combinations and puts the groups on the stage tables, L10N_BR_T_EXTAX_STG_RETAIL (for TaxWeb) and L10N_BR_S_EXTAX_STG_RETAIL (for Synchro).
l10n_br_seed_extax_future_process_retail.ksh	This module picks up the staged groups placed on L10N_BR_T_EXTAX_STG_RETAIL (for TaxWeb) and L10N_BR_S_EXTAX_STG_RETAIL(for Synchro) by l10n_br_extax_stg_retail.ksh and calls the external tax provider with them. The results of these calls are placed on the L10N_BR_T_EXTAX_RES_RETAIL (for TaxWeb), L10N_BR_S_EXTAX_RES_RETAIL (for Synchro), L10N_BR_T_EXTAX_RES_RETAIL_DET (for TaxWeb), and L10N_BR_S_EXTAX_RES_RETAIL_DET (for Synchro) tables.
l10n_br_seed_extax_future_finish_retail.ksh	This module picks up the group level tax call results that l10n_br_seed_extax_future_process_retail.ksh placed on L10N_BR_T_EXTAX_RES_RETAIL (for TaxWeb), L10N_BR_S_EXTAX_RES_RETAIL (for Synchro), L10N_BR_T_EXTAX_RES_RETAIL_DET (for TaxWeb), L10N_BR_S_EXTAX_RES_RETAIL_DET (for Synchro) and explodes them back to the item/location level. It then uses the item/location level information to write tax information to GTAX_ITEM_ROLLUP and POS_MODS_TAX_INFO.
transform_br_country_attrib_final.ksh	This script updates the columns default_po_cost, default_deal_cost, and default_cost_comp_cost to NIC and updates the column item_cost_tax_incl_ind to Y for the country BR in the country_attrib table.
transform_br_upd_nic_cost_type.ksh	This script updates the unit cost to negotiated item cost (NIC) for the tables ITEM_SUPP_COUNTRY_LOC and ITEM_SUPP_COUNTRY. This script also updates the default_costing_type column of the future cost table to NIC.

Implementation Checklist for Standard Systems

Use the following checklist to implement ORFM in a standard environment:

RMS Security setup for ORFM - Finalize ORFM user roles. In ORFM, you can control access only at the menu level. ORFM uses the RMS security infrastructure to restrict access. For instance, one role could be set up with access rights to edit or view NF while another role can be set up to resolve any discrepancy on NF. For more information on setting up RMS security, see the Oracle Retail Merchandising System Operations Guide.
RMS System setup - Verify the following in RMS before using the ORFM application:
- s Base Country is set as BR for Brazil.
- RMS system option Currency Code is set as BRL.
- RMS system options the default_tax_type is set as GTAX to enable tax functionality.
- CREDIT_MEMO_LEVEL – Ensure that the CREDIT_MEMO_LEVEL in the system options table is set at location level 'L'. This system option indicates at what level the invoicing will happen for deals.
- RMS system options Allow Auto Shipping/Receiving at Store is not selected.
- All tax codes in the RMS VAT_CODES table are exactly the same as the tax codes set up in the TaxWeb Tax Rules. This enables better tax integration with merchandising system.
For more information, refer to the Oracle Retail RMS-ReSA User Guide for Brazil Localization.
Verify the following setup in RMS:
- The localization_ind indicator in the COUNTRY_ATTRIB table is set to Y for Brazil.
- The default location is set up for Brazil using the COUNTRY_ATTRIB table. The default location is set up after you create the first location and is most likely to be set as the location for which most of the purchases occur.
- In the COUNTRY_ATTRIB table, ensure the ITEM_COST_TAX_INCL_IND parameter is set to Y with the DEFAULT_DEAL_COST and the DEFAULT_COST_COMP_COST DEFAULT_PO_COST parameter to (NIC).
- The Flex field values are set to country BR. For the country BR, the fiscal attribute value should be 105.
- The Flex field values for all entities (Store, Warehouse, Supplier/Site, Partner, Outside Location, Transfer Entity, Set of Books) are set up appropriately.
RTIL URL and Server Configure – Capture valid RTIL URL details based on where it is deployed. Update the RMS RETAIL_SERVICE_REPORT_URL table with the URL for RS_CODE of RTIL. Supply a timeout value (the unit is in milliseconds) in the TIMEOUT column. You can arrive at this value in conjunction with the RIB timeouts configured at the customer premise. This value should be less than the configured RIB timeout.
RIB Adapters setup – Verify that the Schedule Submission adapter (ORFM Specific) and SO Status adapter (for transfers from RWMS or SIM) are up and running. This ensures that ORFM is successfully integrated with the external warehouse and store management systems.
Fiscal Information from the TaxWeb Tax Rules– Execute the fiscal download batch to obtain the various fiscal codes from the TaxWeb Tax Rules. The fiscal attributes provided by the TaxWeb Tax Rules are associated with master entities such as locations and suppliers in RMS. It is also used during transaction processing in ORFM. One of the fiscal codes is Nomenclatura Comum do Mercosul (NCM). Verify that following fiscal attributes are available in the system:
- NCM_CODES
- NCM_CHAR_CODES
- NCM_PAUTA_CODES
- NCM_IPI_CODES
- CNAE_CODES
- SERVICE CODES
- FEDERAL SERVICE CODES
- NOP Codes
- CEST Codes
Note:
The fiscal download (fisdnld) batch accepts any one of the parameters for instance, NCM, NCMCHAR, CEST and so on. You can also choose the parameter as 'ALL'.
Document Type setup – Set up the Document Type information in ORFM. The document type is meant to allow users to segregate NF sequencing that are associated to document types. It is in the document type setup where users can define the model type that corresponds to the codes defined by fiscal authorities in Brazil such as 55 for electronic NF, 65 for customer electronic NF and so on. You have to manually set up the required document types as per business definitions and associate them to one or more utilizations. ORFM requires mandatory association of a document type with a NF.

Utilization Codes setup – Set up the utilization codes for different transaction types in ORFM. Utilization codes control the NF processing logic. The utilization codes have to be captured for every inventory transaction. The utilization code parameters control the application behavior. You need the NOP codes for setting up utilization codes.

Table 2-2 Utilization Code Parameters

Utilization Parameter	Description
Complementary NF	Indicates the utilization is of type Complementary NF. When you select the Complementary NF check box, the Complementary NF Type list is enabled.
Complementary NF Type	Choose the Complementary NF type from the ComplementaryNF Type list: Triangulation Non-Merchandise Cost Cost/Tax Correction Exit NF
ICMS-ST Recovery	Controls whether the particular transaction is marked for Imposto sobre Circulação de Mercadorias e prestação de Serviços (ICMS)-ST tax recovery or not.
Item Utilization	The Item Utilization is sent to Tax Rules when populating the Freight Object. Choose the valid values from the following Utilizations LOV: Commercialization (C) Industrialisation (I)
Automatic NF Approval	Controls whether or not the outbound fiscal documents are validated, matched and approved automatically. This is relevant only for outbound NFs.
Allow Receiving	Select this check box to enable the schedule submission message flow to RWMS and SIM. In case of complementary NFs, where no receiving happens, this check box is disabled. This indicator is relevant for inbound NFs only.
Choose NF	Select this check box to choose a reference fiscal document. This is relevant for returns to vendor (RTV) related utilizations only.
Import Order NF	Select this check box if the utilization ID is for a PO NF of type Import.
Import Order Type	Choose one of the following Import Order Type from the Import Order Type list: Direct Import Import on behalf of Third Parties Import By Order
NFE Manifest	Select this check box to request manifest.

Note:

Both Complementary NF and Complementary NF Type check boxes are not editable if you use the utilization code in an NF.
If the Import Order type is Direct Import, the Complementary NF cannot be setup as Triangulation as there is no Triangulation for Direct Import Order currently supported in the system.
Complementary NF can also be issued for Any Exit NF. The Requisition type for this configuration must be FFNF.

ORFM System Configuration Table – All ORFM system parameters are located in FM_SYSTEM_OPTIONS table. These system parameters define some system behaviors that must be informed to ensure alignment between ORFM features and customer's business requirements.

The following are all ORFM system parameters (categorized under respective functionality) required to be set up appropriately:

General System Options: These parameters define general ORFM system behavior.

Table 2-3 General System Options

Variable	Description	Valid Values
ALLOW_SUBMIT_DATE	Check Entry_Or_Exit Date and Exit Hour fields for all NF in a schedule during submit for receiving process is greater than system date.	Y: If greater than system date, user will be not able to submit schedule for receivingN: If greater than system date, user is able to submit schedule for receiving.
DEBIT_MEMO_TRAN_CODES	Tran Codes list which have to be posted as look up code CREDIT in AP header staging, field FISCAL_TYPE_LOOKUP_CODE	Valid tran codes separated by comma.
DEFAULT_ACTION_REQ_PARM	Default Action Required Parametrization list of all NF status.	Fixed value ''ARBS'' that is code_type from code_detail table.
DEFAULT_COST_TAX_NOP	Default cost tax calls NOP.	Valid Nature Of Operation (NOP) ID.
DEFAULT_COUNTRY	Default supplier country.	Valid country ID. Default BR.
DEFAULT_CURRENCY	Default currency code.	Valid currency ID. Default BRL.
DEFAULT_NFCE_DOC_TYPE	Default Document Type for NFCe.	Valid Fiscal Document Type.
DEFAULT_NFCE_MODEL_CODE	Default Model Code for Customer NFE (NFCe).	Valid NFCe Model code.
DEFAULT_NFE_DOC_TYPE	Default Document Type for NFE.	Valid Fiscal Document Type.
DEFAULT_NFE_IND_TYPE	Default NFe indication.	Y: Indicate that system is working with Electronic NF. Default value N: Indicate that system is not working with Electronic NF.
DEFAULT_NFE_MODEL_CODE	Default Model Code for NFE.	Valid NFe Model code.
DEFAULT_NOP	Default Nature of Operation.	Valid Nature of Operation (NOP) ID.
DEFAULT_PRENF_SERIES	Default PRENF series. Used in issue NF that is not get official sequence number.	Until 5 alphanumeric position.
DEFAULT_REF_MESSAGE	This NF number %s1 is referenced to the original NF %s2 issued on %s3 respectively.	Valid referenced NF Message.
DEFAULT_REF_MESSAGE_ICMS_ST	ICMS-ST retido anteriormente, Base Cálculo R$ %s1, Valor Retido R$ %s2.	Valid ICMS ST Message.
DEFAULT_RETAIL_TAX_NOP	Default retail tax calls NOP.	Valid Sales Nature of Operation (NOP).
DOC_TYPE_PO	Default fiscal document type code (e.g. 1 - Nota Fiscal - Modelo 1, 1A).	Valid Fiscal Document Type.
ENABLE_DEBUG	Indicates whether to save the debug messages on the debug table (FM_DEBUG).	Y: enable debug messages on the debug table (FM_DEBUG).N: disable debug messages on the debug table (FM_DEBUG).
EXT_TAX_PROVIDER	Indicates which external tax provider is integrated with the system.	Taxweb: Taxweb Tax Engine.Synchro: Synchro Tax Engine.
HOUR_FORMAT	Format to represent fields of hour. Must be HH24:MI or HH:MI AM.	HH24:MI: 24 hour formatHH12:MI: 12 hour format
NF_BREAKUP_TAX_REGIME	Identify the attribute for breaking the NF.	Y: System breaks NF when ST flag is flagged at Item level during issuing NFNull: System does not break NF when ST flag is flagged at Item level during issuing NF
NF_MAX_ITEM	Maximum allowable line Items on NF during the issue. If number of items is greater than defined in this parameter, from next item will be issued in other NF.	Valid number value
NUMBER_FORMAT	Value Field Format.	FM9G999G999G999G990D90PR: Default format value
NUMBER_FORMAT_4	Value Field Format for 4decimal.	NUMBER_FORMAT_4: Default format value
ORFMI_MAX_DAYS	Number of days minus the ORFMi date.	Valid number value
ORFMI_MIN_DAYS	Number of days minus the ORFMi date.	Valid number value
ORFMO_MAX_DAYS	Number of days minus the ORFMo date.	Valid number value
ORFMO_MIN_DAYS	Number of days minus the ORFMo date.	Valid number value
PERCENT_FORMAT	Percentage Field Format.	FM9G999G999G999G999G990D9000"%": Default format value
QTY_FORMAT	Quantity Field Format.	FM9G999G999G999G999G999G990D0: Default format value.
RECOVERABLE_TAX_CST	Value related to the selected CST	Valid CST number value

Orders System Options: These parameters define ORFM system behavior to Purchase Orders.

Table 2-4 Orders System Options

Variable	Description	Valid Values
COST_RESOLUTION_RULE	Default Resolution Action for Cost Discrepancies	RECONCILE: When user decides discrepancy resolution. SYS: System will automatically resolve discrepancy by system. NF: System will automatically resolve discrepancy by NF
DEFAULT_DISCREP_LEGAL_MESSAGE	Stores the default legal message in SPED detail table, in field TXT, when discrepancy resolution is resolved by SYSTEM.	Valid Legal Message
DEFAULT_ORIGIN_CODE	Retrieve Default Origin Code case user does not inform.	Y: Retrieve Origin Code from Item dataN: User must inform Origin Code
DEFAULT_PO_TYPE	During PO migration, it is used to provide fiscal utilization used in these migrated PO.	Valid Utilization ID
DEFAULT_RURAL_PROD_DOC_TYPE	Default Document Type for Rural Producer NF	Valid Fiscal Document Type
DEFAULT_RURAL_PROD_UTILIZATION	Default Utilization ID for Rural Producer NF	Valid Utilization ID
ENABLE_AUTO_UPDATE_ORIGIN_FCI	Enables auto update for Item-Location Origin and FCI.	Y: Enable update FCI number and Origin Code in Item/Location with data from PO entry NFN: Disable update FCI number and Origin Code in Item/Location with data from PO entry NF
QTY_RESOLUTION_RULE	Default Resolution Action for Quantity Discrepancies	RECONCILE: when user decides discrepancy resolution. SYS: system will automatically resolve discrepancy by system. NF: system will automatically resolve discrepancy by NF
TAX_RESOLUTION_RULE	Default Resolution Action for Tax Discrepancies	RECONCILE: when user decides discrepancy resolution. SYS: system will automatically resolve discrepancy by system. NF: system will automatically resolve discrepancy by NF

Deals System Options: These parameters define ORFM system behavior to Deals Management.

Table 2-5 Deals System Options

Variable	Description	Valid Values
DEAL_DEFAULT_UTIL	Default Utilization ID for deals.	Valid Utilization ID
DEAL_DEF_CMPLX_TYPE	Default Document Type for complex deals.	Valid Fiscal Document Type
DEAL_DEF_FXMRH_TYPE	Default Document Type for merchandise fixed deals.	Valid Fiscal Document Type
DEAL_DEF_FXNMRH_TYPE	Default Document Type for non-merchandise fixed deals.	Valid Fiscal Document Type

EDI System Options: These parameters define ORFM system behavior to EDI. Electronic Data Interchange (EDI) - It is a mechanism through which data is exchanged between two systems or parties. In retail, it is used to exchange data between a retailer and a vendor or third party. Certain system options need to be set up around EDI and supporting partners.

Table 2-6 EDI System Options

Variable	Description	Valid Values
DEFAULT_DOCUMENT_TYPE	Default document type used by the process to create an EDI document based on external systems.	Valid Fiscal Document Type
EDI_DEF_PTNR_ID	Indicates the default partner ID, in Transportation Details tab used in NFs created by screen and EDI.	Valid Partner ID
EDI_DEF_PTNR_TYPE	Indicates the default partner type, in Transportation Details tab used in NFs created by screen and EDI.	Valid Partner Type

Direct Import System Options: These parameters define ORFM system behavior to Direct Import transactions.

Table 2-7 Direct Import System Options

Variable	Description	Valid Values
DEFAULT_SOFTWAY_DI_UTIL_ID	Default Utilization ID for NF issued by RFM that imported from SOFTWAY DI NFs through EDI process.	Valid Utilization ID
DEF_SFTW_COMPL_CT_DI_UTIL_ID	Default Utilization ID for SOFTWAY Complementary NF with Additional Cost/Tax.	Valid Utilization ID
DEF_SFTW_COMPL_NM_DI_UTIL_ID	Default Utilization ID for SOFTWAY Complementary NF with Non Merchandise Additional Cost.	Valid Utilization ID
DI_NF_SERIAL_GENERATION_IND	Indicates whether the fiscal number, series, document type and utilization id are generated in RFM(Y) and it is RFM that issue NF or not (N), means that NF was issued in Softway.	Y: Importation NF is generated by RFMN: Importation NF is generated by Softway
DI_UNIT_COST_COMP	Indicates which trading system being used.It can be either Softway(S) or some Third party system(T)	S: SoftwayT: Third party system
PRIORITY_TSF_IPI_IMPORTED	Indicates the priority of import or non-imported stock on first exit	Y: Import stock on first exitN: Non-Import stock on first exit

Tolerance System Options: These parameters define ORFM system behavior to Importation.

Table 2-8 Tolerance System Options

Variable	Description	Valid Values
CALC_TOL_TYPE	For entry NF, indicates the calculation tolerance type: P when percentage and V when Value.	P: PercentageV: Value
CALC_TOL_VALUE	For entry NF, indicate the calculation tolerance value	Valid number

Sales and Tax Burden System Options: These parameters define ORFM system behavior to Sales and Tax Burden.

Table 2-9 Sales and Tax Burden System Options

Variable	Description	Valid Values
AVERAGE_TAX_RATE_SOURCE_ENTITY	Name of the authorized institute that provides the average cumulative tax rates for operations to end consumers.	Valid authorized Institute name
DEFAULT_REF_MESSAGE_FDSHIP	Default legal message to inform the relation between the Shipment NF and the Sale NF in a future delivery scenario.	Valid Future Delivery Shipment NF Message

Stand Alone System Options: These parameters define ORFM system behavior to Stand Alone.

Table 2-10 Stand Alone System Options

Variable	Description	Valid Values
END_CONSUMER_MAX_VALUE	Default End Customer Max Value	For FFNF for customers, disable END_CONSUMER flag when NF value is greater than this parameter.

Cancellation NF System Options: These parameters define ORFM system behavior to Cancelation NF.

Table 2-11 Cancellation NF System Options

Variable	Description	Valid Values
DEFAULT_CANCEL_MESSAGE	Default Cancel Message for NFe Cancellation	Valid system role.
DEFAULT_JUSTIF_NULLIFICATION	Default Justification for NF Nullification.	Valid Justification Message.
ENABLE_ACCOUTING_REVERSAL	Indicates whether to revert accounting information for cancelled Nota Fiscal.	Y: Enable accounting reversal for all cancel NF N: Disable accounting reversal for all cancel NF
FISCAL_CANCEL_ROLE	Role with privilege to NFE cancel.	Valid system role.
DEFAULT_CANCEL_MESSAGE	Manual approval protocol mask.	Valid Protocol Mask.
MANUAL_CANCEL_ROLE	Role with privilege to NFE manual cancel.	Valid system role.
STOCK_REVERSAL_VIRTUAL_STORE	Holds the default virtual store that will be used in the inventory reversal process to put merchandise back to the WH.	Valid virtual store number.

Commerce Anywhere NF System Options: These parameters define ORFM system behavior to Commerce Anywhere.

Table 2-12 Commerce Anywhere NF System Options

Variable	Description	Valid Values
DEFAULT_DRSP_CO_PO_TYPE	Default PO Type for Drop Ship Customer Order when null in ORMS (fiscal utilization code in ORFM)	Valid Utilization ID.
DEFAULT_FD_SALE_DOC_TYPE	Default Document Type for future delivery Customer Order SALE NF.	Valid Fiscal Document Type.
DEFAULT_FD_SALE_UTIL_ID	Default Utilization ID for future delivery Customer Order SALE NF.	Valid Utilization ID.
DEFAULT_FD_SHIP_DOC_TYPE	Default Document Type for future delivery Customer Order Shipment NF.	Valid Fiscal Document Type.
DEFAULT_FD_SHIP_UTIL_ID	Default Utilization ID for future delivery Customer Order Shipment NF.	Valid Utilization ID.
DEFAULT_OUTBOUND_CUST_UTIL_ID	Default Utilization ID for outbound customer order transfers.	Valid Utilization ID.
DEFAULT_PAYMENT_METHOD	Default Payment Method	01: Cash02: Check03: Credit Card04: Debit Card05: Store Card10: Voucher (VA - Vale Alimentação)11: Voucher (VR - Vale Refeição)12: Gift Card13: Voucher (VC - Vale Combustível)99: Others
DEFAULT_PRESENCE_IND_CO	Default presence indicator	Valid presence indicator number.
DEFAULT_PRESENCE_IND_NFCE	Default presence indicator for NFCE	Valid presence indicator number.
DEFAULT_PRESENCE_IND_NFE	Default presence indicator for NFE	Valid presence indicator number.
DEFT_MULTISITE_CO_IN_IC_DOC	Default Document Type for Multisite Customer Order Inbound IC Transfers.	Valid Fiscal Document Type.
DEFT_MULTISITE_CO_IN_IC_UTIL	Default Utilization ID for Multisite Customer Order Inbound IC Transfer.	Valid Utilization ID.
DEFT_MULTISITE_CO_IN_TSF_DOC	Default Document Type for Multisite Customer Order Inbound Transfer.	Valid Fiscal Document Type.
DEFT_MULTISITE_CO_IN_TSF_UTIL	Default Utilization ID for Multisite Customer Order Inbound Transfer.	Valid Utilization ID.
DEFT_MULTISITE_CO_OUT_IC_DOC	Default Document Type for Multisite Customer Order Outbound IC Transfers.	Valid Fiscal Document Type.
DEFT_MULTISITE_CO_OUT_IC_UTIL	Default Utilization ID for Multisite Customer Order Outbound IC Transfers.	Valid Utilization ID.
DEFT_MULTISITE_CO_OUT_TSF_DOC	Default Document Type for Multisite Customer Order Outbound Transfer.	Valid Fiscal Document Type.
DEFT_MULTISITE_CO_OUT_TSF_UTIL	Default Utilization ID for Multisite Customer Order Outbound Transfer.	Valid Utilization ID.
DEFT_SALE_CO_DOC_TYPE	Default Doc Type for Outbound CO.INTER-State: All. INTRA-State: Addressee is NOT an End Consumer or an ICMS Contributor.	Valid Fiscal Document Type.
DEFT_SALE_CO_DOC_TYPE_INTRA	Default Doc Type for Outbound CO. INTRA-State: Addressee must be an End Consumer and must NOT be an ICMS Contributor.	Valid Fiscal Document Type.

Inventory Adjustment System Options: These parameters define ORFM system behavior to Inventory Adjustment.

Table 2-13 Inventory Adjustment System Options

Variable	Description	Valid Values
DEFAULT_DNF_STOCK_DOC_TYPE	Default Document Type for DNF Inventory Adjustments.	Valid Fiscal Document Type.
DEFAULT_STOCK_DOC_TYPE	Default Document Type for Inventory Adjustments.	Valid Fiscal Document Type.
ENABLE_SIM_WS_INTEGRATION	Identify if when there is a NF cancellation RFM will call the SIM Inv Adj Web Service to. Valid values should be Y or N.	Y: call the SIM Inventory Adjustment Web Service to inform SIM about NF cancellation N: call the SIM Inventory Adjustment Web Service to inform SIM about NF cancellation.
REASON_ID_INVADJ_SIM_WS_INT	This variable holds the reason ID used for integration with SIM Inventory Adjustment Web Service.	Valid number value.

Invoice Receiving Layer (IRL) System Options: These parameters define ORFM system behavior to Invoice Receiving Layer (IRL).

Table 2-14 Invoice Receiving Layer (IRL) System Options

Variable	Description	Valid Values
DEFAULT_COMP_COST_TAX_UTIL_ID	Default Utilization ID for complementary cost NF.	Valid Utilization ID.
DEFAULT_COMP_FREIGHT_UTIL_ID	Default Utilization for complementary freight NF.	Valid Utilization ID.
DEFAULT_TRIANGULATION_UTIL_ID	Default Utilization ID to use in triangulation NF that came from IRL.	Valid Utilization ID.
IRL_ALLOWS_MULTISITE	Indicates if IRL Monitor allows multisite treatment.	Y: Allow IRL monitor for multi-siteN: Allow IRL monitor for single-site.
IRL_ALLOWS_WORKSHEET	Indicates if WORKSHEET option will be available for IRL.	Y: Allow users change IRL NF status to WorksheetN: Does not allow users change IRL NF status to Worksheet.
IRL_AUTO_REFUSAL	Indicates if IRL allows automatic refusal in Pre-validation.	Y: system can auto refusal NF that comes from IRLN: system cannot auto refusal NF that comes from IRL.
IRL_AUTO_REFUSAL_DESCRIPTION	Indicates the default reason description to Automatic Refusal.	Valid Auto Refusal message.
IRL_REASON_DESCRIPTION	Indicates if IRL Receipt Refusal requires reason description.	Y: IRL Receipt Refusal requires reason description.N: IRL Receipt Refusal does not require reason description.
IRL_SEFAZ_VALIDATION	Indicates if IRL SEFAZ validation is required.	Y: IRL SEFAZ validation is required before pre-validation processN: IRL SEFAZ validation does not required before pre-validation process.
IRL_XML_DATABASE_BKP	Indicates if IRL allows storing XML into database.	Y: IRL allows storing XML into database.N: IRL does not allow storing XML into database.

Reclassification System Options: These parameters define ORFM system behavior to Reclassification.

Table 2-15 Reclassification System Options

Variable	Description	Valid Values
FM_FRECLASS_ACTIVE_DATE	Minimum number of days of active date to item fiscal reclassification from system date. If 0 means change is done immediately.	Valid number value.
FM_FRECLASS_COPY_DOWN_CHILD	In process of fiscal item reclassification is copy classification item parent to child.	Y: reclassification item parent extends to child items.N: reclassification item parent does not extend to child items.
FM_FRECLASS_ONLINE_IND	Define information that can be edit in screen.	Y: Reclassification will be on line N: reclassification will be only through batch.

Transfers, Transfers IC, and Repairing System Options: These parameters define ORFM system behavior to Transfers, Transfers IC, and Repairing.

Table 2-16 Transfers, Transfers IC, and Repairing System Options

Variable	Description	Valid Values
DEFAULT_INBOUND_IC_DOC_TYPE	Default Document Type for Inbound IC Transfers.	Valid Fiscal Document Type
DEFAULT_INBOUND_IC_UTIL_ID	Default Utilization ID for Inbound IC Transfers.	Valid Utilization ID
DEFAULT_INBOUND_REP_DOC_TYPE	Default Document Type for Inbound Repairing Transfers.	Valid Fiscal Document Type
DEFAULT_INBOUND_REP_UTIL_ID	Default Utilization ID for Inbound Repairing Transfers.	Valid Utilization ID
DEFAULT_INBOUND_TSF_DOC_TYPE	Default Document Type for Inbound Transfers.	Valid Fiscal Document Type
DEFAULT_INBOUND_TSF_UTIL_ID	Default Utilization ID for Inbound Transfers.	Valid Utilization ID
DEFAULT_IN_RETURN_IC_UTIL_ID	Default Utilization ID for Return Transfers Inter-Company.	Valid Utilization ID
DEFAULT_IN_RETURN_TSF_UTIL_ID	Default Inbound Utilization ID for Return Transfers.	Valid Utilization ID
DEFAULT_IN_RET_IC_DOC_TYPE	Default Inbound Document Type for Return Transfers Inter Company.	Valid Fiscal Document Type
DEFAULT_IN_RET_TSF_DOC_TYPE	Default Inbound Document Type for Return Transfers.	Valid Fiscal Document Type
DEFAULT_OUTBOUND_IC_DOC_TYPE	Default Document Type for Outbound IC Transfers.	Valid Fiscal Document Type
DEFAULT_OUTBOUND_IC_UTIL_ID	Default Utilization ID for Outbound IC Transfers.	Valid Utilization ID
DEFAULT_OUTBOUND_REP_DOC_TYPE	Default Document Type for Outbound Repairing Transfers.	Valid Fiscal Document Type
DEFAULT_OUTBOUND_REP_UTIL_ID	Default Utilization ID for Outbound Repairing Transfers.	Valid Utilization ID
DEFAULT_OUTBOUND_TSF_DOC_TYPE	Default Document Type for Outbound Transfers.	Valid Fiscal Document Type
DEFAULT_OUTBOUND_TSF_UTIL_ID	Default Utilization ID for Outbound Transfers.	Valid Utilization ID
DEFAULT_OUT_RETURN_IC_UTIL_ID	Default Outbound Utilization ID for Return Transfers Inter-Company.	Valid Utilization ID
DEFAULT_OUT_RETURN_TSF_UTIL_ID	Default Outbound Utilization ID for Return Transfers.	Valid Utilization ID
DEFAULT_OUT_RET_IC_DOC_TYPE	Default Outbound Document Type for Return Transfers Inter Company.	Valid Fiscal Document Type
DEFAULT_OUT_RET_TSF_DOC_TYPE	Default Outbound Document Type for Return Transfers.	Valid Fiscal Document Type
REF_NF_MANDATORY_FREIGHT	Indicates if it is mandatory to inform the reference NF for Complementary NF Freight.	Y: it is mandatory to inform the reference NF for Complementary NF Freight. N: it is not mandatory to inform the reference NF for Complementary NF Freight.
TSF_PURCHASE_PRICE	Indicates whether last purchase price(Y) OR WAC(N) as valid value when issue a transfer NF.	Y: Last purchase price as valid value on transfer NF N: WAC as valid value on transfer NF.

Return Merchandise Authorization (RMA) System Options. These parameters define ORFM system behavior to Return Merchandise Authorization (RMA).

Table 2-17 Return Merchandise Authorization (RMA) System Options

Variable	Description	Valid Values
DEFAULT_RMA_DOC_TYPE	Default Document Type for RMA	Valid Fiscal Document Type
DEFAULT_RMA_UTIL_ID	Default Utilization ID for RMA	Valid Utilization ID

Return to Vendor (RTV) System Options. These parameters define ORFM system behavior to Return to Vendor (RTV).

Table 2-18 Return to Vendor (RTV) System Options

Variable	Description	Valid Values
BALANCE_CONTROL_RTV	Indicates whether the balance control for RTV is hold or not.	Y: Balance Control is ON and Balance Control tables will be filled and RTV will use it to referenced NFsN: Balance Control is OFF.
DEFAULT_FREIGHT_TYPE	Default freight type used by processes that issue NF as RTV, RNF, Transfers and RMA.	CIF: Cost, Insurance and FreightFOB: Freight on Board9: No Freight
DEFAULT_REASN_FOR_RTRN	Default Reason for a Return Document.	Valid number
DEFAULT_REF_MESSAGE_RTV	Devolução ref. a NF n½ %s1, emitida em %s2, Valor de R$ %s3	Valid referenced RTV Message
DEFAULT_RNF_DOC_TYPE	Default Document Type for Return NF	Valid Fiscal Document Type
DEFAULT_RNF_UTILIZATION_ID	Default Utilization ID for Return NF	Valid Utilization ID
DEFAULT_RTV_DOC_TYPE	Default Document Type for RTVs.	Valid Fiscal Document Type
DEFAULT_RTV_DOC_TYPE_TRIANG	Default Document Type for Triangulation RTVs.	Valid Fiscal Document Type
DEFAULT_RTV_UTIL_ID	Default Utilization ID for RTVs.	Valid Utilization ID
DEFAULT_RTV_UTIL_TRIANG_ID	Default Utilization ID for outbound RTV NF for the Supplier Delivery in a triangular operation purchase.	Valid Utilization ID
REF_NF_MANDATORY_RTV	Indicates if it is mandatory to inform the reference NF for RTV NF issues.	Y: it is mandatory to inform the reference NF for RTV NF.N: it is not mandatory to inform the reference NF RTV NF.

Purge System Options. These parameters define ORFM system behavior to Purge.

Table 2-19 Purge System Options

Variable	Description	Valid Values
FM_FRECLASS_PURGE	Minimum Days to keep records of item fiscal reclassification lots after purge batch execution.	Valid number value
HISTORY_DAYS_GTAX_ITEM_ROLLUP	Number of days in the past that will be used for purge to TAX_ITEM_ROLLUP_HIST	Valid number value
HISTORY_DAYS_HIST_TABLES	Number of days the history table can hold the records	Valid number value
HISTORY_DAYS_POS_MODS_TAX_INFO	Number of days in the past that will be used for purge to POS_MODS_TAX_INFO_HIST	Valid number value
HISTORY_DAYS_PROCESSED_EDI	Number of days the EDI NFs can exits in the EDI tables before getting purged.	Valid number value
IRL_PURGE_DAYS	Indicates the number of days for purge the IRL tables.	Valid number value
PURGE_DAYS	Days before records are purged from the tables	Valid number value

Tolerance setup – Set up tolerances at cost, quantity (percentage or value set for system/supplier) and calculation level (for rounding or truncation) in FM_TOLERANCES table. During fiscal processing, the entry NF values are compared with the PO details for variances; tolerances facilitate identification of only those discrepancies which fall over and above applicable tolerance levels.
ORFM Tax setup – Enter the tax codes as in the TaxWeb Tax Rules in the VAT Codes Maintenance form of RMS. Tax details have to be inserted manually in the ORFM FM_TAX_CODES table, because there is no user interface in the ORFM application for inserting the tax details. The value added tax (VAT) codes in ORFM must be similar to the data set up in VAT codes in RMS. Also, ensure that the tax code/VAT codes set up in RMS and ORFM are as available in the TaxWeb Tax Rules.
Fiscal Document Numbering Sequence setup – Set up the fiscal document number sequencing details through the Location Fiscal Number form in ORFM. Fiscal document number sequence set up enables you to capture details on sequence series for each supported requisition type. During NF generation, ORFM generates and associates a unique sequence number to the NF based on its requisition type and related sequence series.
Brazil Localization setup – Verify that the L10N_PKG_CONFIG table for decoupling contains entries for Brazil before any transactions happen within ORFM. These entries enable Brazil localization related features.
SPED Configuration setup – For SPED, you have to interface with third-party system. You have to share the database, and the ports have to be opened in order to establish network connectivity. You can decide to either host the SPED interfacing application (Interdados) within their environment or host it in fiscal partner's environment. For security considerations, a separate schema has to be created that contains only synonyms to as many objects required by the fiscal partner to generate the SPED information. Only the 'select' privileges has to be granted on these synonyms. No insert/update/delete should be allowed. This integrated environment is accessed through DB Link by third party systems.
Ensure access to the following forms (accessed through RMS forms) are denied through Security settings for Brazil localized users when Brazil localization is ON:
- Receiver Cost Adjustment (RECCTADJ)
- Receiver Unit Adjustment (RECUTADJ)
- Average Cost Adjustment (AVCSTADJ)
- Inventory Adjustment by Item (INVADJSK)
- Inventory Adjustment by Location (INVADJST)

Note:

Only RMS supports the multi-currency functionality.