Remito Argentina

Davi Bernardes
Oracle LACLS
October, 2022

2 Confidential – © 2019 Oracle Internal/Restricted/Highly Restricted

Agenda
1 Solution approach
2 Introduction
3 Functional Configuration overview
4 Technical Configuration overview
5 Creating a Remito
6 COT Integration
7 Printed Remito
8 Monitoring Remitos and COT
9 Documentation

3 Confidential – © 2019 Oracle Internal/Restricted/Highly Restricted

Agenda
1 Solution approach
2 Introduction
3 Functional Configuration overview
4 Technical Configuration overview
5 Creating a Remito
6 COT Integration
7 Printed Remito
8 Monitoring Remitos and COT
9 Documentation

4 Confidential – © 2019 Oracle Internal/Restricted/Highly Restricted

 Solution approach
Remito is a legal document that supports the transfer and/or movements of products and goods.

Remito has a proper number that must comply with the Argentinean government format and rules, not being
allowed gaps over its numbering.

The Remito number has 17 digits and is composed by 3 segments separated by a hyphen (‘-‘):
1) Letter
“R” or “X” depending on type of movements
Length: one digit
2) Branch
Defined by the Tax authority
Length: four or five digits
3) Sequential numbering
Range number assigned by the Tax authority
Length: eight digits
The sequence number is gapless and must be increment by one number for each Remito created

The Remito number is assigned to the Shipment after the Ship Confirm action is concluded. This will
guarantee there is no gap in the Remito numbering since confirmed Shipments can’t be changed anymore.

The Remito may be needed to be submitted for Tax Authority approval depending on the products/goods
source or target locations. The process of communicating the Remito to the Tax Authority is named “COT”.
Solution approach
Solution approach
Solution approach
Agenda
1 Solution approach
2 Introduction
3 Functional Configuration overview
4 Technical Configuration overview
5 Creating a Remito
6 COT Integration
7 Printed Remito
8 Monitoring Remitos and COT
9 Documentation

9 Confidential – © 2019 Oracle Internal/Restricted/Highly Restricted

 Introduction
Solution scope:

 User interface to configure the Remito Numbering process;

 Prints the Remito;

 Interfaces the Remito (COT) with Tax Authority via Planexware or Gosocket;

 Monitors the Remitos and COT statuses thru a monitoring dashboard;

Agenda
1 Solution approach
2 Introduction
3 Functional Configuration overview
4 Technical Configuration overview
5 Creating a Remito
6 COT Integration
7 Printed Remito
8 Monitoring Remitos and COT
9 Documentation

11 Confidential – © 2019 Oracle Internal/Restricted/Highly Restricted

 Functional Configuration overview
Inventory In LACLS Remito Setup
Shipments Organizations
User

ERP Custom Roles Numbering

Grants access to the
rules
Remito Setup

Data Access
Business Units Geography
Shipping Party Fiscal
Legal Entity Lookup
Parameters for Document Classification
Inventory Org. Sequences

Customer Lookup Geography

Descriptive Flex Tax Reporting Localization

Fields Type System options Processing
Inventory Catalog Product Item

12
Functional Configuration overview
Allow application use
and data access

Data Accesses
Functional Configuration overview
Functional Configuration overview
Functional Configuration overview
Functional Configuration overview
Functional Configuration overview
Functional Configuration overview
Functional Configuration overview
 Functional Configuration overview

Manage Legal Entity Tax Profile =>

Functional Configuration overview
Functional Configuration overview
 Functional Configuration overview
The Lookup Code of the Lookup Type LACLS_AR_COT_PROVINCES accommodate the tax authority province code which
demands COT.

In the example below verify that the lookup codes B, C and S are the Tax Authority Province Code which represents
respectively Buenos Aires, CABA and Santa Fe. That means the provinces identified with codes B, C and S in the ERP will
generate COT.
 Functional Configuration overview
The Customer VAT Condition is displayed below to the ship to name in the printed Remito.

For that to happen, it is necessary to associate the fiscal classification code which represents the VAT condition to the
Customer and to the Legal Entity.

Whenever a Remito goes to a customer the Vat condition will be extract from the Customer Classification, but if the Remito
goes to another inventory organization, i.e. a Trasfer Order, the Vat condition will be extracted from the Legal Entity
Classification.
 Functional Configuration overview

Customer => Legal Entity =>

Agenda
1 Solution approach
2 Introduction
3 Functional Configuration overview
4 Technical Configuration overview
5 Creating a Remito
6 COT Integration
7 Printed Remito
8 Monitoring Remitos and COT
9 Documentation

27 Confidential – © 2019 Oracle Internal/Restricted/Highly Restricted

Technical Configuration overview
Padrones

ERP SFTP OIC

Deploy Integrations
Create folder
Deploy BIP structures

Configure the
connections

Create custom
Configure the OIC
LACLS Roles
Lookup

Deploy VBCS

Prepare the
integration user
Configure VBCS
User

28
 Technical Configuration overview
User cretion requirements:

To access the Remito application, the users from Oracle ERP Cloud must also have a valid user in the Oracle Integration
Cloud Service (OIC).

The end user needs to have an OIC User and an ERP User sharing the same user name and e-mail.

Remito’s users can’t have multiple ERP users sharing the same e-mail otherwise it won’t be possible access Remito
application.

Additionally the OIC user must have the role “ServiceUser (Service instance user role.)” assigned to it.

Valid connection

ERP OIC

Username = User1 Username = User1

E-mail = user1@oracle.com E-mail = user1@oracle.com
 Technical Configuration overview
In general integration users are used to configure the OIC connections instead a regular application user and as well is the
user informed in the OIC Lookup parameter.
This is the user which triggers the ERP services in behalf of the current user, so it is recommended that the integration user
has as much as privileges as possible. The regular user logged in the application does not need to know the integration user
credentials.

Attention: Make sure to grant data access in the integration user’s roles based in your functional implementation, like
business unit names, ledger names, inventory organizations, reference data sets and other information which is unique to
your implementation design. You may require your functional expert to accomplish this task.
Application Diagnostics Administrator ORA_FND_DIAG_ADMINISTRATOR_JOB
Application Diagnostics Regular User ORA_FND_DIAG_REGULAR_USER_JOB
Application Implementation Consultant ORA_ASM_APPLICATION_IMPLEMENTATION_CONSULTANT_JOB
Employee ORA_PER_EMPLOYEE_ABSTRACT
Inventory Manager ORA_INV_INVENTORY_MANAGER_JOB
Order Manager ORA_DOO_ORDER_MANAGER_JOB
Order Orchestration Error Recovery Manager ORA_DOO_ORDER_ORCHESTRATION_ERROR_RECOVERY_MANAGER_ABSTRACT
Order Promising Manager ORA_MSC_ORDER_PROMISING_MANAGER_JOB
Pricing Manager ORA_QP_PRICING_MANAGER_JOB
Product Data Steward ORA_EGI_PRODUCT_DATA_STEWARD_JOB
Resource ORA_HZ_RESOURCE_ABSTRACT
Sales Administrator ORA_ZBS_SALES_ADMINISTRATOR_JOB
Sales Analyst ORA_ZSP_SALES_ANALYST_JOB
Sales Manager ORA_ZBS_SALES_MANAGER_JOB
Sales Representative ORA_ZBS_SALES_REPRESENTATIVE_JOB
Shipping Manager ORA_WSH_SHIPPING_MANAGER_JOB
Supply Chain Application Administrator ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB
Supply Chain Planning Application Administrator ORA_MSC_SUPPLY_CHAIN_PLANNING_APPLICATION_ADMINISTRATOR_JOB
Warehouse Manager ORA_INV_WAREHOUSE_MANAGER_JOB
Agenda
1 Solution approach
2 Introduction
3 Functional Configuration overview
4 Technical Configuration overview
5 Creating a Remito
6 COT Integration
7 Printed Remito
8 Monitoring Remitos and COT
9 Documentation

31 Confidential – © 2019 Oracle Internal/Restricted/Highly Restricted

Creating a Remito
Creating a Remito
Agenda
1 Solution approach
2 Introduction
3 Functional Configuration overview
4 Technical Configuration overview
5 Creating a Remito
6 COT Integration
7 Printed Remito
8 Monitoring Remitos and COT
9 Documentation

34 Confidential – © 2019 Oracle Internal/Restricted/Highly Restricted

COT Integration
COT Integration
COT Integration
 COT Integration
Transfer orders to customers

In case of Shipments for Transfer Orders it is possible to override information related to the destination by using the configured
descriptive flexfields.

The overridden information takes effect only on COT file, i.e: Supposing the customer ‘A’ is referred inside the shipment but user
decided to use the overridden functionality on the flexfield to point to the customer ‘B’. When COT is generated it will collect
information related from customer ‘B’ instead from customer ‘A’.
 COT Integration
Patente vehiculo

Patente Vehiculo is a required information for COT approval if “Transportista CUIT” is the same as “CUIT Empresa”.

The patente vehiculo information can be stored at Shipment and/or Carrier via descriptive flexfields.

The COT process first tries to extract the Patente Vehiculo from the Shipment, in case it is no filled it tries to extract from Carrier.
Agenda
1 Solution approach
2 Introduction
3 Functional Configuration overview
4 Technical Configuration overview
5 Creating a Remito
6 COT Integration
7 Printed Remito
8 Monitoring Remitos and COT
9 Documentation

40 Confidential – © 2019 Oracle Internal/Restricted/Highly Restricted

Printed Remito
Agenda
1 Solution approach
2 Introduction
3 Functional Configuration overview
4 Technical Configuration overview
5 Creating a Remito
6 COT Integration
7 Printed Remito
8 Monitoring Remitos and COT
9 Documentation

42 Confidential – © 2019 Oracle Internal/Restricted/Highly Restricted

Monitoring Remitos and COT
Monitoring Remitos and COT
Agenda
1 Solution approach
2 Introduction
3 Functional Configuration overview
4 Technical Configuration overview
5 Creating a Remito
6 COT Integration
7 Printed Remito
8 Monitoring Remitos and COT
9 Documentation

45 Confidential – © 2019 Oracle Internal/Restricted/Highly Restricted

 Documentation

https://mosemp.us.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=1399
96534907750&id=2622019.1&_adf.ctrl-state=18in9wfr14_53
Note: Latin America Cloud Local Solution for Argentina (Doc ID 2622019.1)
Documentation

https://docs.oracle.com