1 Feature Summary
This chapter describes the feature enhancements in this release.
Noteworthy Enhancements
This guide outlines the information you need to know about new or improved functionality in the Oracle Retail Merchandising Cloud Services update and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.
Column Definitions
-
Feature: Provides a description of the feature being delivered.
-
Module Impacted: Identifies the module associated with the feature, if any.
-
Scale: Identifies the size of the feature. Options are:
-
Small: These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.
-
Medium: These UI or process-based features are typically comprised of field, validation, or program changes. Therefore the potential impact on users is moderate
-
Large: These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.
-
-
Delivered: Is the new feature available for use immediately after upgrade or must the feature be enabled or configured? If no, the feature is non-disruptive to end users and action is required (detailed steps below) to make the feature ready to use.
- Customer Action Required: You must take action before these features can be used. These features are delivered disabled and you choose if and when to enable them.
Table 1-1 Noteworthy Enhancements
| Feature | Module Impacted | Scale | Delivered | Customer Action Required? | Oracle Service Request |
|---|---|---|---|---|---|
|
Merchandising, Invoice Match |
Large |
Disabled |
Yes |
No |
|
|
Pricing |
Large |
Disabled |
Yes |
No |
|
|
Merchandising |
Large |
Disabled |
Yes |
No |
|
|
Merchandising |
Medium |
Enabled |
Yes |
No |
|
|
Merchandising |
Small |
Enabled |
No |
No |
|
|
Enhanced Expense Profile Functionality to Allow Ability to Push a Profile Down to Items |
Merchandising |
Small |
Enabled |
No |
No |
|
Ability to Re-default Expense Profiles at Item-Supplier/Item-Supplier-Country Level |
Merchandising, |
Small |
Enabled |
No |
No |
|
Enhanced Purge Process for Purchase Orders to now Consider Active Invoices |
Merchandising |
Small |
Enabled |
No |
No |
|
Fiscal Management |
Large |
Enabled |
No |
No |
|
|
Invoice Match, Merchandising |
Small |
Enabled |
No |
No |
|
|
New Get Rest Service to Retrieve Item Location Weekly Sales History |
Merchandising |
Small |
Disabled |
Yes |
No |
|
Merchandising |
Small |
Enabled |
No |
No |
Consignment Invoicing Enhancements
This cloud service update includes enhancements adding two significant functionalities to the existing consignment support offered by Oracle Retail:
-
Consignment Cost Review – This allows for reviewing consignment costing in Sales Audit post consignment sales.
-
Consignment Vendor Invoicing -This allows for Consignment Invoicing like conventional invoicing involving entry of invoices from vendors and matching in Invoice Matching Cloud Service (IMCS).
Consignment Cost Review
With this enhancement, all consignment sales can now optionally be reviewed, and the consignment rate or cost can be updated through a ReST API and online screen in Sales Audit before they are interfaced to Merchandising. This can be useful for retailers who may wish to apply a consignment rate/cost that is different than what is defined for an item/location in Merchandising for selected sales transactions: for example, consignment items sold to an employee or application of a different consignment rate based on sub-locations within a large department store.
The sales RTLOG has been enhanced to support the optional capture of an item-level consignment rate or consignment cost at the point of sale. Retailers who wish to include sub-location or other details can capture the same in any of the reference fields at the item level in the RTLOG and the same will be made available for an optional rate review process, wherein the retailer can review consignment sales information and make updates to the consignment cost or consignment rate.
A new system option, Consignment Review Days, has been introduced which controls whether consignment rate review is being used. If this option is retained at the default value of zero, then it implies that consignment rate review is not being used, and consignment sales will be extracted from Sales Audit to Merchandising without any delay as long the transaction is error-free. In the event of the Consignment Review Days being non-zero, it implies that rate review is intended, and consignment sales will be held back in Sales Audit for a review window that will end once the review process is complete or a duration equal to that specified in the Review Days parameter has elapsed. During this review window, an external process can review consignment sales records and make updates to the consignment rate/amount based on additional information available on the transaction.
Consignment sales can be identified by a Consignment Review Status column on the Transaction Item table (accessible via RDS) that will carry a status of Pending for Consignment Item records pending review. A new Consignment Sales update service has been provided to allow an external system/process to update the cost/rate on the consignment sales records. This rate/cost adjustment can also be performed via Sales Audit online screens. Once the transaction is reviewed, it is marked Complete and extracted for publishing to Merchandising. Wherever adjustments have been made to the consignment rate/cost, these adjusted values will be extracted to Merchandising and used for Transaction Data postings. In the event of adjusted values not being available, consignment cost/rate passed from the POS will be extracted to Merchandising and used for Transaction Data posting. In the event of neither the adjusted values nor values from POS being available, the consignment rate/cost definitions in Merchandising will be used for the transaction data postings and invoicing.
Consignment Vendor Invoicing
Two new options have been introduced at the supplier site level to control whether Merchandising will generate purchase orders and invoices for consignment sales.
-
Consignment Ordering Indicator – This indicates whether Merchandising will generate purchase orders for consignment sales. If set to Yes, Merchandising will aggregate consignment sales at the level/duration specified by the existing consignment invoicing options and create purchase orders. The purchase orders created will now additionally carry item details and will be accompanied by system-created shipment records corresponding to the quantities on the order. If this option is not set, then Merchandising will not create purchase orders automatically for consignment sales. All purchase order Transaction Data postings corresponding to consignment sales will be made available in a staging table (accessible via RDS). Retailers can opt to roll up this data in any manner desirable and create purchase orders accordingly in Merchandising via any order creation means (Online screen, Webservice, Spreadsheet Upload, and so on). These purchase orders will need to be marked as Consignment Vendor Orders during creation. Upon approval of these orders, they will be auto-closed, and shipments auto-created with the corresponding order quantities. Like Consignment Vendor Orders, the system will also support interfacing Consignment Vendor Returns (RTV) into Merchandising.
-
Self-Invoicing Indicator – This indicates whether consignment purchases should be self-invoiced by the retailer, or vendor invoiced. If checked (Set to Self-Invoicing), then Merchandising will create invoice records for consignment orders, which will be interfaced into Invoice Matching. These are matched invoices and do not require further matching in Invoice Matching. If self-invoicing is not opted for, then purchase orders and shipments created in Merchandising will require matching in Invoice Matching against a vendor invoice. Invoice Matching will support the entry of consignment invoices for such vendors. Documents created against consignment returns (Credit Note Request/Debit Memo) will always be generated in Merchandising irrespective of the setting of the Self Invoicing Indictor, and hence will not need processing in ReIMCS.
By default, both the above defined options will be selected for all supplier sites existing in the system, thus ensuring that consignment purchase orders and invoices will continue to be created in Merchandising in line with the existing self-invoicing functionality.
Steps to Enable
System Options
To use the Consignment Rate Review feature, the Sales Audit system options, Consignment Sales Review Period should be set to a value greater than zero.
| Attribute Name | New or Update? | Attribute Description | Default Value |
|---|---|---|---|
|
Consignment Sales Review Period |
New |
This column indicates the review window in hours from the point of consignment sales staging within which an external system can review and update the consignment rate/amount for the staged consignment items. If the consignment rate/amount is not reviewed within this time window, then the record will be eligible for getting exported to other system automatically with the existing consignment rate/amount. Default value zero indicates that the Rate Review Process is not used. Valid values are whole numbers between 0 to 960 (hours i.e., 40 days). |
0 (zero) |
Batch Schedule
| Process Name | Process Type | New or Updated? | Delivered |
|---|---|---|---|
|
CONSIGNMENT_BILLING_PROCESS |
Nightly |
New |
Enabled |
Integration
| API Name | Change Type | Integration | Field Name | Change Description |
|---|---|---|---|---|
|
/ResaReSTServices/services/private/Resa/consignmentSalesTransactionUpdate |
New |
REST Service |
Transaction information with the adjusted values of Consignment Rate/Unit Cost. |
New service that provides the ability to accept Adjusted values of Consignment Rate and Consignment unit cost for consignment data staged for Rate Review. |
|
/ResaReSTServices/services/private/Resa/salesService |
Update |
REST Service |
Consignment Rate, Consignment Unit Cost |
Added fields Consignment Rate and Consignment Unit Cost in the item details node. |
|
/purchaseOrder/details/create |
Update |
REST Service |
orig_ind |
Updated the length of orig_ind to 2 and updated validation to allow the orig ind value for consignment vendor order (12). |
|
/purchaseOrder/details/update |
Update |
REST Service |
orig_ind |
Updated the length of orig_ind to 2 and updated validation to allow the orig ind value for consignment vendor order (12). |
|
/purchaseOrder/expenses/create |
Update |
REST Service |
orig_ind |
Updated the length of orig_ind to 2 and updated validation to allow the orig ind value for consignment vendor order (12). |
|
/purchaseOrder/expenses/update |
Update |
REST Service |
orig_ind |
Updated the length of orig_ind to 2 and updated validation to allow the orig ind value for consignment vendor order (12). |
|
/purchaseOrder/hts/assessments/create |
Update |
REST Service |
orig_ind |
Updated the length of orig_ind to 2 and updated validation to allow the orig ind value for consignment vendor order (12). |
|
/purchaseOrder/hts/assessments/update |
Update |
REST Service |
orig_ind |
Updated the length of orig_ind to 2 and updated validation to allow the orig ind value for consignment vendor order (12). |
|
/purchaseOrder/hts/create |
Update |
REST Service |
orig_ind |
Updated the length of orig_ind to 2 and updated validation to allow the orig ind value for consignment vendor order (12). |
|
/purchaseOrder/hts/update |
Update |
REST Service |
orig_ind |
Updated the length of orig_ind to 2 and updated validation to allow the orig ind value for consignment vendor order (12). |
|
/purchaseOrder/lettersOfCredit/create |
Update |
REST Service |
orig_ind |
Updated the length of orig_ind to 2 and updated validation to allow the orig ind value for consignment vendor order (12). |
|
/purchaseOrder/lettersOfCredit/update |
Update |
REST Service |
orig_ind |
Updated the length of orig_ind to 2 and updated validation to allow the orig ind value for consignment vendor order (12). |
|
/purchaseOrders/create |
Update |
REST Service |
orig_ind |
Updated the length of orig_ind to 2 and updated validation to allow the orig ind value for consignment vendor order (12). |
|
/purchaseOrders/update |
Update |
REST Service |
orig_ind |
Updated the length of orig_ind to 2 and updated validation to allow the orig ind value for consignment vendor order (12). |
|
/foundation/suppliers/create |
Update |
REST Service |
Generate Consignment Order, Generate Self Invoicing |
New indicator fields added to the request payload . Valid values are Y (Yes) and N (No). |
|
/foundation/suppliers/update |
Update |
REST Service |
Generate Consignment Order, Generate Self Invoicing |
New indicator fields added to the request payload. Valid values are Y (Yes) and N (No). |
|
/inventory/returnsToVendor/manage |
Update |
REST Service |
Consignment Vendor RTV |
New field added to the request payload. This value will determine whether the RTV is Consignment Vendor RTV or not. Valid values are Y(Yes) and N(No). |
|
/services/foundation/supplier |
Update |
REST Service |
Generate Consignment Order, Generate Self Invoicing |
Indicator fields added to the response payload. |
|
Order Subscription API |
Update |
RIB Message |
orig_ind |
Field width increased to 12 to allow value for Consignment Vendor Order. |
|
RTV Subscription API |
Update |
RIB Message |
Consignment Vendor RTV |
New field added to the subscription object. Valid values are Y(Yes) and N(No). |
|
Vendor Publication API |
Update |
RIB Message |
Generate Consignment Order, Generate Self Invoicing |
New fields added to the publication object. Valid values are Y(Yes) and N(No) |
|
Vendor Subscription API |
Update |
RIB Message |
Generate Consignment Order, Generate Self Invoicing |
New fields added to the subscription object. Valid values are Y(Yes) and N(No). |
Codes
| Code Type | Code Type Description | Code | Code Description | New or Updated? | Delivered |
|---|---|---|---|---|---|
|
CSRP |
Consignment Sales Review Period Unit |
D |
Days |
New |
Disabled |
|
CSRP |
Consignment Sales Review Period Unit |
H |
Hours |
New |
Disabled |
|
OROR |
Order Origin |
12 |
Consignment Vendor Order |
Update |
Enabled |
|
RTVO |
RTV Origin Indicator |
CONVEN |
Consignment Vendor RTV |
New |
Enabled |
RDS/DAS Updates
| Application Table | DAS/RDS Table or View | Change Type | Change Description |
|---|---|---|---|
|
SA_TRAN_ITEM |
DAS_WV_SA_TRAN_ITEM |
Update |
Added columns CONSIGNMENT_RATE CONSIGNMENT_UNIT_COST CONSIGNMENT_REVIEW_STATUS CONSIGNMENT_STAGED_DATETIME ADJUSTED_CONSIGNMENT_RATE ADJUSTED_CONSIGNMENT_UNIT_COST |
|
SA_TRAN_ITEM |
RDS_WV_SA_TRAN_ITEM |
Update |
Added columns CONSIGNMENT_RATE CONSIGNMENT_UNIT_COST CONSIGNMENT_REVIEW_STATUS CONSIGNMENT_STAGED_DATETIME ADJUSTED_CONSIGNMENT_RATE ADJUSTED_CONSIGNMENT_UNIT_COST |
|
SA_TRAN_ITEM_REV |
DAS_WV_SA_TRAN_ITEM_REV |
Update |
Added columns CONSIGNMENT_RATE CONSIGNMENT_UNIT_COST CONSIGNMENT_REVIEW_STATUS CONSIGNMENT_STAGED_DATETIME ADJUSTED_CONSIGNMENT_RATE ADJUSTED_CONSIGNMENT_UNIT_COST |
|
SA_TRAN_ITEM_REV |
RDS_WV_SA_TRAN_ITEM_REV |
Update |
Added columns CONSIGNMENT_RATE CONSIGNMENT_UNIT_COST CONSIGNMENT_REVIEW_STATUS CONSIGNMENT_STAGED_DATETIME ADJUSTED_CONSIGNMENT_RATE ADJUSTED_CONSIGNMENT_UNIT_COST |
|
SA_SYSTEM_OPTIONS |
DAS_WV_SA_SYSTEM_OPTIONS |
Update |
Added column CONSIGNMENT_SALES_REVIEW_PERIOD |
|
SA_SYSTEM_OPTIONS |
RDS_WV_SA_SYSTEM_OPTIONS |
Update |
Added column CONSIGNMENT_SALES_REVIEW_PERIOD |
|
SUPS |
DAS_WV_SUPS |
Update |
Added the new GEN_CONSGIN_ORDER and GEN_CONSIGN_INVOICE column in the views |
|
SUPS |
RDS_WV_SUPS |
Update |
Added the new GEN_CONSGIN_ORDER and GEN_CONSIGN_INVOICE column in the views. |
|
CONSIGNMENT_BILLING |
DAS_WV_CONSIGNMENT_BILLING |
New |
New DAS view based on table Consignment_billing table. |
|
CONSIGNMENT_BILLING |
RDS_WV_CONSIGNMENT_BILLING |
New |
New RDS view based on table Consignment_billing table. |
Consignment Pricing Enhancements for Pricing Cloud Service
This cloud service update will extend the consignment functionality to support price event creation and management based on the primary supplier ownership and pricing control at the item/location level. Based on the new parameter in Merchandising, Pricing Control, which would be defined at the primary supplier/location level for consignment/concession items, price events can either be created and managed by the retailer or the supplier.
For supplier-controlled items/locations, price events are expected to be defined in an external system and interfaced to the Pricing Cloud Service for approval/execution and communication to downstream systems such as an external POS. The functionality is only supported when not using the Oracle Retail Xstore Suite. The existing screens and interfaces in Pricing Cloud Service are enhanced to distinguish between supplier-controlled and retailer-controlled items/locations based on their inventory status (Owned and Concession/Consignment), and restrict price creation/management for item/locations which are managed by the suppliers via online screens in Pricing Cloud Service. The existing inbound APIs are modified to have additional parameters to allow external systems to define whether a price event is for supplier-controlled, or retailer-controlled items. Based on this parameter, Pricing Cloud Service processes interfaced events, ensuring the primary supplier ownership and pricing control set up at the item/location are validated. The existing setup for consignment/concession item and their price management will not be impacted by this change.
The system option, Allow Supplier-Controlled Pricing, has been added in Merchandising to indicate whether supplier-controlled pricing for Consignment/Concession stock is enabled in MFCS and RPCS. For approved items, the pricing control attribute can be edited via Ownership Change functionality in Merchandising. The new Ownership Change type has been introduced - 'Update Pricing Control' which will allow changing the pricing control attribute for Consignment/Concession at item/supp/country and/or item/supplier/country/location levels. For existing change types, Owned to consignment and Owned to concession, the pricing control attribute has been added in the ownership change screen. A new validation has been added in the Ownership Change screen and the Process Scheduled Ownership Change Data Batch to prevent ownership change for item/supplier/country or item/supplier/country/location when there exists - worksheet, rejected, submitted or approved price changes, clearances and promotion offers with effective date on or after the effective date of the ownership change. With this enhancement, the existing screens, Induction API, Ownership Change batches and inbound/outbound interfaces in Merchandising have been modified to support creation, management and communication of the pricing attribute at item-supplier-country and item-supplier-country-location levels.
Steps to Enable
The Allow Supplier-Controlled Pricing system option should be set to Y(Yes) to turn the feature ON.
Integration
| API Name | Change Type | Integration | Field Name | Change Description |
|---|---|---|---|---|
|
BDI_PRICING_PROMO_OFFER |
Update |
BDI |
GENERATED_BY PRIMARY_SUPPLIER PURCHASE_TYPE |
Added these 3 new columns to PROMO_OFFER_OUT table. |
|
Clearance Induction |
Update |
REST Service |
primarySupplier purchaseType generatedBy |
Added these 3 new fields |
|
Price Change Induction |
Update |
REST Service |
primarySupplier purchaseType generatedBy |
Added these 3 new fields |
|
Promotion Induction |
Update |
REST Service |
primarySupplier purchaseType generatedBy |
Added these 3 new fields |
|
RPM_NEW_ITEM_LOCATION |
Update |
Table-based |
GENERATED_BY PRIMARY_SUPPLIER PURCHASE_TYPE |
Added these 3 new columns to staging table RPM_ITEM_LOC_WS |
|
V2/item/promo |
Update |
REST Service |
primarysupplier purchasetype generatedby |
Added these 3 new fields in REST response for v2 |
Consignment Pricing Enhancements for Merchandising Cloud Service
This cloud service update extends the consignment functionality to support price event creation and management based on the primary supplier ownership and pricing control at the item/location level. Based on the new parameter in Merchandising, Pricing Control, which is defined at the primary supplier/location level for consignment/concession items, price events can either be created and managed by the retailer or the supplier. For supplier-controlled item/locations, price events are expected to be defined in an external system and interfaced to the Pricing Cloud Service (RPCS) for approval/execution and communication to downstream systems such as an external POS. The functionality is only supported when not using the Oracle Retail Xstore Suite.
The existing screens and interfaces in RPCS have been enhanced to distinguish between supplier-controlled and retailer-controlled items/locations based on their inventory status (Owned and Concession/Consignment) and restrict price creation/management for item/locations, which are managed by the suppliers through online screens in RPCS. Additional parameters, item/location primary supplier and purchase types, have been added to the existing inbound APIs in RPCS to allow external systems to define whether a price event is for supplier-controlled, or retailer-controlled items. Based on these parameters, RPCS can process an interfaced event, ensuring the primary supplier ownership and pricing control set up at item/location are validated. Existing setup for consignment/concession item and their price management is not impacted by this change.
The system option, Allow Supplier-Controlled Pricing, has been added in Merchandising to indicate whether supplier-controlled pricing for Consignment/Concession stock is enabled in MFCS and RPCS.
For approved items, the pricing control attribute can be edited through the Ownership Change functionality in Merchandising. A new Ownership Change type has been introduced, 'Update Pricing Control', which enables changing the pricing control attribute for Consignment/Concession at the item/supp/country and/or item/supplier/country/location levels. For existing change types, Owned to consignment and Owned to concession, the pricing control attribute has been added in the ownership change screen. A new validation has been added in the Ownership Change screen and the Process Scheduled Ownership Change Data Batch to prevent ownership change for item/supplier/country or item/supplier/country/location when there exists worksheet, rejected, submitted or approved price changes, clearances and promotion offers with an effective date on or after the effective date of the ownership change.
With this enhancement, the existing screens, Induction API, Ownership Change batches and inbound/outbound interfaces in Merchandising have been modified to support the creation, management, and communication of the pricing attribute at the item-supplier-country and item-supplier-country location levels.
Steps to Enable
System Options
The Allow Supplier-Controlled Pricing system option should be set to Y(Yes) to turn the feature ON.
| Attribute Name | New or Update? | Attribute Description | Default Value |
|---|---|---|---|
|
Allow Supplier Controlled Pricing |
New |
Determines whether supplier controlled pricing for consignment/concession items is allowed within the Merchandising and Pricing solutions. When this indicator is set Yes(Y) then the pricing control attribute can be provided for consignment/concession items when their pricing is managed by supplier in Pricing. |
N |
Integration
| API Name | Change Type | Integration | Field Name | Change Description |
|---|---|---|---|---|
|
/foundation/suppliers/create |
Update |
REST Service |
Default Pricing Control |
New parameter Default Pricing Control has been added with valid values as R(Retailer) and S(Supplier). |
|
/item/locations/create |
Update |
REST Service |
Pricing Control |
New parameter Pricing Control has been added with valid values as R(Retailer) and S(Supplier). |
|
/item/locations/update |
Update |
REST Service |
Pricing Control |
New parameter Pricing Control has been added with valid values as R(Retailer) and S(Supplier). But it will be considered as ignored. |
|
/items/create |
Update |
REST Service |
Pricing Control |
New parameter Pricing Control has been added with valid values as R(Retailer) and S(Supplier). It is added at country of sourcing and location level. |
|
/item/suppliers/create |
Update |
REST Service |
Pricing Control | New parameter Pricing Control has been added with valid values as R(Retailer) and S(Supplier). |
| /item/supplier/countries/create |
Update |
REST Service |
Pricing Control | New parameter Pricing Control has been added with valid values as R(Retailer) and S(Supplier). |
| /item/supplier/countries/update |
Update |
REST Service |
Pricing Control | New parameter Pricing Control has been added with valid values as R(Retailer) and S(Supplier). |
| /item/supplier/country/locations/update |
Update |
REST Service |
Pricing Control | New parameter Pricing Control has been added with valid values as R(Retailer) and S(Supplier). |
|
/SupplierBean/SupplierService |
Update |
SOAP Service |
Pricing Control | New parameter Pricing Control has been added with valid values as R(Retailer) and S(Supplier). |
|
Item Subscription API |
Update |
RIB Message |
Pricing Control | New parameter Pricing Control has been added with valid values as R(Retailer) and S(Supplier). |
|
Vendor Subscription API |
Update |
RIB Message |
Pricing Control | New parameter Pricing Control has been added with valid values as R(Retailer) and S(Supplier). |
|
Item Publication API |
Update |
RIB Message |
Pricing Control | New parameter Pricing Control has been added with valid values as R(Retailer) and S(Supplier). |
|
Vendor Publication API |
Update |
RIB Messag |
Pricing Control | New parameter Pricing Control has been added with valid values as R(Retailer) and S(Supplier). |
|
/services/foundation/item |
Update |
REST Service |
Pricing Control |
New attribute Pricing Control has been added in JSON payload returned by GET service. Existing customers who want use the Consignment Pricing functionality can choose to execute MERCHAPI_DATA_REBUILD_ADHOC_JOB to update the cache table with new JSON payload format which includes pricing control field. |
|
/services/foundation/item/location |
Update |
REST Service |
Pricing Control |
New attribute Pricing Control has been added in JSON payload returned by GET service. Existing customers who want use the Consignment Pricing functionality can choose to execute MERCHAPI_DATA_REBUILD_ADHOC_JOB to update the cache table with new JSON payload format which includes pricing control field. |
Codes
| Code Type | Code Type Description | Code | Code Description | New or Updated? | Delivered |
|---|---|---|---|---|---|
|
OCTP |
Ownership Change Type |
OC6 |
Update Pricing Control |
Update |
Enabled |
|
PRCT |
Pricing Control |
R |
Retailer |
New |
Enabled |
|
PRCT |
Pricing Control |
S |
Supplier |
New |
Enabled |
RDS/DAS Updates
| Application Table | DAS/RDS Table or View | Change Type | Change Description |
|---|---|---|---|
|
SYSTEM_OPTIONS |
RDS_WV_SYSTEM_OPTIONS |
Update |
Added column ALLOW_SUPPLIER_CONTROLLED_PRICING. |
|
SYSTEM_OPTIONS |
DAS_WV_SYSTEM_OPTNS |
Update |
Added column ALLOW_SUPPLIER_CONTROLLED_PRICING. |
|
ITEM_SUPP_COUNTRY |
RDS_WV_ITEM_SUPP_COUNTRY |
Update |
Added column PRICING_CONTROL. |
|
ITEM_SUPP_COUNTRY_LOC |
DAS_WV_ITEM_SUPP_COUNTRY_LOC |
Update |
Added column PRICING_CONTROL. |
|
OWNERSHIP_CHANGE_DETAIL_ITEM |
RDS_WV_OWNERSHIP_CHANGE_DETAIL_ITEM |
Update |
Added column PRICING_CONTROL. |
|
ITEM_SUPP_COUNTRY |
DAS_WV_ITEM_SUPP_COUNTRY |
Update |
Added column PRICING_CONTROL. |
|
ITEM_SUPP_COUNTRY_LOC |
RDS_WV_ITEM_SUPP_COUNTRY_LOC |
Update |
Added column PRICING_CONTROL. |
|
V_ITEM_SUPP_COUNTRY_LOC |
RDS_WV_V_ITEM_SUPP_COUNTRY_LOC |
Update |
Added column PRICING_CONTROL. |
|
OWNERSHIP_CHANGE_DETAIL_ITEM |
DAS_WV_OWNERSHIP_CHG_DTL_ITEM |
Update |
Added column PRICING_CONTROL. |
|
OWNERSHIP_CHANGE_DETAIL_LOC |
RDS_WV_OWNERSHIP_CHANGE_DETAIL_LOC |
Update |
Added column PRICING_CONTROL. |
|
OWNERSHIP_CHANGE_DETAIL_LOC |
DAS_WV_OWNERSHIP_CHG_DTL_LOC |
Update |
Added column PRICING_CONTROL. |
Decimal Precision Attribute for Xstore
This cloud service update will include the integration of an item-level attribute called Decimal Precision from Merchandising to Xstore. The XStore Office Cloud Service (XOCS) solution uses an item level attribute (QTY_SCALE) that specifies the decimal precision of accuracy when weighing a product having a unit of measure (UOM) other than Each (EA), but this attribute was not previously available from Merchandising. To support the central management of this attribute, a corresponding attribute named ‘Decimal Precision’ has been added as part of the unit of measure (UOM) definition within Merchandising. This attribute will be available in the Item Location Publish ReST API for Omnichannel. This is expected to be populated for all items having their Selling Unit of Measure (UOM Class) other than Quantity.
Steps to Enable
This new field will be automatically present for new/updated records in the JSON cache, but the refresh batch needs to be run in case the field is required for old data. Also, the new Admin API template needs to be used for viewing the data.Integration
| API Name | Change Type | Integration | Field Name | Change Description |
|---|---|---|---|---|
|
/services/foundation/omnichannel/item/itemlocation |
Update |
REST Service |
SellingUomDecimalPrecision |
Added SellingUomDecimalPrecision |
RDS/DAS Updates
| Application Table | DAS/RDS Table or View | Change Type | Change Description |
|---|---|---|---|
|
UOM_CLASS |
DAS_WV_UOM_CLASS |
Update |
Added column DECIMAL_PRECISION. |
|
UOM_CLASS |
RDS_WV_UOM_CLASS |
Update |
Added column DECIMAL_PRECISION. |
Modification in Item Location Subscription API
This cloud service update will include enhanced Item Location subscription ReST service with following additional fields: 1. Measure of each 2. Measure of price 3. Unit of measure of price 4. Primary variant 5. Primary cost pack 6. Inbound handling days 7. Ranged indicator 8. Costing location
Integration
| API Name | Change Type | Integration Type | Field Name | Change Description |
|---|---|---|---|---|
|
/services/item/locations/create |
Update |
REST Service |
Multiple Fields. |
Modified to include additional fields in item location create ReST service. Below Fields has been included. 1. Measure of each 2. Measure of price 3. Unit of measure of price 4. Primary variant 5. Primary cost pack 6. Inbound handling days 7. Ranged indicator 8. Costing location |
|
/services/item/locations/update |
Update |
REST Service |
Multiple Fields. |
Modified to include additional fields in item location update ReST service. Below Fields has been included. 1. Measure of each 2. Measure of price 3. Unit of measure of price 4. Primary variant 5. Primary cost pack 6. Inbound handling days 7. Ranged indicator 8. Costing location |
Enhanced Expense Profile Functionality to Allow Ability to Push a Profile Down to Items
This cloud service update will include the enhanced expense profile functionality that provides the ability to push expense profile shipping routes and/or associated expenses down to items. Five different push methods can be used.
Summary of Each Push Method
-
Replace Item Profile (RP) – This method will delete all item shipping routes and associated expenses, and then add the expense profile's shipping routes and expenses to the item.
-
Add Missing Shipping Routes (AR) – This method will preserve any existing item expense shipping routes and expenses as is, and add any shipping routes and associated expenses from the expense profile that are missing in item expenses.
-
Add Missing Profile (AP) – This method will push an entire Supplier Country level expense profile (all shipping routes and expenses), Supplier Zone level expense profile, Partner Country level e pense profile, Partner Zone Level expense profile or Country expense profile, down to items only where no country level or zone level item expenses exist.
-
Merge Shipping Routes / Replace Expenses (MRRE) – The method will retain existing item expense shipping routes that are not on the expense profile as is. For shipping routes on the expense profile, if the shipping route exists in item expenses, delete associated item expenses and add all expenses from the expense profile for that shipping route; if the shipping route does not exist in item expenses, add the missing route and associated expenses from the expense profile.
-
Merge Shipping Routes / Add Missing Expenses (MRAE) – The method will retain existing item expense shipping routes that are not on the expense profile as is. For shipping routes on the expense profile, if the shipping route exists in item expenses, leave existing expenses as is and add any missing expenses from the expense profile for that shipping route; if the shipping route does not exist in item expenses, add the missing route and associated expenses from the expense profile.
Batch Schedule
| Process Name | Process Type | New or Updated? | Delivered |
|---|---|---|---|
|
BATCH_EXPPROF_ITMCOSTUPD_PROCESS |
Nightly |
New |
Enabled |
Codes
| Code Type | Code Type Description | Code | Code Description | New or Updated? | Delivered |
|---|---|---|---|---|---|
|
EPPM |
Expense Profile Push Methods to Downstream Entities |
AP |
Add Missing Profile |
New |
Enabled |
|
EPPM |
Expense Profile Push Methods to Downstream Entities |
AR |
Add Missing Shipping Routes |
New |
Enabled |
|
EPPM |
Expense Profile Push Methods to Downstream Entities |
MRAE |
Merge Shipping Routes / Add Missing Expenses |
New |
Enabled |
|
EPPM |
Expense Profile Push Methods to Downstream Entities |
MRRE |
Merge Shipping Routes / Replace Expenses |
New |
Enabled |
|
EPPM |
Expense Profile Push Methods to Downstream Entities |
RP |
Replace Item Profile |
New |
Enabled |
RDS/DAS Updates
| Application Table | DAS/RDS Table or View | Change Type | Change Description |
|---|---|---|---|
|
DAS_WV_EXP_PROF_HEAD |
DAS_WV_EXP_PROF_HEAD |
Update |
Updated to include new column UPDATE_ITEMS_IND column mirroring value from EXP_PROF_HEAD.UPDATE_ITEMS_IND which is the expense profile push method to be applied. |
Ability to Re-default Expense Profiles at Item-Supplier/Item-Supplier-Country Level
This cloud service update will include the enhanced expense profile functionality. Previously, when creating item/supplier or item/supplier/country relationships via Item Induction or online, if expenses are not defaulted at the time of creation, there isn’t an option to default them at a later point. With this enhancement, rather than performing a push from the expense profile which will update all items, a new option has been added that provides a way to selectively choose which items get refreshed with related expense profiles. A new button ‘Default Expense Profiles’ has been added to the Item Suppliers and Item Supplier Countries screens to enable users to refresh expense profiles for a given item/supplier or item/supplier/country. A similar capability has been added to the Item Induction.
Enhanced Purge Process for Purchase Order to now Consider Active Invoices
This cloud service update includes the enhanced purge process for purchase orders. This process now considers if there are active invoices before purging a purchase order.
Fiscal Document Receiving Enhancements
Functional Overview
Oracle Retail Fiscal Management Cloud Service (RFMCS) is designed to help retailers manage their fiscal and compliance requirements related to fiscal documents. RFMCS is intended to enable compliance for retailers that operate in regions with complex taxes and regulations that affect the supply chain and financial-related features in the scope of Retail Merchandising Cloud Services.
RFMCS has specific groups of features with different purposes:
-
Fiscal Data Management is a set of features related to the creation and maintenance of fiscal attributes and their association with items and entities. The attributes are used by RFMCS to support legal and taxation requirements.
-
Fiscal Document Management is the set of features that support the receiving and generation of fiscal documents based on a pre-defined business workflow. This module introduces the workflow-based development concept in which the business rules applied to a transaction processing flow is defined and kept separated from the components that execute the flow. With this approach, users have total visibility of what is being processed in the system, the exchange of messages, the errors, and validations.
-
Foundation Data has a group of functionalities related to the setup of the application including user restrictions/assignments, data loading, and transaction codes setup.
Fiscal Data Management
New Fiscal classification and reclassification data loading option
A new option to download and upload the fiscal classification and reclassification templates will make it easier to select specific items or entities, download their fiscal attribute association, and perform bulk maintenance.
Fiscal Document Management
RFMCS's main objective is the management of fiscal documents and the support to fiscal document receiving and generation.
Fiscal Document Receiving Workflow
The Fiscal Document Receiving feature is meant to support the receiving of fiscal documents associated with a transaction and is based on a pre-defined processing workflow. The first workflow available in RFMCS is the Purchase Order Fiscal Document Receiving (POFDR) of Brazilian NFe model 55.
The POFDR workflow allows the receiving of fiscal documents via REST service or the direct upload via a screen. As part of this workflow, there will be the following capabilities:
-
Unicity validations
-
Tax validations
-
PO matching
-
Discrepancy identification
-
Generation of return document requests
-
Fiscal ledger updates
-
Tax account data
-
Financial posting data generation
-
Electronic Manifestation and NFe status verification
-
Inventory update in MFCS
-
Fiscal document data exported to RDS
Fiscal Ledger
RFMCS enables a fiscal document-based lot control, meant to support balance requirements for taxes, returns, and anything that requires the control of fiscal inventory at the item/location level. The fiscal ledger consists of controlling all entries and exits of items with fiscal documents at the location level.
Fiscal Ledger will be fed with fiscal document information as part of a transaction workflow processing. It is possible to perform manual updates in the Fiscal Ledger via screen.
Foundation Data
RFMCS foundation data enables the configuration of user access to locations and workflows, the setup and maintenance of transaction codes to be applied during fiscal document processing flows, and the data loading of setup data.
User Assignment
Fiscal Document Management features will have location-level restrictions applied to users. A user from one location may not have access to documents from other locations. In addition to location-level restrictions, the User Assignment will allow workflow level restrictions as well.
Manage Transaction Codes
Transaction codes are used to provide consolidated and calculated data used to generate financial postings. In RFMCS the transaction codes can be configured, including the calculation and application rules. A set of pre-configured transaction codes is available for each workflow supported.
Data Loading
Setup data configuration via download and upload is available in RFMCS.
The setup data templates available are:
-
Item Fiscal Attributes
-
Entity Fiscal Attributes
-
Fiscal Ledger
-
Transaction Codes
-
User Assignments
-
General Ledger Accounts
-
General Ledger Cross Reference
Batch Schedule
| Process Name | Process Type | New or Updated? | Delivered |
|---|---|---|---|
|
RFM_FDR_MANIFEST_ADHOC_PROCESS |
Ad Hoc |
New |
Enabled |
|
RFM_FDR_MANIFEST_CYCLE_PROCESS |
Cyclic |
New |
Enabled |
Integration
| API Name | Change Type | Integration | Field Name | Change Description |
|---|---|---|---|---|
|
RFMCS Flex Integration Service - Create |
New |
Rest Service |
New Payload |
New Service |
|
RFMCS NFE Manifest Service |
New |
Rest Service |
New Payload |
New Service |
|
RFMCS Flex Integration Service - Get |
New |
Rest Service |
New Payload |
New Service |
Codes
| Code Type | Code Type Description | Code | Code Description | New or Updated? | Delivered |
|---|---|---|---|---|---|
|
DSEC |
Fiscal Document Sequences Extension Code |
END_CO |
End consumer indicator |
New |
Enabled |
|
DSEC |
Fiscal Document Sequences Extension Code |
MOD |
Brazilian NFE Model Code |
New |
Enabled |
|
DSEC |
Fiscal Document Sequences Extension Code |
SERIE |
Brazilian NFE Serial Code |
New |
Enabled |
|
DSEC |
Fiscal Document Sequences Extension Code |
WORKFL |
Workflow Code |
New |
Enabled |
|
DSET |
Fiscal Document Sequences Extension Type |
01 |
Filter |
New |
Enabled |
|
DSET |
Fiscal Document Sequences Extension Type |
02 |
Attribute |
New |
Enabled |
|
DSMV |
Document Sequences Mod Values |
55 |
Brazilian NFE Model 55 |
New |
Enabled |
|
DSMV |
Document Sequences Mod Values |
65 |
Brazilian NFE Model 65 |
New |
Enabled |
|
FWFL |
Fiscal Workflows |
CNFDG |
Complementary NF Document Generation |
New |
Enabled |
|
FWFL |
Fiscal Workflows |
COFDG |
Customer Order Fiscal Document Generation |
New |
Enabled |
|
FWFL |
Fiscal Workflows |
CRNDG |
Credit Note Document Generation |
New |
Enabled |
|
FWFL |
Fiscal Workflows |
DNIDG |
Direct NF Inbound Document Generation |
New |
Enabled |
|
FWFL |
Fiscal Workflows |
DNODG |
Direct NF Outbound Document Generation |
New |
Enabled |
|
FWFL |
Fiscal Workflows |
FFIDG |
Free Form Inbound Document Generation |
New |
Enabled |
|
FWFL |
Fiscal Workflows |
FFODG |
Free Form Outbound Document Generation |
New |
Enabled |
Privileges
| Priv Name | Change Type | Priv Description | Parent Duty |
|---|---|---|---|
|
DOWNLOAD_DATA_PRIV |
New |
A privilege for downloading data via the Download Setup Data screen |
RFM_FOUNDATION_INQUIRY_DUTY |
|
VIEW_TRANSACTION_CODES_PRIV |
New |
A privilege for viewing transaction codes data via the Manage Transaction Codes screen |
RFM_FOUNDATION_INQUIRY_DUTY |
|
VIEW_USER_ASSIGNMENTS_PRIV |
New |
A privilege for viewing user assignments for location and workflow via the User Assignment screen |
RFM_FOUNDATION_INQUIRY_DUTY |
|
VIEW_DOCUMENT_SEQUENCES_PRIV |
New |
A privilege for viewing document sequence setups via the Manage Document Sequence screen. |
RFM_FOUNDATION_INQUIRY_DUTY |
|
VIEW_FISCAL_ATTRIBUTES_PRIV |
New |
A privilege for viewing fiscal attributes via the Item Attributes and Entity Attributes screens. |
RFM_FISCAL_ATTRIBUTES_INQUIRY_DUTY |
|
VIEW_FISCAL_DOCUMENTS_PRIV |
New |
A privilege for viewing fiscal documents in both Manage Document Receiving and Manage Document Issuing screens, as well as in the Fiscal Document detail screen. |
RFM_FISCAL_DOCUMENTS_INQUIRY_DUTY |
|
MAINTAIN_TRANSACTION_CODES_PRIV |
New |
A privilege for maintaining transaction codes data via the Manage Transaction Codes screen. Users with this privilege must also have the View Transaction Codes Priv |
RFM_FOUNDATION_MGMT_DUTY |
|
MAINTAIN_USER_ASSIGNMENTS_PRIV |
New |
A privilege for create and maintain user assignments for location and workflow via the User Assignment screen. Users with this privilege must also have the View User Locations Priv. |
RFM_FOUNDATION_MGMT_DUTY |
|
MAINTAIN_DOCUMENT_SEQUENCES_PRIV |
New |
A privilege for creating and maintain document sequence setups via the Manage Document Sequence screen. Users with this privilege must also have the View Document Sequence Priv |
RFM_FOUNDATION_MGMT_DUTY |
|
UPLOAD_DATA_PRIV |
New |
A privilege for uploading data via the Upload Setup Data screen. Users with this privilege must also have the Download Data Priv |
RFM_FOUNDATION_MGMT_DUTY |
|
VIEW_FISCAL_LEDGER_PRIV |
New |
A privilege for viewing fiscal ledger records via the Fiscal Ledger Balance Sheet screen |
RFM_FISCAL_DOCUMENTS_INQUIRY_DUTY |
|
MAINTAIN_FISCAL_ATTRIBUTES_PRIV |
New |
A privilege for creating and maintaining fiscal attributes via the Item Attributes and Entity Attributes screens. Users with this privilege must also have the View Fiscal Attributes Priv. |
RFM_FISCAL_ATTRIBUTES_MGMT_DUTY |
|
MAINTAIN_FISCAL_DOCUMENTS_PRIV |
New |
A privilege to create and maintain fiscal documents in Fiscal Document Management screens. Users with this privilege must also have the View Fiscal Documents Priv. |
RFM_FISCAL_DOCUMENTS_MGMT_DUTY |
|
MAINTAIN_FISCAL_LEDGER_PRIV |
New |
A privilege for creating fiscal ledger records via the Fiscal Ledger Balance Sheet screen. Users with this privilege must also have the View Fiscal Ledger Priv. |
RFM_FISCAL_DOCUMENTS_MGMT_DUTY |
Duties
| Duty Name | Change Type | Duty Description | Child Duty | Base Role |
|---|---|---|---|---|
|
RFM_FISCAL_ATTRIBUTES_INQUIRY_DUTY |
New |
A duty for searching for and viewing fiscal attributes via the Item Attributes and Entity Attributes screens. |
FISCAL_ANALYST_JOB |
|
|
RFM_FISCAL_DOCUMENTS_INQUIRY_DUTY |
New |
A duty for searching for and viewing fiscal documents. |
FISCAL_ANALYST_JOB |
|
|
RFM_FOUNDATION_INQUIRY_DUTY |
New |
A duty for searching and viewing RFM foundation data |
FISCAL_ANALYST_JOB |
|
|
RFM_FISCAL_ATTRIBUTES_MGMT_DUTY |
New |
A duty for creating and maintaining fiscal attributes via the Item Attributes and Entity Attributes screens. This duty is an extension of the Fiscal Attribute Inquiry Duty. |
RFM_FISCAL_ATTRIBUTES_INQUIRY_DUTY |
FISCAL_MANAGER_JOB |
|
RFM_FOUNDATION_MGMT_DUTY |
New |
A duty for maintaining RFM foundation data. This duty is an extension of the Foundation Inquiry Duty. |
RFM_FOUNDATION_INQUIRY_DUTY |
FISCAL_MANAGER_JOB |
|
RFM_FISCAL_DOCUMENTS_MGMT_DUTY |
New |
A duty for managing fiscal document processing workflows within RFMCS. This duty is an extension of the Fiscal Document Inquiry Duty. |
RFM_FISCAL_DOCUMENTS_INQUIRY_DUTY |
FISCAL_MANAGER_JOB |
|
RFM_GLOBAL_MENU_DUTY |
New |
This is a duty that is used to grant access to the Fiscal Management link in the Application Navigator in the sidebar menu. There are no privileges within the duty, associating this duty to a role will grant access |
RFM_APPLICATION_ADMINISTRATOR_JOB |
RDS/DAS Updates
| Application Table | DAS/RDS Table or View | Change Type | Change Description |
|---|---|---|---|
|
RFM_ERROR_KEYS_TL |
RDS_WV_RFM_ERROR_KEYS_TL |
New |
This is the translation table for RFM_ERROR_KEYS_TL table. |
|
RFM_ERROR_KEYS |
RDS_WV_RFM_ERROR_KEYS |
New |
This table contains one row for each error message used in the system. |
|
RFM_FDM_ATTRIB_ITEMLOC |
RDS_WV_RFM_FDM_ATTRIB_ITEMLOC |
New |
This table contains the fiscal attributes associated at item-location level. |
|
RFM_FDM_ATTRIB_ITEMSUPP |
RDS_WV_RFM_FDM_ATTRIB_ITEMSUPP |
New |
This table contains the fiscal attributes associated at item-supplier level. |
|
RFM_FDM_ATTRIB_ORDCUST |
RDS_WV_RFM_FDM_ATTRIB_ORDCUST |
New |
This table contains the fiscal attributes associated to customer orders. |
|
RFM_FDM_ATTRIB_ITEM |
RDS_WV_RFM_FDM_ATTRIB_ITEM |
New |
This table contains the fiscal attributes associated to items. |
|
RFM_FDM_ATTRIB_LOCATION |
RDS_WV_RFM_FDM_ATTRIB_LOCATION |
New |
This table contains the fiscal attributes associated to locations. |
|
FM_FDM_ATTRIB_PARTNER |
RDS_WV_RFM_FDM_ATTRIB_PARTNER |
New |
This table contains the fiscal attributes associated to partners. |
|
RFM_FDM_ATTRIB_SUPPLIER |
RDS_WV_RFM_FDM_ATTRIB_SUPPLIER |
New |
This table contains the fiscal attributes associated to suppliers. |
|
RFM_WFLW_SET_VAR |
RDS_WV_RFM_WFLW_SET_VAR |
New |
This table contains the variables used to define workflow process sequence exceptions. |
|
RFM_FLX_DOC_FDR_HIST |
RDS_WV_RFM_FLX_DOC_FDR_HIST |
New |
This table holds data related to fiscal documents generated by RFM. |
|
RFM_WFLW_SET_ACTION |
RDS_WV_RFM_WFLW_SET_ACTION |
New |
This table holds data related to screenActions. |
|
RFM_FLX_DOC_FDR_KEYS_HIST |
RDS_WV_RFM_FLX_DOC_FDR_KEYS_HIST |
New |
This table holds key data related to a fiscal document. |
|
RFM_CODE_DETAIL |
RDS_WV_RFM_CODE_DETAIL |
New |
This table holds the code details for a code type |
|
RFM_CODE_DETAIL_TL |
RDS_WV_RFM_CODE_DETAIL_TL |
New |
This table holds the code details translation. |
Ability to Specify Best Terms Date
This cloud service update includes the option to manually enter or edit the best terms date. If the best terms date is entered, it will overide the determination of the date during the best terms calculation. The best terms date is the basis date which is passed to the financial system with the best terms (payment terms).
New Get Rest Service to Retrieve Item Location Weekly Sales History
This cloud service update includes a new Rest service to query item_loc_hist table that takes several query parameters and provides all the fields in the table as response payload. This table has extremely high volume and this service requires at least one of the following parameters to be provided - EOW Date, Item or Location.
Integration
| API Name | Change Type | Integration Type | Field Name | Change Description |
|---|---|---|---|---|
|
Get Item Location Weekly Sales (MerchIntegrations/services/sales/itemLocation/weekly) |
New |
REST Service |
New Payload |
New Rest Service |
RDS/DAS Table Updates
New columns to hold external reference ID are added in Organization Unit and Language tables and the same has been replicated into RDS and DAS. Similarly, a newly introduced table to hold the mapping for vendor type code is also added to RDS and DAS for replication.
DAS/RDS Updates
| Application Table | DAS/RDS Table or View | Change Type | Change Description |
|---|---|---|---|
|
ORG_UNIT |
DAS_WV_ORG_UNIT |
Update |
Added new external_ref_id field. |
|
LANG |
DAS_WV_LANG |
Update |
Added new external_ref_id field. |
|
ORG_UNIT |
RDS_WV_ORG_UNIT |
Update |
Added new external_ref_id field. |
|
LANG |
RDS_WV_LANG |
Update |
Added new external_ref_id field. |
|
VENDOR_TYPE_CODE_MAPPING |
DAS_WV_VENDOR_TYPE_CODE_MAPPING |
New |
New DAS view to expose VENDOR_TYPE_CODE_MAPPING table. |
|
VENDOR_TYPE_CODE_MAPPING |
RDS_WV_VENDOR_TYPE_CODE_MAPPING |
New |
New RDS view to expose VENDOR_TYPE_CODE_MAPPING table. |