Oracle® Retail Merchandising System/Sales Audit Brazil Localization User Guide Release 14.1.3 E83673-01 |
|
Previous |
Next |
This chapter describes the new forms and updates to the forms in the transfers and inventory control modules of RMS.
The chapter contains the following sections:
The Transfer Maintenance window includes updates to address the Repairing type of transaction. The changes are as follows:
A new Context Type called Repairing is added in the Transfer Maintenance window. This is to indicate the transfer is meant for repairing.
The Utilization Code menu item has been introduced in the Options menu for the Transfer Maintenance window.
To edit a transfer, do the following:
Navigate: From the RMS Start Menu, select Inventory, then select Transfer. The Transfer Search window appears.
Search for, and retrieve a transfer in New/Edit mode. The Transfer Maintenance window appears.
To enable two-legged transfers, a new context type called Repairing has been added as shown below.
Note: For more information about creating two-legged transfers, refer to Creating two-legged transfers. |
Edit the remaining fields on the Transfer Maintenance as required.
A retailer may send merchandise to the external finisher or the supplier for finishing work (such as printing, dyeing, and embroidery), or repair (in case of damaged merchandise). After the finishing or repairing work is done, the finisher or the supplier may return the merchandise back to the same location or to a different location. The merchandise may be sent to a third party warehouse merely for temporary stocking and as required, the third party warehouse may send them back. While the merchandise are out of warehouse or store for stocking, repair, or finishing, RMS accounts for the inventory as the retailer's inventory.
This flow is handled in RMS through two-legged transfers. In the first leg, inventory is sent from the retailer's location (warehouse or store) to the finisher's location. In the second leg, finished or repaired merchandise are received back from the finisher at the retailer's location. Because the finisher's location is an outside location, the retailer is not responsible for the receiving or shipping activities at those locations.
Repairing activity can be initiated from any downstream application. The details of the activity are published to RMS to create a two-legged transfer. The following changes have been made in RMS to create a two-legged transfer:
The downstream application has to publish the transfer details for the first leg such as the warehouse/store–external finisher.
RMS checks the ”To location” on the transfer. If the ”To location” is an external finisher, it creates a two-legged transfer using the ”from” and ”to” locations. The first leg will have the ”From location” and ”To location”. This location information is published by the downstream applications, and the second leg will have the ”To location” as ”From Location” and ”From Location” as ”To Location.”
In Brazil, every transaction types such as purchase order, transfer, return to vendor will have the information about the purpose of buying or selling or transfer. This is typically referred to as Utilization. Each utilization code is associated with one or more CFOP codes. CFOP codes are provided by the Federal government which is used to do the tax calculation in ORFM.
To add an utilization code, do the following:
Navigate: From the RMS Start Menu, select Inventory, then select Transfer. The Transfer Search window appears.
Search for, and retrieve a transfer in New/Edit mode. The Transfer Maintenance window appears.
Click the Options menu. Utilization is part of the Options menu in the Transfer Maintenance window.
Click Utilization. The Localization Flexible Attributes window appears.
Click the Utilization Code LOV. Select the applicable utilization code from the List of Util Codes for TSF/MRT that is displayed.
Click Apply. The utilization code is associated with that transfer.
Changes have been made to relate transfer returns to the original transaction. The association process has not been changed. The following rules remain valid:
For transfer requests created directly in RMS, the association with new utilization is done manually.
For transfer requests created in the Store Inventory Management (SIM), the association is done automatically during the integration with RMS, using the new Context Type and the new System Option, setting the utilization default.
To identify the transaction as a Transfer Return in RMS, follow the steps below:
Navigate: From the RMS Start Menu, select Inventory, then select Transfer. The Transfer Search window appears.
Search for, and retrieve a transfer in New/Edit mode. The Transfer Maintenance window appears.
In the Context Type field, select Return Transfer. By selecting the context type, RMS automatically defaults to the Utilization for transfer returns.
The process of generating a transfer request has not changed. You only have to identify the transfer as a Transfer Return by choosing a new Context Type Return Transfer:
Creating a return, when the destination is a Warehouse
Creating a transfer, when the destination is a Store
A new option, Utilization, has been added to the Mass Return Transfers window.
Navigate: From the RMS Start Menu, select Inventory, then select Mass Return Transfers. The Mass Return Transfer Search window appears.
Search for and retrieve a transfer in Edit mode. Restrict the search to transfers in Input status. The Mass Return Transfers window appears.
To add an utilization code, do the following:
In the Mass Returns Transfer window, from the Options menu, click Utilization. The Localization Flexible Attributes window appears. This window is used for associating the utilization code to the Mass Returns Transfer.
Click the Utilization Code LOV. Select the relevant Utilization Code from the LOV.
Click Apply. The utilization code is associated with that mass return transfer.
Validation has been added during submission/approval of the MRT, so that if no utilization code is defined, an error message will be raised.