Frequently Asked Questions about In Out

It is the new version of the ONESOURCE Global Trade (OSGT) solution, the result of a technology modernization project. With a bolder design, modern components and new screens, ONESOURCE Global Trade (OSGT) is here to bring your business to a new level of accuracy, compliance and efficiency in foreign trade processes. We’re talking about a big step towards the future. Thus, in this document, the term OSGT will be used to refer to this new version and the term OSGT to refer to the current version.

Among several advantages and many benefits, we can highlight:

The modules included in the OSGT modernization plan are: In Out, Export, Import, Exchange (Import and Export), Drawback, Single Window (Import and Export) and RECOF. Other modules may be evaluated and included in the project scope in the future.

Launch will occur per module according to the following calendar:

The remaining modules will be released sequentially, being announced in advance at quarterly release events. If you are an on-premises customer, refer to the On-Premises Customers subtopic.

As of version 22.2 In Out is now available as OSGT. All cloud customers on version 22.2 (or higher) will be notified starting in November 2022 to begin using In Out.

The expected time to complete OSGT is approximately 3 years, with the first module being launched in November 2022. This time is subject to updates, which will be communicated throughout the project. So don't miss the quarterly release launch events.

Yes, LatAm In Out, Export and Import modules will be available in OSGT.

Both these releases and other OSGT-related news will be communicated in the quarterly release webinars.

On the

Data Import Errors

screen, depending on the interface where the error occurred, you need to specify the associated table (

Table

field in the top filter) that contains the process number. Then click the advanced filter icon, identified by a funnel symbol. Select the respective column and enter the process number you want to search in the list of import errors displayed.

For example: for the

IS - IN - TXT - Bill of Lading

interface, enter the

IS_BILL_OF_LADING_HEADER

table. Assign the desired value to the

COD_PROCESS

:

When an Import ID is canceled, the errors that appear are based on the filters on the home screen, including the date range. The

Data Import/Export

screen consists of three distinct areas: the

interface filter

in the left sidebar, the

interfaces with scheduled executions

in the upper right panel, and the

interfaces already executed

in the lower right panel. When an execution is canceled in the scheduled executions area, there is no change to the information displayed in the executed interfaces area. This last area reflects the configuration made in the filter selection (left panel), i.e., the errors presented remain associated with the same date range, but are only related to the interfaces selected in the filter panel.

There was no change to the In Out service on the machine (In Out Server). The changes made focused exclusively on the graphical pattern, layout and navigation flow of the screens. The service itself remains unchanged and will continue to work the same as before.

Yes. When replacing the current OSGT, the OSGT versions will by default support existing features. If any of these features are discontinued, we will notify all users in advance. To stay up to date on all of this, simply follow the release announcements sent out quarterly.

Yes, In Out has full feature parity with current In Out.

No, the scenarios and business flows supported by the modules will not undergo major changes. The new technology will have an impact primarily related to improvements in usability, access speed, and integration with other technologies.

No, the access credentials have not changed. They are the same as those used in the current OSGT version.

Access to the solution will be centralized in OSGT from version 22.4. That is, you will receive a new URL that will contain both In Out and access to the other OSGT modules.

Knowing this, to access the OSGT modules, follow these steps:

This can occur on first access to the OSGT version. When you first click on the ONESOURCE Global Trade app icon, you will be automatically redirected to Citrix where the applications for the current OSGT version are listed. On first access, in addition to this redirection, the user will be created in the Activity Directory (AD) and this user will be synchronized with all AD servers. This synchronization may take a while, causing the message “It is impossible to launch the XXX application” to appear. Wait a few minutes and repeat the access flow. From the second access, this message will no longer be displayed.

Yes, but it is important to remember that the application user interface is designed and optimized for increased desktop productivity. For a better mobile experience, consider using the newly launched ONERSOURCE Global Trade Mobile, available for IOS and Android platforms.

There is no additional technical requirement. The customer only needs internet access with access released to the OSGT address. As a Thomson Reuters hosted customer, the version upgrade process will remain the same, following the same communication process from our cloud team, starting with the update in the QA (Testing) environment and subsequently in PROD (Production). You will receive the additional required OSGT access information.

Yes. These customers will be able to use OSGT when this version is released to that customer segment. The projected release date is the second half of 2023, but we will release more information about this soon.

Customers who host OSGT in their own data centers will need to contact our network of approved partners or the Professional Services team for version updates, as currently occurs in release updates. For more information about customizations, see the subtopic Customizations and Personalizations.

These customers will need to make additional Linux servers available for the OSGT installation, which will be distributed in kubernetes-managed containers. In early 2023, we will make available in one document all the details of the OSGT architecture and installation, following current OSGT practice.

An additional executable will be made available that will install all required services on the new solution infrastructure in addition to the OSGT application itself. It is important to emphasize that the current OSGT installers responsible for installing the modules on the application server and performing the database update will be maintained. For OSGT we will have an additional installer.

No, because the OSGT architecture is based on open-source components and no additional components need to be licensed to upgrade to OSGT.

Existing data will be maintained and no migration is required. This is because the OSGT modules will be modernized versions of the current modules, operating in the same way. Your database will remain the same while maintaining all existing data.

For now, no. All interfaces will continue to run according to the current In Out service/interface server. Therefore, there will be no risk of impact to OSGT data/interface integration with enterprise systems.

No. To use OSGT, you only need a modern internet browser (Google Chrome, Mozilla Firefox, or Microsoft Edge) and internet access to enter the new application address. To learn more about how access for customers hosting OSGT in their own data centers will work, see the On Premises Customers subtopic.

No, standard and custom interfaces will not be impacted.

No, In Out has no personalizations and customizations that will be impacted. When customizable and personalizable modules are released in OSGT (as Export), we will provide tools to support the adaptation process or automate the conversion of some existing components.

In this context, upgrade simplification is one of the key pillars of OSGT modernization. Among the strategies we developed to maintain this simplicity we can mention:

In accordance with the current customization policy, both our Thomson Reuters Professional Services team and our network of approved partners will be enabled to perform this type of procedure from the customer request.

No, our support and service process will remain the same. If you have any questions about the process, please refer to our version policy.

The processes and channels for requesting support and suggesting product improvements remain the same as before. If you have any questions about the process, please refer to our version policy.

The OSGT launch webinar video, available on the Product Releases portal, has all the details of the new version. For specific questions, please reach out to your Customer Success Manager, Account Manager or partners.

Trainings are recorded and recordings are posted to the Help Center of the module, accessed via the help button ().

This manual is available in the Help Center of the module, accessed via the help button ().

No, because OSGT is considered the modernized version of the modules that our customers already own and are therefore already licensed.

No, just as it does not exist in the current version update process. For more information on personalizations and customizations, see the

Technical Information

subtopic.

Following the release of the module in the OSGT version, our clients will have the timeframe stipulated in the current version policy to update the solution.

Following the release of the OSGT module version, customers will have the time frame set forth in the current version policy to update, subject to the restrictions set forth in the policy if they do not use the supported versions.

As is already the case today, our OSGT cloud update team will notify each customer according to the release schedule. Additional training information may also be sent via email.