16 Items Management
This section describes the common functionality and configurations available for Items Management.
Implementation Overview
This section provides an implementation overview.
Functionality
The Items Management module gives the possibility to create and maintain Items (either by UI or by file export/import) and publishes them to MFCS.
Status Workflow
Figure 16-1 Items Management Status Workflow
Items Management follows a workflow path, and the status can change depending on:
- The user permissions
- The current Status of the Item
Item Status:
- Draft – Draft is the initial status of an item is when the creation process starts. At any time during in Draft a user can save and continue later, staying in draft status. When submitting if enough information is available to submit the Item Status can be changed to New, if the user does not have approval permissions, or directly to Approved Status (via Processing).
- New – New is the status of an item with a minimum amount of information to be created is in. In this status an Item can be Approved to send the item to MFCS or Rejected to change the status of the item to Rejected.
- Rejected – In Rejected Status an item can still be updated and submitted back to New Status, to restart the approval process if needed.
- Approved – An Approved Item is an Item that exists in MFCS and is complete to be used on all processes in SPCH.
- Changes Proposed – Changes Proposed is a status used when a user without approve permissions updates an Approved Item. During this Status the changes can be approved and then sent to MFCS or Rejected and the changes are discarded.
- Processing – Processing Status is an interim status while an item is being interfaced with MFCS. Since the integration is not near real-time. The item is not editable whilst on this status. Once the integration is successful, the item will move to Approved Status. If during Processing an issue is encountered that is a recoverable error (data validations for example), the Item Status will be moved to the previous Status to allow the Item data to be fixed before processing the item again, if the issue found is non recoverable the Item will move to Error Status instead.
- Error – Error Status is used when an issue is encountered while interfacing the Item into MFCS and when in this status technical support will be required to understand what caused the error.
Configuration
This section describes the configurations.
POM Configuration
Batch scheduler details with all batches, dependencies and frequencies can be downloaded following the steps in the Supply Chain Hub Frameworks section.
Figure 16-3 Items Management Batch Schedule Overview
Similar Items
Items Management enables the possibility of adding views configurations so they can return possible similar the new item being created and stop the item approval process until the changes are merged in the existing item, or the data that makes the new item look similar is changed.
To support it the System Parameter NEW_ITEM_MERGE_RECOM can be configured as Y and during the submit process the views configured in table ORCV_SPIM_SIMILAR_ITEMS_VIEWS are executed to insert possible matches in table ORCV_SPIM_SIMILAR_ITEMS. After executing the views with success and any rows are inserted, the process does not continue to approval and a new validation issue is raised to notify the user that they may have duplicates and must act.
When the user enters the new or existing item with possible duplicates a new button is displayed that opens a popup for the user to choose which of the existing duplicate items to merge the changes to. After confirming the new item is deleted, the changes merged into existing item and the existing item is sent for approval.
Database Objects
Views
The views that can be created must return the following two fields so that the process can use them to filter and insert in similar items tables. The views must be added to ORCV_SPIM_SIMILAR_ITEMS_VIEWS.
| Column | Data Type | Notes |
|---|---|---|
| EXISTING_ITEM | VARCHAR2(25) | This fields contains the approved MFCS item that has a duplicated barcode in a SPIM unapproved item. |
| NEW_ITEM | VARCHAR2(25) | This fields contains the not approved SPIM item that has a duplicated barcode in a MFCS approved item. |
Other Cloud Services Configuration
This section describes implementation details that must be reviewed from Oracle Retail Merchandising System perspective.
System Options
To ensure that Items can correctly integrate with MFCS some configurations in the MFCS configuration table CORESVC_ITEM_CONFIG must be made. To allow Items Management to explode Item level 1 information to lower levels the following parameters must be set to N in CORESVC_ITEM_CONFIG.
| PARAMETER | VALUE |
|---|---|
| CASCADE_UDA_DETAILS | N |
| CASCADE_IUD_ITEM_SUPP_COUNTRY | N |
| CASCADE_IUD_ISC_DIMENSIONS | N |
| CASCADE_IUD_ISMC | N |
| ISC_UPDATE_ALL_LOCS | N |
| ISC_UPDATE_ALL_CHILD_LOCS | N |
| CASCADE_VAT_ITEM | N |
| CASCADE_IIM_DETAILS | N |
| CASCADE_IUD_ITEM_SUPPLIER | N |
| CASCADE_ITEM_HTS | N |
| CASCADE_ITEM_HTS_ASSESS | N |
| CASCADE_ITEM_EXPENSES | N |
| CASCADE_ITEM_TICKET | N |
| CASCADE_ITEM_SEASONS | N |
| CASCADE_ITEM_UPCHRG | N |
Furthermore, two of the configurations must be aligned with their corresponding configurations in the Items Management System Parameters in table ORCV_SYSTEM_PARAMETERS with area CONFIG and module Items Management.
| MFCS CORESVC_ITEM_CONFIG | ORCV ORCV_SYSTEM_PARAMETERS |
|---|---|
| MAX_ITEM_RESV_QTY | RESERVE_ITEM_MAX_AMOUNT |
| MAX_ITEM_EXPIRY_DAYS | RESERVE_ITEM_MAX_EXPIRY |
Note:
MAX_ITEM_RESV_QTY must be configured with at least value 10.Reason Codes
Whenever a user updates an Item that is already approved, they need to specify a reason for that update. These reasons are identified by reason codes which are defined at system level. Below you can find the list of the codes available, the sequence and their description.
The codes are defined in the ORCV_CODE_HEAD and ORCV_CODE_DETAIL tables.
UDAs
Items Management uses some attributes that are specific to it but still need to be integrated with MFCS, to do so specific user-defined attributes need to be created in MFCS. The user attribute identifier on the table below is an implementation example.
These attributes are specified below.
| UDA ID | UDA DESCRIPTION | UDA TYPE | UDA VALUE | UDA VALUE DESCRIPTION | SINGLE VALUE INDICATOR |
|---|---|---|---|---|---|
| 9001 | ORCV Item Integration Revision | FF (Free Form) | NA | NA | Y |
| 9002 | On Sale Date | DT (Date) | NA | NA | Y |
| 9003 | Off Sale Date | DT (Date) | NA | NA | Y |
| 9004 | Stock Available | LV (List of Values) | 1 | Y | Y |
| 9004 | Stock Available | LV (List of Values) | 2 | N | Y |
Note:
Important to note is that these UDAs need to be aligned with the following System Parameters in ORCV_SYSTEM_PARAMETERS, if they need to have a different ID.| AREA | PARAMETER | DESCRIPTION | VALUE 1 | VALUE 2 |
|---|---|---|---|---|
| CONFIG | ITEM_INT_REVISION_UDA | UDA that must be used exclusively in the integration process. | 9001 | NA |
| CONFIG | EXCLUDED_UDA | UDAs that should be excluded from the user assigning to an item. | ON_SALE_DATE | 9002 |
| CONFIG | EXCLUDED_UDA | UDAs that should be excluded from the user assigning to an item. | OFF_SALE_DATE | 9003 |
| CONFIG | EXCLUDED_UDA | UDAs that should be excluded from the user assigning to an item. | STOCK_AVAIL | 9004 |
Other Implementation Considerations
This section describes Item Management implementation considerations.
Notifications and Alerts
Items Management uses Events Framework to inform users about events occurred by generating notifications and alerts. Below is the list of Notifications and Alerts available. The notifications are implemented through the Rule Engine Framework documented in the Supply Chain Hub Frameworks section.
Notifications
This section describes the notifications for Items Management.
ORCV_SPIM_EVENT_ITEM_RECOVERY
Notification triggered when user approves an item and the item fails the approval.
| Property | Value |
|---|---|
| Event Name | SPIM_EVENT_ITEM_RECOVERY |
| Event Type | ORCV_SPIM_EVENT_ITEM_RECOVERY |
| Description | An error(s) occurred during the item(s) approval process. |
| Trigger | UI action |
| Target Users | User that approved the item. |
ORCV_SPIM_EVENT_PROP_CHANG_EXIST_ITEM
Notification triggered when a change propose is submitted.
| Property | Value |
|---|---|
| Event Name | SPIM_EVENT_PROP_CHANG_EXIST_ITEM |
| Event Type | ORCV_SPIM_EVENT_PROP_CHANG_EXIST_ITEM |
| Description | Items with new changes proposed by Retailer |
| Trigger | UI/S9T action |
| Target Users | All Retailer users with permissions for the item department or primary supplier will receive the notification. |
ORCV_SPIM_EVENT_SUBM_NEW_ITEM
Notification triggered when a new item is submitted.
| Property | Value |
|---|---|
| Event Name | SPIM_EVENT_SUBM_NEW_ITEM |
| Event Type | ORCV_SPIM_EVENT_SUBM_NEW_ITEM |
| Description | New Items submitted |
| Trigger | UI/S9T action |
| Target Users | All Retailer users with permissions for the item department or primary supplier will receive the notification. |
Alerts
ORCV_SPIM_EVENT_ITEMS_PENDING
Email sent with the List of Items that were submitted 'x' days ago and still in 'New' or 'Changes Proposed'.
| Property | Value |
|---|---|
| Event Name | SPIM_EVENT_ITEMS_PENDING_ACTION |
| Event Type | ORCV_SPIM_EVENT_ITEMS_PENDING |
| Alert Type | |
| Description | Items with actions pending |
| Trigger | Rules Engine Batch with key: SPIM_ITEM_EVT_PND |
| Target Users | Retail Contact for the item Suppliers |
Custom Validations
The application performs validations by implementing Custom Validation Groups of the Custom Validations Framework described in the Supply Chain Hub Frameworks section. The groups are listed below.
SPIM_ITEM_APPROVE
Triggered when the user approves an Item by UI or S9T.
All validation functions for this Custom Validation Group are available in ORCV_SPIM_MGMT_ITEM_VAL package.
| FUNCTION | VALIDATION | SEQ NO |
|---|---|---|
| VALIDATE_HEADER | Validate item header data. | 1 |
| VALIDATE_IMPORT | Validate item import data. | 2 |
| VALIDATE_IMAGE | Validate item image data. | 3 |
| VALIDATE_PACKITEM | Validate pack item data. | 4 |
| VALIDATE_PRICING | Validate item pricing data. | 5 |
| VALIDATE_RANGING | Validate item ranging data. | 6 |
| VALIDATE_SUPPLIER | Validate item supplier data. | 7 |
| VALIDATE_BUY_ATTR | Validate item buy attributes. | 8 |
| VALIDATE_DIFFS | Validate item diffs. | 9 |
SPIM_ITEM_SUBMIT
Triggered when the user submits an Item by UI or S9T.
All validation functions for this Custom Validation Group are available in ORCV_SPIM_MGMT_ITEM_VAL package.
| FUNCTION | VALIDATION | SEQ NO |
|---|---|---|
| VALIDATE_HEADER | Validate item header data. | 1 |
| VALIDATE_IMPORT | Validate item import data. | 2 |
| VALIDATE_IMAGE | Validate item image data. | 3 |
| VALIDATE_PACKITEM | Validate pack item data. | 4 |
| VALIDATE_PRICING | Validate item pricing data. | 5 |
| VALIDATE_RANGING | Validate item ranging data. | 6 |
| VALIDATE_SUPPLIER | Validate item supplier data. | 7 |
| VALIDATE_DIFFS | Validate item diffs data | 8 |
| VALIDATE_BUY_ATTR | Validate item buy attributes. | 9 |
Custom Flex Attributes
This application supports three different types of Custom Flex Attributes (CFA): Item Master, Item Supplier and Item Supplier Country. For each CFA there is a corresponding System Parameter to allow their use. For S9T, the worksheet must also be enabled.
Before importing CFA attribute configuration from MFCS, make sure the entities defined in ORCV_CFA_EXT_ENTITY match the entities on the MFCS side. To import the CFAs run the import batch. Afterwards the attributes will be synchronized every time a user accesses that CFA group in the UI. The import only needs to be run if there are any changes in the group sets or groups and the details are available in the Supply Chain Hub Frameworks section.
Specific Batch Configuration
This section describes specific batch configurations.
Check Status Batch
The Check Status batch is used to validate if an item was successfully published into MFCS.
- Job: ORCV_SPIM_CHECK_STATUS_JOB
- Frequency: Nightly
- Dependency: None
- Inter Scheduler Dependency: None
Batch configuration table: ORCV_BATCH_CONFIG
| COLUMN NAME | DEFAULT VALUES |
|---|---|
| PROGRAM_NAME | ORCV_SPIM_CHECK_STATUS_JOB |
| MAX_CHUNK_SIZE | 1000 |
| MAX_CONCURRENT_THREADS | 4 |
| RETRY_LOCK_ATTEMPTS | 3 |
| RETRY_WAIT_TIME | 3 |
| RETRY_MAX_ATTEMPTS_COUNT | 3 |
| RETRY_ORDERED | N |
| RETRY_IND | N |
Codes
Certain operations require codes to define the options available at system level. Below you can find the list of code types available.
The codes are defined in the ORCV_CODE_HEAD and ORCV_CODE_DETAIL tables.
| CODE TYPE | CODE TYPE DESCRIPTION |
|---|---|
| IDTF | SPIM Display Type field code, to be used on the ORCV_SPIM_SELL_ATTR table. |
| IMCB | SPIM item Location Calculation Basis, to be used on the Add Locations popup screen. |
| IMEL | SPIM error level. To be used in the ORCV_SPIM_ITEM_ERRORS table. |
| IMIT | SPIM item type, to be used on the dashboard screen. |
| IMLT | SPIM item Location Type, to be used on the Add Locations popup screen. |
| IMRR | SPIM revision reason code, to be used on the ORCV_SPIM_ITEM_REV_CTRL table. |
| IMRS | SPIM revision status, to be used on the ORCV_SPIM_ITEM_REV_CTRL table. |
| IMST | SPIM item status, to be used on the dashboard screen. |
Templates
Items Management uses a spreadsheet download and upload process, developed as part of the Retail Supply Chain Hub Frameworks, for creation, maintenance, and extraction of data. To support these processes there are some templates which must be configured, and several configurations should be reviewed as part of the implementation.
Template SPIM Item Data
Table 16-1 Template key: SPIM_ITEM_DATA
| ACTION TYPE | ROLE NAME |
|---|---|
| Download | ORCV_SPIM_ITEM_APPR_JOB |
| Download | ORCV_SPIM_ITEM_EDIT_JOB |
| Download | ORCV_SPIM_ITEM_VIEW_JOB |
| Download Blank | ORCV_SPIM_APP_JOB |
| Upload | ORCV_SPIM_ITEM_APPR_JOB |
| Upload | ORCV_SPIM_ITEM_EDIT_JOB |
Table 16-2 Worksheet Item Header
| ACTION | MANDATORY CELLS / FIELDS | NOTES |
|---|---|---|
| Create |
Item or VPN, Item type, Supplier, Vendor Description, Item Description, Inventory, Orderable, Sellable, Department ID, Class ID, Subclass ID, Standard UOM |
Creates a new Item. When the user has Edit permissions, it creates the Item with status New. When the user has Approve permissions, it creates the Item with status Approved. If other column or columns are mandatory, the enrichment process will populate the proper default values. |
| Update |
Item or VPN Updatable: vendor description, Item description, brand ID, season, on sale date, off sale date, recommend retail price |
Updates the Item with the new details. When a user with Edit permissions does the upload, if the previous status was New or Reject, the Item status will be New. If the previous status was Approved or Change Proposed, the status will be Change Proposed. When a user with Approve permissions does the upload, the Item status will be Approved. |
| Approve | Item or VPN | Approves items, if in Change Proposed approves the latest changes. |
| Reject | Item or VPN | Rejects all changes. |
Table 16-3 Worksheet Item SKU
| ACTION | MANDATORY CELLS / FIELDS | NOTES |
|---|---|---|
| Create |
Item parent or VPN parent, Item SKU or Primary VPN SKU, Diff Value 1 Diff Value 2 Diff Value 3 Diff Value 4 |
Adds item skus to the style (item parent). The diff values are mandatory if exists diff groups or diff ids associated to the item parent. |
| Update |
Item parent or VPN parent, Item SKU Updatable: primary VPN SKU, primary barcode, primary barcode type |
Updates the item SKU of the Item parent associated. |
Table 16-4 Worksheet Item Barcodes
| ACTION | MANDATORY CELLS / FIELDS | NOTES |
|---|---|---|
| Create |
Item SKU or VPN SKU, Barcode, Barcode Type, Primary Barcode |
Adds item barcode to the SKU. |
| Update |
Item SKU or VPN SKU Updatable: barcode, barcode type, primary barcode |
Updates the barcode of the associated SKU item. |
| Delete | Item SKU or VPN SKU | Deletes the barcode of the associated SKU item. |
Table 16-5 Worksheet Pack Components
| ACTION | MANDATORY CELLS / FIELDS | NOTES |
|---|---|---|
| Create |
Item Parent or VPN Parent, Component, VPN Component, Qty |
Adds item component to pack. |
Table 16-6 Worksheet Item Supplier Country
| ACTION | MANDATORY CELLS / FIELDS | NOTES |
|---|---|---|
| Create |
Item or VPN, Supplier, Primary Supplier, Origin Country, Primary Country, Unit cost or Purchase rate, Purchase Type |
Adds supplier country to the Item. Unit cost or Purchase rate are mandatory depending on Purchase type selected. |
| Update |
Item or VPN Updatable: lead time, pickup lead time, supplier pack size, packing method, min order qty, max order qty |
Updates information related to the supplier country associated. |
Table 16-7 Worksheet Item Supplier Country Dim
| ACTION | MANDATORY CELLS / FIELDS | NOTES |
|---|---|---|
| Create |
Item or VPN, Supplier, Origin Country, Dim Object |
Adds supplier country dimension to the Item. |
| Update |
Item or VPN Updatable: item length, item width, item height, LWH UOM, weight, WEIGHT UOM |
Updates information related to the supplier country dimensions associated. |
Table 16-8 Worksheet Item Buying Attributes
| ACTION | MANDATORY CELLS / FIELDS | NOTES |
|---|---|---|
| Create |
Item or VPN, UDA Type, UDA ID, UDA Date or UDA FF/LOV |
Adds buying attributes to the Item. UDA Date or UDA FF/LOV depends on UDA Type selected. |
Table 16-9 Worksheet Item Selling Attributes
| ACTION | MANDATORY CELLS / FIELDS | NOTES |
|---|---|---|
| Create |
Item or VPN, Attribute, Value |
Adds selling attributes to the Item. |
| Update |
Item or VPN Updatable: value |
Updates the value of the attribute associated. |
Table 16-10 Worksheet Item Import
| ACTION | MANDATORY CELLS / FIELDS | NOTES |
|---|---|---|
| Create |
Item or VPN, Origin country, Import country, HTS |
Adds HTS to the Item. |
Table 16-11 Worksheet Item Range
| ACTION | MANDATORY CELLS / FIELDS | NOTES |
|---|---|---|
| Create |
Item or VPN, Location, Status |
Adds range to the Item. In case of the Purchase Type exceptions, it’s necessary to fill the purchase type, if different from owned, then must fill the cost per unit or purchase rate (only one can be filled). |
| Update |
Item or VPN Updatable: status |
Updates the status of the location. |
Table 16-12 Worksheet Item Retail by Zone
| ACTION | MANDATORY CELLS / FIELDS | NOTES |
|---|---|---|
| Create |
Item or VPN, Zone ID, Retail price |
Adds retail price per zone ID to the Item. |
Table 16-13 Worksheet Item Image
| ACTION | MANDATORY CELLS / FIELDS | NOTES |
|---|---|---|
| Create |
Item or VPN, Image name, Image address, Primary image, Display priority |
Adds image to the Item. |
| Update |
Item or VPN Updatable: primary image |
Updates the primary image indicator. |
Template SPIM Supplier Default
Table 16-14 Template Key: SPIM_SUPP_DFLT
| ACTION TYPE | ROLE NAME |
|---|---|
| Download | ORCV_SPIM_ITEM_APPR_JOB |
| Download | ORCV_SPIM_ITEM_EDIT_JOB |
| Download | ORCV_SPIM_ITEM_VIEW_JOB |
| Download Blank | ORCV_SPIM_APP_JOB |
| Upload | ORCV_SPIM_ITEM_APPR_JOB |
Table 16-15 Worksheet Supplier Defaults
| ACTION | MANDATORY CELLS / FIELDS | NOTES |
|---|---|---|
| Create |
Supplier, Entity – Attribute, Value 1, Default Value |
Creates a new attribute (selected from the entity-attribute list) for the supplier. Value 2, value 3 and value 4 can be filled according to selected entity attribute. |
| Update |
Supplier, Entity – Attribute Updatable: value 1, value 2, value 3, value 4, default value |
Updates the values and default value indicator for the entity-attribute to supplier related. |
| Delete |
Supplier, Entity – Attribute, Value 1, Value 2, Value 3, Value 4 |
Deletes the entity-attribute for the supplier. |
Table 16-16 Worksheet Supplier Merch Mappings
| ACTION | MANDATORY CELLS / FIELDS | NOTES |
|---|---|---|
| Create |
Supplier, At least one of the following fields: Brand or Ref 1, Dept |
Creates a new mapping between brand and/or supplier references (1 to 5) to the Merch Hierarchy. |
| Update |
Supplier, Brand and/or Ref (1 to 5) |
Updates the Merch Hierarchy mapping (department, class, subclass). |
| Delete |
Supplier, Brand and/or Ref (1 to 5) |
Deletes the Merch Hierarchy mapping. |
Table 16-17 Worksheet Supplier Selling Attributes
| ACTION | MANDATORY CELLS / FIELDS | NOTES |
|---|---|---|
| Create |
Supplier, Selling attribute ID, Dept, Value, Required |
Adds selling attributes values to the supplier. |
| Update |
Supplier, Selling attribute ID, Dept Updatable: value, required |
Updates the supplier selling attributes. |
| Delete |
Supplier, Selling attribute ID, Dept |
Deletes the supplier selling attributes. |
Codes
Certain operations require codes to define the options available at system level. Below you can find the list of code types available.
The codes are defined in the ORCV_S9T_CODE_HEAD and ORCV_S9T_CODE_DETAIL tables.
| CODE TYPE | CODE TYPE DESCRIPTION |
|---|---|
| IHAC | Item Management Header - Item Data Action |
| IHIT | Item Management - Item Type |
| IDAC | Item Management - Item Data Action |
| IDUT | Item Management - Item UDA Type |
| IDID | Item Management - Item Detail Action |
| IPAC | Item Management - Pack Component Action |
| IHIY | Item Management - Indicator LOV (Yes) |
| SDAC | Supplier Defaults - Action |
| SDEA | Supplier Defaults - Entity Attribute |
References
Items Management also uses the Queries module to enable communication between retailer and supplier users, details about Queries are available in the Supply Chain Hub Frameworks section. It also has the ability to attach documents to Items, if the user type is Retailer the attachments will be available for all Retailer and Supplier users of the Item and if the user is Supplier the attachments will be available for Retailer users and Supplier users with access to the same supplier.
Operations
This section describes Inventory and Sales operations.
Integration by Module
Figure 16-4 Items Management Integration by Module
| STEP | DESCRIPTION |
|---|---|
| 0 | RSCH Data Access of MFCS data |
| 1 | Item Induction Java Services checks if Item Management has Items to be published and produces ODS files to be consumed by MFCS Item Induction Job. |
| 2 | Item Induction Java Services sends produced files to Integration File Transfer. |
| 3 | Integration File Transfer publishes files to MFCS File Transfer Services (FTS) or MFCS shared folder (depending on configuration). |
| 4 | Items Management calls Upload Download Java Service to transform files, depending on the request details, Upload Download Java Service might need to callback to Item Management to get more details. |
| 5 | Item Loc Java Services checks if Item Management has Items to be published and generates xItemLoc RIB messages to be integrated with MFCS. |
| 6 | Item Loc Java Services calls RIB-EXT Rest with generated xItemLoc messages. |
| 7 | Item Management calls Items MFCS ReST Merch Integration request for Item IDs. |
| 8 | Item Reserve Java Service calls MFCS ItemManagementService with a Rest request to request Item IDs. |
| 9 | Items Integration calling Diff Group and Diff Rest endpoint of MFCS ReST Merch Integration to create Diffs and Diff Details. |
| 10 | Event Alert Java Service checks if there are alerts to be triggered. |
Batch by Module
This section describes the batch by module.
Check Item Status Batch
Authentication Method: OAuth2
BaseURL: https://<BASE_URL>/ords/mfcs/orcv/merch/itemsmanagement/batch/checkstatus/<URL_PATH>
| URL PATH | REQUEST METHOD | REQUEST BODY | AFFECTED TABLES |
|---|---|---|---|
| start | POST |
{ "cycleName": "", "flowName": "", "processName": "", "async": "", "executionId": "", "jobName": "ORCV_SPIM_CHECK_STATUS_JOB", "agentExecutionId": "", "parameters": "" } |
ORCV_BATCH_STATUS_CONTROL ORCV_THREAD_CONTROL ORCV_BATCH_AUDIT_STATUS ORCV_SPIM_ITEM_RESERVE_XREF ORCV_SPIM_ITEM_HEADER |
| restart | POST |
{ "cycleName": "", "flowName": "", "processName": "", "async": "", "executionId": <EXEC_ID>, "jobName": "ORCV_SPIM_CHECK_STATUS_JOB", "agentExecutionId": "", "parameters": "" } |
ORCV_BATCH_STATUS_CONTROL ORCV_THREAD_CONTROL ORCV_BATCH_AUDIT_STATUS ORCV_SPIM_ITEM_RESERVE_XREF ORCV_SPIM_ITEM_HEADER |
| log | GET |
URL query parameters: /log?jobName=ORCV_SPIM_CHECK_STATUS_JOB &executionId=<EXEC_ID>&logDate=YYYY-DD-MM |
N/A |
| kill | POST |
{ "cycleName": "", "flowName": "", "processName": "", "async": "", "executionId": <EXEC_ID>, "jobName": "ORCV_SPIM_CHECK_STATUS_JOB", "agentExecutionId": "", "parameters": "" } |
ORCV_BATCH_STATUS_CONTROL ORCV_THREAD_CONTROL ORCV_BATCH_AUDIT_STATUS ORCV_SPIM_ITEM_RESERVE_XREF ORCV_SPIM_ITEM_HEADER |
| status | GET |
URL query parameters: /status?jobName=ORCV_SPIM_CHECK_STATUS_JOB &executionId=<EXEC_ID>&logDate=YYYY-DD-MM |
N/A |
| status/all | GET |
URL query parameters: /status?<EXEC_IDs> |
N/A |
| config | GET | Empty | N/A |
Alerts
Items Management sends alerts using the Rules Engine Framework documented in the Supply Chain Hub Frameworks section, below is the list of rules batch-based rules required to be executed in batch scheduler.
| EVENT NAME | RULE | JOB |
|---|---|---|
| ORCV_SPIM_EVENT_ITEMS_PENDING | SPIM_ITEM_EVT_PND | ORCV_SPIM_ITEM_EVT_PND_JOB |
Service by Module
This section describes the Service by Module.
Recalculate Defaults
This service will be used to update the default weights for the default mappings between the defined entities based on configuration defined in ORCV_SPIM_MERCH_MAP_CFG_WEIGHT.
Rest URL: /ords/mfcs/orcv/merch/itemsmanagement/recalculate/defaults
| Weight | |
|---|---|
| Url Path | <Rest URL>/weight |
| Request Method | PUT |
| Sample Request Body | NA |
| Sample Success Message |
{ "msg": "Success" } Response Code: 200 (Success) |
| Sample Failure Message |
{ "statusMsg": "Processed with error.", "errorMsg": "Invalid Column" } Response Code: 400 (Bad Request) |
| Affected Tables | ORCV_SPIM_MERCH_MAP_CFG_WEIGHT |
Reference
Please refer to the Supply Chain Hub Frameworks section for operational details on integration and item reserve services.