Oracle Retail Merchandising

Replenishment Attribute Update Overview

February 2020 | Release 19.0.x

Copyright © 2020, Oracle and/or its affiliates
Disclaimer
This document in any form, software or printed matter, contains proprietary information that is the exclusive property of
Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle software
license and service agreement, which has been executed and with which you agree to comply. This document and
information contained herein may not be disclosed, copied, reproduced or distributed to anyone outside Oracle without
prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any
contractual agreement with Oracle or its subsidiaries or affiliates.
This document is for informational purposes only and is intended solely to assist you in planning for the implementation
and upgrade of the product features described. It is not a commitment to deliver any material, code, or functionality, and
should not be relied upon in making purchasing decisions. The development, release, and timing of any features or
functionality described in this document remains at the sole discretion of Oracle.
Due to the nature of the product architecture, it may not be possible to safely include all features described in this document
without risking significant destabilization of the code.
.

1 Replenishment Attribute Update Overview] Release 19.0.x

Copyright © 2020, Oracle and/or its affiliates
TABLE OF CONTENTS
Disclaimer 1
Replenishment Attribute Update 3
Custom Templates 3
Creating New Attributes 3
Downloading Existing Attributes 4
Manual Upload 4
Validations 5
Validations on Create 6
Validations on Update 10
Validations on Delete 11
Error Resolution 11

Appendix A: Data Creation Examples 12

Create an Activation for an Item/Store 12
Create an Update for a Class 14

Appendix B: Configuration Parameters 16

Replenishment Induction Configuration (REPL_INDUCT_CONFIG) 16

2 Replenishment Attribute Update Overview] Release 19.0.x

Copyright © 2020, Oracle and/or its affiliates
Replenishment Attribute Update
In order to manage significant volumes of data relevant to different aspects of business, a lot of retailers have built
processes to upload updates from external systems to increase the overall efficiency. One such instance is Oracle Retail
Replenishment Optimization, which is used to optimize attributes that are directly linked with the replenishment process.
There is also a frequent requirement to support mass updates of attributes within Merchandising.
Given these use cases, Merchandising will support replenishment attributes loaded manually from a spreadsheet, in bulk,
using an xml version of the template layout, or via web service. Most of this paper focuses on the manual spreadsheet
upload and download processes. However, the bulk and web service processes also have similar validations as described in
this document.

Custom Templates
Similar to the functionality added for items and purchase orders, replenishment attribute management via the spreadsheet
method supports configurable templates. The default ‘base’ template provided with the solution will be discussed in detail in
this paper and includes all the attributes that are available to be updated, but it is equally important to understand that there
is a built in capability to create your own templates that can be used for specific purposes and help tailor this capability to
your business.
For example, you may choose to have different templates for activating items on replenishment versus updating existing
replenishment attributes; or different templates based on the replenishment method. Creating one or more custom
templates allows you to create a spreadsheet template showing only those attributes that you want users to update, and also
supports a defaulting feature to default certain attributes that are set commonly across items and locations for that
particular template.
For more details on this configuration process, see the Spreadsheet Template Management White Paper.

Creating New Attributes

If you wish to activate a new item/location combination on replenishment or create a new scheduled update of an
item/location that is currently on replenishment, the recommended first step is to download a blank template – either the
appropriate custom template or the base template, whichever is relevant. To do that, access the Download Blank Template
link under Data Loading in the task list. First select the type to download – item, cost change, and purchase order templates
are also available for download in this screen – and then select the appropriate template. This will allow you to save a
version of the blank spreadsheet template locally. Once you have filled out the template with the updates required, you are
ready to upload it from the location you have saved it into in Merchandising.

3 Replenishment Attribute Update Overview] Release 19.0.x

Copyright © 2020, Oracle and/or its affiliates
Downloading Existing Attributes
Any existing replenishment attributes can be exported, either from scheduled updates or the current replenishment
attributes for an item/location, rather than starting with a blank template. For this purpose, the Merchandising task list
contains the Download Replenishment Attributes and Download Scheduled Updates links under the Replenishment folder.
You can search for and download records into your selected template directly, which can then be saved locally. Starting in
this way will provide you with the information on the existing attribute configuration to use as a starting point to make your
updates. All the rows that are returned in your search will be part of the data extracted.

Once you have the required data queried into the search results, you can click on the Download button to initiate the export.
The pop up displayed will allow you to select the template into which the data will be extracted. The Process Description field
will default to a value based on the timestamp, but it can be updated by the user for tracking the download process in case
of any issues.

Manual Upload
Once the data has been updated into the spreadsheet, the next step will be to upload this into Merchandising. This is done
by selecting the Upload Replenishment Attributes option in the Merchandising task list. To do this, you will have to select the
template that you used for creating the spreadsheet and then select the location where your file has been saved. Finally, a
process name is given to allow tracking of the progress of the upload based on the activity timestamp after it is submitted;
but this can be edited, if required.

4 Replenishment Attribute Update Overview] Release 19.0.x

Copyright © 2020, Oracle and/or its affiliates
Upon clicking the Upload button, the information will be processed by Merchandising in the background. If there are any
errors, then a notification will be sent to you to review the issue and correct the data. In case of no errors, no notification will
be sent, but the status can still be validated by accessing the Data Loading  Review Status option in the task list.

Validations
The key validations that will be performed while uploading replenishment data are given below. Prior to performing a
detailed level validation, the file format is validated to ensure that all the expected data elements are included. The basic
validation is as follows:
1. The upload file/message should contain data that is in-line with the data type requirements of the target tables.
2. In case of duplicate records even with different actions, in the same file, the duplicate records will not be processed and
an error will be logged.
3. The data in each record sent has all the mandatory data included based on the action type indicated in the file or
message.
4. The data in each record is valid.
If this validation fails, then the entire upload is rejected. Otherwise it will move on to data level validation. For any data level
validation failure, the corresponding error is logged against the failed record and the processing moves on to the next
record.
The sections below explain the data validations that will occur based on the different action types.

5 Replenishment Attribute Update Overview] Release 19.0.x

Copyright © 2020, Oracle and/or its affiliates
Validations on Create
If you select an action type of Create in the upload, then this indicates you are creating a new replenishment update. This
could mean that you are activating new item/locations on replenishment, creating a scheduled update to existing
item/location combinations, or creating a scheduled deactivation of items/locations currently on replenishment. The table
below outlines the key field level validations that occur when creating a replenishment update. However, it should be noted
that there are also a number of other validations that can occur based on the combination of replenishment method, stock
category and order control. For more on what attributes are required for each of those combinations, see the RMS
Replenishment Overview white paper.

FIELD1 REPLENISHMENT ACTION VALIDATION

ACTIVATE DEACTIVATE UPDATE

Replenishment This field, if provided, will be ignored when creating new records, since it will be generated by the
Update ID system.

Schedule This field is optional. If not specified, one of the following auto generated descriptions will be used
Description based on the scenario:
 Scheduled Replenishment for <item> at <location>
 Scheduled Replenishment for <item | diff> at <location>
 Scheduled Replenishment for <Dept | Class | Subclass> at <location>

Effective Date Optional; the effective date needs to be greater than or equal to the current date. This date indicates
when the updates will be applied to the item/locations. If no value is specified, then the date will be
defaulted to the current date.

Replenishment Activate Deactivate Update

Action
This action would add This action would This action would update existing
replenishment parameters for delete the replenishment parameters for the specified
the specified items/locations existing items/locations
replenishment
attributes for the
item/location
combinations on
the effective date.

Item Optional; if specified, this can be a transaction level item or a parent level item for which the attributes
are being activated, deactivated, or updated. One field out of an item, department, class, or subclass
must be specified for all create actions.

Diff 1-4 Optional; if a parent level item is specified as the item, then differentiator IDs can also be specified to
further narrow the items that will have their attributes updated. Validation will be done to ensure that
the differentiator IDs are valid and match those that apply for the parent item.

1 All other attributes that are available in the template, but are not listed here are required or optional depending on the
replenishment method specified and details on that can be found in the RMS Replenishment Overview white paper. If the
create action is Deactivate, then the attributes not listed here are not applicable; if the create action is Update, then the not
listed attributes are optional, unless another attribute being updated also requires the value to be specified. For example, if
changing the season, then the phase would also need to be updated.
6 Replenishment Attribute Update Overview] Release 19.0.x
Copyright © 2020, Oracle and/or its affiliates
 FIELD1 REPLENISHMENT ACTION VALIDATION

ACTIVATE DEACTIVATE UPDATE

Department Optional; this field needs to be specified if the update will be made at the department, class, or subclass
level. The specified value needs to be a valid department ID in Merchandising. One field out of an item,
department, class, or subclass must be specified for all create actions.

Class Optional; this field needs to be specified if the update will be made at the class or subclass level. The
value needs to be a valid class ID for the specified department in Merchandising. One field out of an
item, department, class, or subclass must be specified for all create actions.

Subclass Optional; this field needs to be specified if the replenishment is to be set up at the subclass level. The
value needs to be a valid subclass ID for the specified department and class in Merchandising. One field
out of an item, department, class, or subclass must be specified for all create actions.

Location Optional; only used if S or W are selected as the location type. In those cases, this field is required. The
specified value needs to be a valid store or warehouse number, depending on the location type
specified.

Location Type Required field; valid values are: S (Store), W (Warehouse), AS (All Stores), AW (All Warehouses).

Auto Range Optional; indicates whether or n/a n/a

not new item/location
relationships should be created
based on the setup of
replenishment attributes. Valid
values Y or N (default). If
activating for a department,
class, or subclass, then a value of
N will also be assumed.

Activate Date Required; this date must be equal n/a Optional, if not specified then when the update
to or greater than the current is applied, the activate date won’t be updated.
date and less than the deactivate
date, if specified.

Deactivate Date Optional; but if specified, needs n/a Optional, if not specified then when the update
to be at least one day greater is applied, the deactivate date won’t be updated.
than the current date and later
than the activate date.

Presentation Required; will be defaulted to n/a Optional, if not specified then when the update
Stock zero if not specified. is applied, the presentation stock won’t be
updated.

Demo Stock Required; will be defaulted to n/a Optional, if not specified then when the update
zero if not specified. is applied, the demo stock won’t be updated.

Stock Category Required; valid values are (code n/a Optional, if not specified then when the update
type SCST): is applied, the stock category won’t be updated.
 Cross-Docked (C)
 Direct to Store (D)

7 Replenishment Attribute Update Overview] Release 19.0.x

Copyright © 2020, Oracle and/or its affiliates
 FIELD1 REPLENISHMENT ACTION VALIDATION

ACTIVATE DEACTIVATE UPDATE

 WH/Cross Link (L)

 Warehouse Stocked (W)

Order Control Required; valid values are (code n/a Optional, if not specified then when the update
type ROCT): is applied, the order control won’t be updated.
 Automatic (A)
 Buyer Worksheet (B)
 Manual (M)
 Semi-Automatic (S)

Source Required for stock categories n/a Optional, if not specified then when the update
Warehouse cross-docked, WH/cross link, and is applied, the source warehouse won’t be
warehouse stocked for store updated.
location types. Must be a valid
virtual warehouse ID in
Merchandising.

Supplier Required for stock categories n/a Optional, if not specified then when the update
cross-docked, direct to store, or is applied, the supplier site won’t be updated.
WH/cross link, for store location
types, as well as warehouse
stocked for warehouse location
types. This value must be a valid
supplier site ID in Merchandising.

Origin Country Required for stock categories n/a Optional, if not specified then when the update
cross-docked, direct to store, or is applied, the origin country won’t be updated.
WH/cross link, for store location
types, as well as warehouse
stocked for warehouse location
types. This value must be a valid
country code in Merchandising.

Pickup Lead Time Required for stock categories n/a Optional, if not specified then when the update
cross-docked, direct to store, or is applied, the pickup lead time won’t be
WH/cross link, for store location updated.
types, as well as warehouse
stocked for warehouse location
types.

Warehouse Lead Required for stock categories n/a Optional, if not specified then when the update
Time cross-docked, WH/cross link, and is applied, the warehouse lead time won’t be
warehouse stocked for store updated.
location types.

Update n/a n/a Optional; indicates whether or not the

Replenishment replenishment method is being updated for the
Method? items/locations. If this is N (default), then only
those item/location combinations that have the
replenishment method specified in the upload

8 Replenishment Attribute Update Overview] Release 19.0.x

Copyright © 2020, Oracle and/or its affiliates
 FIELD1 REPLENISHMENT ACTION VALIDATION

ACTIVATE DEACTIVATE UPDATE

will be updated. If this is Y, then validation will

ensure that all valid attributes for the new
replenishment method are present and valid in
the upload.

Replenishment Required; valid values are (code n/a Optional; if not specified, then when the update
Method type RM): is applied, the replenishment method will not be
updated. If it is specified and the Update
 Constant (C)
Replenishment Method flag is Y, then the
 Dynamic (D)
replenishment method will be updated to the
 Dynamic – Issues (DI)
specified value for all item/location
 Dynamic – Seasonal (S)
combinations. If the Update Replenishment
 Floating Point (F)
Method flag is N, then the replenishment
 Min/Max (M)
method will not be updated for any
 Store Orders (SO)
item/location combinations, but will be used as
 Time Supply (T)
an additional filter to determine which records
 Time Supply – Issues (TI)
should be updated.
 Time Supply – Seasonal (E)

Review Cycle Required; valid values are (code n/a Optional; if not specified then the review cycle
type RPRC): will not be updated.
 Every Week (0)
 Every Day (1)
 Every 2 Weeks (2)
 Every 3 Weeks (3)
 Every 4 Weeks (4)
 Every 5 Weeks (5)
 Every 6 Weeks (6)
 Every 7 Weeks (7)
 Every 8 Weeks (8)
 Every 9 Weeks (9)
 Every 10 Weeks (10)
 Every 11 Weeks (11)
 Every 12 Weeks (12)
 Every 13 Weeks (13)
 Every 14 Weeks (14)

Update Review n/a n/a If this is set to a value of Y, then the values for
Days? the days of the week will be considered when
updating. Otherwise, they will be ignored.

Monday-Sunday One or more days of the week n/a Optional; if the Update Review Days field is not
must be selected for all review Y, then no updates will be applied, regardless of
cycle settings except Every Day whether or not values are set for the days of the
(1). In that case all days of the week.
week will be defaulted to Y. If no
values have been selected for
any day of the week for other
review cycle options, then an
error will be raised. Valid values Y
or N (default).

9 Replenishment Attribute Update Overview] Release 19.0.x

Copyright © 2020, Oracle and/or its affiliates
 FIELD1 REPLENISHMENT ACTION VALIDATION

ACTIVATE DEACTIVATE UPDATE

Primary Optional; if specified, indicates n/a Optional; if not specified then the primary pack
Replenishment the pack that should be ordered will not be updated.
Pack as part of replenishment instead
of the component item. Valid
values are approved simple packs
containing the specified item.

Default Primary Optional; if this is Y, then the n/a Optional; if not specified then the primary cost
Cost Pack pack that has been defined as the pack will not be used to update the primary
primary cost pack for the item replenishment pack.
will be defaulted to the
replenishment pack. Valid values
are Y and N (default).

Remove Pack n/a n/a Optional; indicates whether or not the primary
pack should be removed for the item/location
combinations; valid values are Y or N (default).

Update Master n/a n/a Optional; indicates whether or not the updates
Attributes being applied should also update the master
replenishment attributes for the item/location
combinations. Valid values are Y or N (default).

Update from n/a n/a Optional; indicates whether or not master

Master Attributes attributes should be used in the update. If this is
Y, then the master attributes will be used to
update all replenishment attributes not included
in the upload. If N, then only those values
included in the upload will be used. Valid values
are Y or N (default).

Validations on Update
If you select an action type of Update in the upload, then this indicates you are updating a previously created scheduled
replenishment attribute update that has not yet been executed. This could be an update that was intended to activate new
item/location combinations on replenishment, to deactivate item/location combinations, or to update existing item/location
replenishment attributes.
The key field level validations that occur when updating a scheduled replenishment update are similar to those that occur
when creating the schedule (see above), and vary based on the replenishment action: Activate, Deactivate, or Update.
However, the following are a few additional points to keep in mind when updating scheduled replenishment updates:
 If field in the template is left null, the system will assume that you are intending to update the attribute to null. If it is a
required field for the replenishment method selected, this will raise an error on upload.
 If a column is not present in the template, then it will not be updated.
 When updating existing scheduled replenishment updates using the spreadsheet method, it is recommended that you
first download the existing scheduled updates from Merchandising, as described above, and then make your updates to
the data. This will help to minimize errors due to missing data as well as help in understanding the current settings.
 When processing an update to an existing scheduled change, the Schedule ID must be included in the upload in order to
correctly process the update.

10 Replenishment Attribute Update Overview] Release 19.0.x

Copyright © 2020, Oracle and/or its affiliates
Validations on Delete
If you select an action type of Delete in the upload, then this indicates you want to delete a previously created scheduled
replenishment attribute update that has not yet been executed. For deletes, there is very little validation performed and
most fields are ignored. The only required field, other than Action, is the Replenishment Update ID.

Error Resolution
If there are any issues faced while uploading the data via spreadsheet, then the status of the process is set to Processed with
Errors or Processed with Warnings in the Data Loading Status screen. Visibility to the details of the errors can be viewed in
the Replenishment Issues screen for each upload with an error. Once the errors have been corrected, the updated file may
be re-uploaded as a fresh upload request.
Errors in download processing are typically due to the inability to access the data or insufficient privileges to create and write
to the specified location. These errors can be resolved by removing any constraints that might have placed a lock on the
data or ensuring that any constraints on creation of the spreadsheet are relaxed.
Errors in upload request processing are typically data related and likely require data correction. The users can use the error
details in the Replenishment Issues screen as a guide to make corrections to the originally uploaded document or download
a new version through the Data Loading Status screen.
If using this method, a worksheet that contains a list of errors associated with the data set will be included as a separate tab
in the downloaded spreadsheet to serve as an offline reference for carrying out the corrections.

The screen shown below is an example of how the information is displayed for the worksheet that had the error, which row
in the worksheet is in error, and a short description of the issue. Once the errors have been corrected, the data can be re-
uploaded into Merchandising as needed, using the corrected file.

While using the bulk upload, this will not have notifications in the case of errors in the upload, but the status of the process
will be available on Data Loading Status screen, similar to the spreadsheet upload. To see the details of the errors externally,
the process status table SVC_PROCESS_TRACKER and the replenishment upload error table CORESVC_REPL_ERR will be
exposed to the retailers by replicating them in the Data Access Schema (DAS).
In the case of the web service option, the processing of these messages will happen synchronously. If there are any
validation errors, the details will be returned to the calling system.

Note: If there are data validation errors in web service upload, these errors will also be visible
in the Data Loading Status screens.

11 Replenishment Attribute Update Overview] Release 19.0.x

Copyright © 2020, Oracle and/or its affiliates
Appendix A: Data Creation Examples
This section provides examples on how to set up information in order to ensure that the replenishment attributes are
created as complete and able to be uploaded successfully when sent to Merchandising. A couple of examples are described
here which include:
 Activate an item store on replenishment
 Update attributes for a class
For each case, the key attributes are included in the tables below along with a description of how they should be set,
representing how a template may be configured to manage similar updates. Attributes not included are assumed to be
either optional or auto-defaulted to the correct value for this type of item.

Create an Activation for an Item/Store

This example illustrates the typical values that would be included for an item without any differentiators at a store using the
Min/Max.

TEMPLATE COLUMN REQUIRED COMMENTS

FOR THIS
EXAMPLE?

Action Yes For this scenario, the option would be Create. Other options include
Update and Delete.

Schedule ID No Will be generated by the system and ignored, if specified for Create.

Schedule Description No If not specified, the following auto generated description will be used:
'Scheduled Replenishment for <item> at <location>’

Effective Date No When creating a new scheduled update, this needs to be a value equal
to or greater than the current date.
Will be defaulted to the current date, if not specified.

Scheduled Action Yes For this use case, we are activating this item/location on
replenishment, so the Schedule Action will be A = Activate

Item Yes Item ID for which the attribute is being created

Location Type Yes Valid values are All Stores, All Warehouses, Store, or Warehouse. For
this example, assume that Store is selected.

Location Yes Should be a valid store, since that was the entered location type

Auto Range Indicator Yes This determines whether or not to create the item/location
relationship in Merchandising when the attributes are uploaded, if it
doesn’t already exist. It will be assumed to be N if not specified.

Activate Date Yes Can be the current date or a future date.

Deactivate Date No Assume that this is not entered for activation, but it can be if desired.
If specified, it must be greater than the activate date and also greater
than the current business date + 1.

Presentation Stock Yes Will be defaulted to zero, if not specified.

12 Replenishment Attribute Update Overview] Release 19.0.x

Copyright © 2020, Oracle and/or its affiliates
 TEMPLATE COLUMN REQUIRED COMMENTS
FOR THIS
EXAMPLE?

Demo Stock Yes Will be defaulted to zero, if not specified.

Replenishment Method Yes In this example, Min/Max will be used. Otherwise, other
replenishment options can be selected from the drop down.

Stock Category Yes Valid Values here are: Cross-docked, Direct to Store, PO Cross-link, or
Warehouse Stocked. For this example, let’s assume that Warehouse
Stocked is selected.

Order Control Yes Valid values here are: Automatic, Semi-Automatic, Buyer Worksheet,
or Manual

Source Warehouse Yes Must be a valid virtual warehouse for the item. In this case, it’s
assumed that the item is already ranged to this warehouse. Auto-
ranging does not apply.

Lead Time - WH to Receiving Yes Number of days it takes for the item to be shipped from the source
warehouse to the store.

Minimum Stock Yes User defined value

Maximum Stock Yes User defined value

Increment % Yes User defined value; usually 100%

Scaling Exempt Yes Yes or No

Maximum Scale Amount Yes User defined value, if Scaling Exempt = N

Review Cycle Yes Options include Every Day, Every Week, or Every X Weeks, where x
can be 2-14. If Every Week or Every X Weeks is selected, then select
one or more of the days of the week when the review should occur on
the reviewed week. For Every Day, all the days of the week should be
Yes.

Monday Yes Yes or No

Tuesday Yes Yes or No

Wednesday Yes Yes or No

Thursday Yes Yes or No

Friday Yes Yes or No

Saturday Yes Yes or No

Sunday Yes Yes or No

13 Replenishment Attribute Update Overview] Release 19.0.x

Copyright © 2020, Oracle and/or its affiliates
 TEMPLATE COLUMN REQUIRED COMMENTS
FOR THIS
EXAMPLE?

Update Master Attributes Yes Set this to ‘Yes’ if you want these attributes to be considered the
“master” for this item/location. This can be used to “reset” the
item/location at a future date, if temporary updates are made.
It will be defaulted to ‘No’ for the ‘Create’ if not specified.

Create an Update for a Class

This example illustrates the typical values that might be included in a template configured for updating attributes (Min Stock
and Max Stock) for all items in a department/class at a warehouse. In this example, we’ll assume that the minimum and
maximum stock levels are being updated for the items in the class being replenished from the specified warehouse that are
using the Min/Max method.

TEMPLATE COLUMN REQUIRED COMMENTS

FOR THIS
EXAMPLE?

Action Yes In this case, we are creating a new schedule update that will Update
replenishment attributes. So, this should be “Create”.

Schedule ID Yes Will be generated by the system and ignored, if specified for Create.

Effective Date No Needs to be a value equal to or greater than the current date.
Will be defaulted to the current date, if not specified.

Scheduled Action Yes U = Update

Department Yes Must be a valid department in Merchandising.

Class Yes Must be a valid class for the specified department in Merchandising.

Location Type Yes W = Warehouse

Location Yes Must be a valid virtual warehouse in Merchandising.

Update Replenishment Method Yes Because in this example we are not changing the replenishment
method, we will set this to No, so that the method is used just for
determining which items to update.

Replenishment Method No This should be Min/Max, to only update those item/warehouse

combinations in the class that are currently on Mix/Max method.

Minimum Stock Yes Value being modified as part of the update

Maximum Stock Yes Value being modified as part of the update

Update Master Attributes Yes Could be Yes or No for this example, depending on whether this is going
to become the new “master” setting or if it is a temporary change.

14 Replenishment Attribute Update Overview] Release 19.0.x

Copyright © 2020, Oracle and/or its affiliates
 TEMPLATE COLUMN REQUIRED COMMENTS
FOR THIS
EXAMPLE?

Update From Master Attributes Yes In this scenario, this would be No, as it is making a specific update, not
resetting all the attributes from the master.

15 Replenishment Attribute Update Overview] Release 19.0.x

Copyright © 2020, Oracle and/or its affiliates
Appendix B: Configuration Parameters

Replenishment Induction Configuration (REPL_INDUCT_CONFIG)

This table is used to configure some of the technical components of replenishment induction.

CONFIGURATION PARAMETER DESCRIPTION

Maximum Chunk Size This specifies the maximum number of replenishment records that can be
processed in one chunk.

Maximum Threads This is the maximum number of threads that should be spawned for the
replenishment induction package.

Wait Between Threads This is the number of milliseconds between the submissions of two threads.

Maximum Records for Download This is the maximum number of replenishment orders that can be
downloaded using a spreadsheet. If the criteria selected for downloading
results in a larger number of records than this value being downloaded, an
error will be raised.

Maximum Records for Synchronous This is the maximum number of replenishment records that can be
Download downloaded using a spreadsheet in a synchronous fashion. Beyond this
threshold, the process is submitted as an asynchronous process.

Maximum Records for Upload2 This is the maximum number of replenishment orders that can be
uploaded using a spreadsheet or bulk load. If the file exceeds this many
records, then it will be rejected.

Maximum Records for Synchronous Upload This is the maximum number of replenishment records that can be
uploaded using a spreadsheet in a synchronous fashion. Beyond this
threshold, the process is submitted as an asynchronous process.

2It is recommended that file sizes be kept to less than .75GB for best performance. This equates to 800,000,000 records in
the upload.
16 Replenishment Attribute Update Overview] Release 19.0.x
Copyright © 2020, Oracle and/or its affiliates
CONNECT WITH US
Call +1.800.Oracle1 or visit oracle.com
Outside North America, find your local office at oracle.com/contact

blogs.oracle.com facebook.com/oracle twitter.com/oracle

Copyright © 2020, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the contents hereof are subject to change without
notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties
and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are formed
either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without
our prior written permission.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC
International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The
Open Group. 0120