This chapter contains the following topics:
This table lists the runubexml commands in scripts that launch the Planning Outbound Processor (R34A400) and Planning Inbound Processor (R34A410):
| Oracle Demantra Workflow | UBE Launch Script | Runubexml Command |
|---|---|---|
| E1 Full Download | runextracts_full.bat located in the e1_environment_ube_launch_script_folder | R34A400_full.xml |
| E1 Incremental Download | runextracts_incr.bat located in the e1_environment_ube_launch_script_folder | R34A400_incr.xml |
| E1 Items Download | runextracts_item.bat located in the e1_environment_ube_launch_script_folder | R34A400_item.xml |
| E1 Locations Download | runextracts_loc.bat located in the e1_environment_ube_launch_script_folder | R34A400_loc.xml |
| E1 Upload | runupload.bat located in the e1_environment_ube_launch_script_folder | R34A410_fcst.xml |
| E1ToPTP_FullDownLoad | runube.xml_full.bat | R34A400_full.xml |
| E1ToPTP_incre_download | runube.xml_incr.bat | R34A400_incr.xml |
| E1ToPTP_PromoPrice_DownLoad | runube.xml_listprice.bat | R34A400_LISTPRICE.xml |
| E1ToPTP_PromoCost_DownLoad | runube.xml_itemcost.bat | R34A400_ITEMCOST.xml |
| PTPToE1_UploadPromotionPrices | backup_promotion_pricing.bat
upload_promoiton_pricing.bat upload_delete_promopricing.bat |
|
| E1ToDSM New Deduction Download | runubexml_deduction.bat | 03b0209_qatpround.xml |
| DSMToE1 Deduction Export | backup_deduction.bat
upload_deduction.bat |
R03b41z2_qatpround.xml |
| E1 APConfirm Import | runubexml_confirm.bat | R04110zb_qatpround.xml |
| DSMToE1 Claim Export | backup_claim.bat
upload_claim.bat |
R04110zc_qatpround.xml |
You must create a runubexml template file for each processor version that is required for the Oracle Demantra integration. These XML files are called by the UBE launching scripts, which launch the appropriate processor and version.
To generate an XML file:
From the command line of the JD Edwards EnterpriseOne server, select the e1_system_bin32 folder.
In the command line, enter runubexml G CREATE_XML jdeRequest.xml. The system creates the jdeRequest.xml file in the same folder.
Open the jdeRequest.xml file and modify these fields:
| Field | Description |
|---|---|
| user | Enter the JD Edwards EnterpriseOne user ID. |
| pwd | Enter the JD Edwards EnterpriseOne password. |
| environment | Enter the JD Edwards EnterpriseOne environment from which you want to extract information. |
| role | Enter the role to use within JD Edwards EnterpriseOne. |
| REPORT_NAME_VALUE | Specify the processor from which you want to create a runubexml template, such as R34A400 for the Planning Outbound Processor or R34A410 for the Planning Inbound Processor. |
| REPORT_VERSION_VALUE | Enter the version you want to use with the specified processor. |
|
Note: The person executing the runubexml command should have the same sign-on rights to the server as the OneWorld services. |
Save the changes to the jdeRequest.xml file.
In the command line, enter runubexml S jdeRequest.xml EnterpriseOne to Demantra Demand Management Integration 13-33 Processor_Version.XML where the value of Processor is either R34A400 (Planning Outbound Processor) or R34A410 (Planning Inbound Processor) and the value of Version is full, incr (incremental), item, loc (location), or fcst (forecast). The resulting XML file, Processor_Version.XML, is generated in the e1_system_bin32 folder. This file contains all the processing options, data selections, and report interconnects for the specified version of the processor.
For the incremental report (R34A400_incr.xml, which only extracts Sales Order History data based on a date range from JD Edwards EnterpriseOne), open the generated xml file in the e1_system_bin32 folder. Use the values in this table to edit the Report_Interconnect fields in the file:
| Field | Description |
|---|---|
| From Days | Specify the number of days before or after the current day to begin gathering extract data.
To gather data starting after today, enter a positive number. For example, to gather data starting three days after today, enter 3. To start gathering data before today, enter a negative number. For example, to start gathering data three days before today, enter –3. The value 0 represents today. If both the From Days and Thru Days fields are left blank, the value is assumed to be 0, which extracts only today's historical data. |
| Thru Days | Specify the number of days before or after the current day to stop gathering extract data.
To stop gathering data after today, enter a positive number. For example, to stop gathering data three days after today, enter 3. To stop gathering data before today, enter a negative number. For example, to stop gathering data three days before today, enter –3. The value 0 represents today. If both the From Days and Thru Days fields are left blank, the value is assumed to be 0, which extracts only today's historical data. |
| IncrementalLoadIndicator | Specify whether full or incremental data is extracted from the Planning Outbound Processor. Values are:
0: Full extraction. 1: Incremental extraction based on values in the From Days and Thru Days fields. |
|
Note: Initially, use these From Days and Thru Days settings:Daily system: –2 and 0 to capture a full two weeks. Weekly system: –41 and 0 to capture a full fiscal month with five weeks, regardless of weekday run. Monthly system: –4 and 0 to capture a full quarter, regardless of month day run. If you take an electronic software update (ESU) that modifies processing options related to these UBEs, you must re-create the XML template. |
This section discusses customizing scripts for:
JD Edwards EnterpriseOne integration with Oracle Demantra Demand Management.
JD Edwards EnterpriseOne integration with Oracle Demantra Predictive Trade Planning.
JD Edwards EnterpriseOne integration with Oracle Demantra Deductions Settlement Management.
You can use three series of scripts to automate the integration between JD Edwards EnterpriseOne and the Oracle Demantra Demand Management system:
Scripts called by the Oracle Demantra workflows.
UBE launch scripts in the JD Edwards EnterpriseOne server.
Postprocessing scripts.
Templates for scripts are included with the Oracle Demantra installation in the demantra_install_folder\e1_integration folder. The scripts require modification to specify the correct directories and runubexml commands. After customization, you must move the scripts to the correct server and folder.
The folders involved in Oracle Demantra Demand Management integration are:
| Folder | Server | Role |
|---|---|---|
| Demantra_install_folder\e1_integration | Demantra | Contains the scripts called by the Oracle Demantra workflows:
|
| Demantra_install_folder\e1_files | Demantra | Location for all extracts, Oracle Demantra forecast, synchronization, and error files. |
| e1_environment_ube_launch_ script_folder | JD Edwards EnterpriseOne | Contains the UBE launch scripts:
|
| e1_input_forecast_folder | JD Edwards EnterpriseOne | Location for the Forecast.txt file after it is copied from the Demantra server by the upload_forecast.bat script. |
| e1_output_folder | JD Edwards EnterpriseOne | Location for the extracts generated by the Planning Outbound Processor (R34A400), synchronization, control, and error files. |
| e1_system_bin32_folder | JD Edwards EnterpriseOne | Contains the runubexml files that start the Planning Outbound Processor (R34A400) and Planning Inbound Processor (R34A410):
Note: In this list, full, incr, item, loc, and fcst represent the version names. |
| e1_postprocessing_script_folder | JD Edwards EnterpriseOne | Contains the postprocessing scripts called by the Planning Outbound Processor (R34A400) and the Planning Inbound Processor (R34A410):
|
For the Oracle Demantra Demand Management integration, the following six scripts are called by five Oracle Demantra workflows:
|
Note: All scripts are located in the demantra_install_folder\e1_integration folder. |
The five scripts located in the e1_environment_ube_launch_script_folder start the runubexml commands that start the Planning Outbound Processor (R34A400) and Planning Inbound Processor (R34A410). They are launched by the Oracle Demantra workflow scripts.
|
Note: All UBE launch scripts are located in the e1_environment_ube_launch_ script_ folder |
These two scripts are called by the Planning Outbound Processor (R34A400) and Planning Inbound Processor (R34A410) respectively:
| Processor | Postprocessing Script | Results |
|---|---|---|
| Planning Outbound Processor (R34A400) | postextract.bat |
|
| Planning Inbound Processor (R34A410) | postupload.bat |
|
|
Note: Both postprocessing scripts are located in the e1_postprocessing_scripts_ folder. |
You can use three series of scripts to automate the integration between JD Edwards EnterpriseOne and the Oracle Demantra Predictive Trade Planning system:
Scripts called by the Oracle Demantra workflows.
UBE launch scripts in the JD Edwards EnterpriseOne server.
Postprocessing scripts.
Templates for scripts are included with the Oracle Demantra installation in the demantra_install_folder\e1_integration folder. The scripts require modification to specify the correct directories and runubexml commands. After customizing, the scripts must be moved to the correct server and folder.
The folders involved in Oracle Demantra Predictive Trade Planning integration are:
| Folder | Server | Role |
|---|---|---|
| demantra_install_folder\e1_integration | Demantra | Contains the scripts called by the Oracle Demantra workflows:
|
| demantra_install_folder\e1_files | Demantra | Location for all extracts, Oracle Demantra promotion, deduction, synchronization, and error files. |
For the Oracle Demantra Predictive Trade Planning integration the following seven scripts called by five Oracle Demantra workflows:
|
Note: All scripts are located in the demantra_install_folder\e1_integration folder. |
These three scripts are called by the Planning Outbound Processor (R34A400) and Planning Inbound Processor (R34A410) respectively:
| Processor | Postprocessing Script | Results |
|---|---|---|
| Planning Outbound Processor (R34A400) | postextract.bat |
|
| Planning Inbound Processor (R34A410) | Postupload_delete.bat |
|
| Planning Inbound Processor (R34A410) | Postupload.bat |
|
|
Note: All three postprocessing scripts are located in the e1_postprocessing_scripts_ folder. |
You can use three series of scripts to automate the integration between JD Edwards EnterpriseOne and the Oracle Demantra Deductions and Settlement Management system:
Scripts called by the Oracle Demantra workflows.
UBE launch scripts in the JD Edwards EnterpriseOne server.
Postprocessing scripts.
Templates for scripts are included with the Oracle Demantra installation in the demantra_install_folder\e1_integration folder. The scripts require modification to specify the correct directories and runubexml commands. After customizing, the scripts must be moved to the correct server and folder.
The folders involved in Oracle Demantra Deductions and Settlement Management integration are:
| Folder | Server | Role |
|---|---|---|
| demantra install folder\e1_integration | Demantra | Contains the scripts called by the Oracle Demantra workflows:
|
| e1_integration\el files | Demantra | Location for all extracts, Oracle Demantra forecast, synchronization, and error files. |
For the Oracle Demantra Deductions and Settlement Management integration there are six scripts called by four Oracle Demantra workflows:
|
Note: All scripts are located in the demantra_install_folder\e1_integration folder. |
This section discusses the considerations for modeling the integration solution for setting up the integration between JD Edwards EnterpriseOne and Oracle Demantra:
Levels in JD Edwards EnterpriseOne.
Customer and company mapping in JD Edwards EnterpriseOne.
Multi-site recommendations.
Null handling during integration.
"Open With" worksheets.
Worksheet filters.
Analytic engine guidelines.
JD Edwards EnterpriseOne requires only three leaf levels: item, customer/company and branch. Each of these leaf levels can have several significant attributes which must be mapped to the parent level. This mapping is not fixed and varies by implementation.
As part of the JD Edwards EnterpriseOne extracts, up to 30 informational fields are available for item, customer and branch. These fields are called category codes and can hold hierarchy-relevant information. As part of an implementation the information in these fields can be leveraged to enhance business value to the customer using Oracle Demantra. The placeholder columns preconfigured in Oracle Demantra are defaulted to disabled and should be enabled if found to add to business value.
To use category codes in JD Edwards EnterpriseOne:
Map the information that is held in each category code in JD Edwards EnterpriseOne.
Assess the business value of each category code and determine whether it contains information that is relevant to the hierarchy level. For example, Item Category Code 13 holds brand information. It is very valuable to see which brand an item belongs to, and create reports based on brand.
Evaluate whether available place-holder levels are sufficient to contain relevant hierarchy information. These are the available place-holder levels:
7 available item levels.
5 available branch levels.
7 available customer levels (level 7 currently mapped to company).
To use customer codes in the Oracle Demantra Business Modeler:
Open the Integration Template model.
For existing levels:
Change the level name to a more business meaningful name.
Ensure that field names point to the correct staging column containing relevant category code information.
For new levels:
Add a new level as the parent of the leaf to which it is a category code.
The table name should be t_src_item_tmpl for Items and t_src_loc_tmpl for Customer or Branches.
Ensure that field names point to the correct staging column containing relevant category code information.
Upgrade the existing model. Do not build a new model.
Open Oracle Demantra Demand Management and grant full control to the category code levels that are used.
Although the predefined data model is designed to meet the best practice requirements for demand management, each implementation might involve a customer with different needs and hierarchies. The Oracle Demantra Hierarchy can be enhanced to support a more complex level structure model, based on these questions and considerations:
Where are additional levels coming from? Do the 3 staging tables (Item, Location, and Sales) have the relevant information to populate these additional levels? Enhancing JD Edwards EnterpriseOne exports to support more information may prove difficult. Lacking a data source, what process maintains this level?
Do additional or changed levels support the implied parent-child relationship? JD Edwards EnterpriseOne does not conduct any hierarchical data validation on the category codes being exported. Data violating model-defined father-son relationships are ejected during loading.
Always upgrade the existing model instead of building a new model.
JD Edwards EnterpriseOne sales data is exported at a resolution of item, customer, company, branch, and date. The inclusion of the company requires some changes in the integration configuration. The location leaf node site now contains a concatenation of customer and company. In order to sort by customer, you must load this information into the Account level. In order to sort by company, you must load this information into the Trading Partner Zone level. Implementation recommendations are:
Rename level Site to Customer Company
Rename level Customer to Customer Old and disable the level in Oracle Demantra Demand Management.
Rename level Account to Customer.
Rename level Trading Partner Zone to Company.
If you have centralized data (that is, a single source of data) for all the sites and a single instance of Oracle Demantra, you should generate a single set of extracts. The generated Sales Order History extract includes the information from all the sites. The existing Oracle Demantra Workflows uses the single Sales Order History extract.
However, in cases of multiple sources of data setup for various sites and a single instance of Oracle Demantra, you should use multiple data extract scripts and workflows. For example, if extracts are generated from two sites, set up one workflow to extract Sales Order History from site one and a second workflow to extract Sales Order History from site two.
These workflows should be set up in series (that is, workflow one should call workflow two after it has been completely processed). This is to ensure that the data from site one is imported from the staging tables into Oracle Demantra before the second set of data is processed. The two workflows cannot run parallel.
During integration, many of the category code fields may be null or empty when transferred from JD Edwards EnterpriseOne. Since these category code fields may be used as levels in Oracle Demantra, it is important that they not remain empty. As part of the integration process, when null values are found, a different string replaces them. This string is configured.
Configuring the string requires modification to the PACKAGE DATA_LOAD. The package parameter VS_DEFAULT contains the values which replace null level information. the default value is N/A.
"Open With" worksheets should be unfiltered. To display a filtered version of the worksheet, you must create a duplicate for "My Worksheets". If you place a filter on a worksheet to be used by "Open With", the "Open With" filter is applied to the already filtered population which may not provide a result set. For example, if the worksheet is filtered to Member 1 of Level 1, and "Open With" is launched from Member 2 of Level 1, the result set is null.
The Demand Management worksheets have a default filter. This filter ensures that when first run in a large production environment, the worksheet does not attempt to run over the entire data population. The added filter points to the default members of all levels that are configured as aggregation levels in the worksheet. During an implementation, open all the worksheets and their embedded worksheets and change the filters to match the business process and scope. Remember that very large worksheets are typically not representative of one user's business process and typically experience degradation in performance.
The batch engine generates a new forecast for a system wide population or a line of business. Using distributed processing, it analyzes very large amounts of data at night and on the weekends when users are not logged into the system. By contrast, the simulation engine generates or regenerates a forecast for a very specific population subset. Simulations can be run on an as-needed basis, and several users may run simulations concurrently. Because of the large amount of processing performed by the batch engine and the fact that it typically regenerates the entire forecast, the batch and simulation engine are not enabled to run at the same time. The analytic engine outputs several accuracy metrics when running the batch engine. They are:
MAPE
BIAS
MRE
RMSE
And several historical observations used to produce the forecast.
The length of history serving as a basis for the first four metrics is set by INIT_PARAMS_0 parameter Metrics Period. This parameter defines the number of periods of history, starting with the most recent and moving backward when calculating the accuracy metrics. These metrics are stored in table MDP_MATRIX and generated by the engine at the level at which a node is forecast. This implies that nodes not receiving a forecast do not have these numbers and that all MDP_MATRIX combinations under a specific node have the same engine metric values.
This section provides an overview of the JD Edwards EnterpriseOne Configuration, customization of JD Edwards EnterpriseOne applications, and planning integration constants and planning file definitions and discusses how to:
Set up planning integration constants.
Set up planning file definitions.
Three processes must be customized to implement the integration between JD Edwards EnterpriseOne and Oracle Demantra applications:
JD Edwards EnterpriseOne applications including versions, processing options, integration constants, and file definitions.
Runubexml template files that contain all the JD Edwards EnterpriseOne variables necessary to start specific versions of the outbound and inbound extracts using the runubexml command from a script. These templates also indicate whether a full or incremental extract is run.
Scripts that transfer JD Edwards EnterpriseOne data from the JD Edwards EnterpriseOne server to the Oracle Demantra server. The scripts also perform synchronization and error checking.
To support the Oracle Demantra workflows, you must set up the following versions:
| Oracle Demantra Workflow | JD Edwards EnterpriseOne Processor | JD Edwards EnterpriseOne Extract Programs |
|---|---|---|
| E1 Full Download | SCP Outbound Processor (R34A400) | Process Branch Extract (R34A470)
Customer Master Extract (R34A530) Item UOM Extract (R34A480) Sales History Extract (R34A425) F4211 Sales History Extract (R34A435) |
| E1 Incremental Download | SCP Outbound Processor (R34A400) | Sales History Extract (R34A425)
F4211 Sales History Extract (R34A435) |
| E1 Items Download | SCP Outbound Processor (R34A400) | Item UOM Extract (R34A480) |
| E1 Locations Download | SCP Outbound Processor (R34A400) | Process Branch Extract (R34A470) |
| E1 Upload | SCP Inbound Processor (R34A410) | Inbound Forecasts Extract (R34A485) |
| E1ToPTP_FullDownLoad | SCP Outbound Processor (R34A400) | Customer Master Extract (R34A530)
Item UOM Extract (R34A480) Sales History Extract (R34A425) F4211 Sales History Extract (R34A435) |
| E1ToPTP_incre_download | SCP Outbound Processor (R34A400) | Sales History Extract (R34A425)
F4211 Sales History Extract (R34A435) |
| E1ToPTP_PromoPrice_Download | SCP Outbound Processor (R34A400) | Future List Extract (R45529) |
| E1ToPTP_PromoCost_Download | SCP Outbound Processor (R34A400) | Item Cost Extract (R41053) |
| PTPToE1_UploadPromotionPrices | SCP Inbound Processor (R34A410) | Inbound Promotional Pricing (R45640) |
| E1ToDSM New Deduction DownLoad | Open Deductions Extract (R03B0209) | |
| E1 APConfirm Import | AP Confirmation (R04110ZC) | |
| DSMToE1 Deduction Export | Inbound Deduction Disposition (R03B41Z2) | |
| DSMToE1_Claim Export | AP Inbound Claim (R04110ZB) |
This section discusses Planning Integration Constants and Planning File Definitions.
Constants are interface definitions and formats. You must set up integration constants for use by the outbound and inbound batch processors. You typically define the constants during the development and setup stage of an implementation. Although you can change the integration constants at any time, you should change the values in the Planning UOM and Shipping UOM fields only when you are performing a complete extract. Otherwise, inconsistent quantities might occur.
You can use the Integration File Definition program (P34A11) to:
Set up the interface definitions for the file locations that the outbound and inbound batch processor programs use.
Define command line instructions for scripts that transfer files between the JD Edwards EnterpriseOne and Oracle Demantra servers.
|
Note: The entries for each file or command line in the Planning File Definition table (F34A11) are platform-specific. If the integration programs are moved from one platform to another, no file name translation is made. For example, if you set up a batch program to run on a Windows NT EnterpriseOne server, the file names that the program uses must be NT-compliant file names. If that batch program is submitted to a UNIX or OS/400 server that is running JD Edwards EnterpriseOne, the program would not run properly because valid Windows NT file names are not valid on the OS/400 or on UNIX. The same is true for command line (FTP script) table entries. A valid Windows NT command is not valid for other JD Edwards EnterpriseOne server platforms. In addition, the Integrated File System (IFS) of the OS/400 is not supported for inbound or outbound flat files. Inbound or outbound flat files on the OS/400 must use the traditional file system. |
| Form Name | Form ID | Navigation | Usage |
|---|---|---|---|
| Integration Constants | W34A10A | Planning & Scheduling (G34A), Planning Integration Constants. | Set up integration constants. |
| Integration File Definitions | W34A11A | Planning & Scheduling (G34A), Planning File Definitions | Set up integration file definitions. |
Access the Integration Constants form.
Select the General tab.
Specify the date format to use as the default value in the extract file or select it from the Select User Defined Codes form. The system date is represented in the EMD format (four-digit year, month, day) by default.
|
Note: For Oracle Demantra integration, the date format is hard coded to MMDDYYYY, and you should set the processing option to 1 in the Planning Outbound Processor (R34A400) on the Demantra Processing tab. |
Specify the character, such as a comma or semicolon, that the system uses to separate fields in flat files. The system requires a value in this field.
|
Note: For Oracle Demantra integration, the flat-file delimiter is hard-coded to semicolon, and you should set the processing option to 1 in the Planning Outbound Processor (R34A400) on the Demantra tab. |
Specify the character, such as a single or double quotation marks, that the system uses to denote text in flat files. The system requires a value in this field.
|
Note: For Oracle Demantra integration, the data format is hard coded to double quotation marks, and you should set the processing option to 1 in the Planning Outbound Processor (R34A400) on the Demantra tab. |
Specify whether the exported forecasts are generated using monthly or weekly periods. The system validates the value in this field against the values in UDC 34A/MW.
Access the Integration File Definitions form.
Enter a pre-established index or number that the system uses to retrieve data from a file. For example, the keys to the Employee Master file might be Employee Number, Social Security Number, or Home Department.
|
Note: You cannot leave this field blank if you have text in the corresponding File Definition field. |
Specify the name of the flat file, including the directory path where the file exists or where the system executes a command line.
This section provides an overview of the SCP Outbound Processor program and discusses how to:
Run the SCP Outbound Processor program.
Set processing options for the SCP Outbound Processor (R34A400).
You use the SCP Outbound Processor (R34A400) program to transfers flat file extracts from the JD Edwards EnterpriseOne system to the Oracle Demantra system. The following JD Edwards EnterpriseOne extracts are required for integration to Oracle Demantra:
| Outbound Extract | Oracle Demantra Application Supported | Data Retrieved |
|---|---|---|
| SCP Process Branch Information (R34A470) | Demand Management
Predictive Trade Planning |
Use this batch program to retrieve information from these JD Edwards EnterpriseOne tables:
|
| SCP Customer Master Information Extract (R34A530) | Demand Management
Predictive Trade Planning |
Use this batch program to retrieve:
|
| SCP Item UOM Extract (R34A480) | Demand Management
Predictive Trade Planning |
Use this batch program to retrieve:
This extract program generates two extracts: SCP Item Branch Extract and SCP Master UOM Extract. |
| SCP Sales History Extract (R34A425) | Demand Management
Predictive Trade Planning |
Use this batch program to retrieve:
You can also specify a date in the processing options to exclude from the extraction any sales orders with a promised date that occurs before the beginning date. |
| SCP F4211 Sales History Extract (R34A435) | Demand Management
Predictive Trade Planning |
Use this batch program to retrieve:
You can also specify the beginning date for the selection of sales order history records to be included. The system does not include sales orders with a promised ship date before this date. |
Using the processing options associated with the SCP Outbound Processor or its extract programs, you can customize the extracts to generate. For more finite customization, use data selection options. Using JD Edwards EnterpriseOne versions, you can create different configured sets of outbound extracts that can be run at different times during the day to meet the requirements.
Select Planning & Scheduling (G34A), Planning Outbound Processor.
Processing options enable you to specify the default processing for programs and reports.
Specify the key value that is associated with the path name of the EnterpriseOne outbound control file. The key value must be a valid entry in the Integration File Definition table (F34A11). You can enter path names and keys in the Integration File Definitions program (P34A11). This processing option is required.
Specify the key value that is associated with the path name of the SCP outbound control file. The key value must be a valid entry in the Integration File Definition table (F34A11). You can enter path names and keys in the Integration File Definitions program (P34A11). If you enter 1 in the Batch Control processing option, you must enter a key value in this field.
Activate EnterpriseOne-related batch control. Values are:
Blank: Do not verify that the previous JD Edwards EnterpriseOne batch is completed before starting the batch. Start a new batch regardless of whether JD Edwards EnterpriseOne has completed processing the previous batch associated with this control file.
1: Verify that the previous JD Edwards EnterpriseOne batch is complete before starting this batch. If the previous batch has not been acknowledged, do not run this batch.
|
Note: Turn off batch control only under special conditions, for example for demos and testing when batch control is not needed, the first time you run the batch associated with this control file; or when you must reset the batch control file settings because the control file was deleted. |
Activate SCP-related batch control. Values are:
Blank: Do not verify that SCP has acknowledged processing the previous batch before starting this batch. Start a new batch regardless of whether SCP has acknowledged processing the previous batch that is associated with this control file.
1: Verify that SCP has acknowledged processing the previous batch before starting this batch. If the previous batch has not been acknowledged, do not run this batch.
|
Note: Turn off batch control only under special conditions, for example for demos and testing when batch control is not needed, the first time you run the batch associated with this control file; or when you must reset the batch control file settings because the control file was deleted. |
Enter the address book number of the person who receives a notification when an error occurs during batch processing. This person receives messages through the work center. If you leave this option blank, the system does not send out a notification when errors occur.
Specify the key value that is associated with the path name of the error log created in the batch. The key value must be a valid entry in the Integration File Definition table (F34A11). You can enter path names and keys in the Integration File Definitions program (P34A11). The error log is a text file that contains batch status information and record counts. The same information appears on the standard report that this batch program produces. If you leave this processing option blank, the system does not write the error log text file, but still produces the standard report output.
Specify the key value that is associated with external commands to be executed before any individual extract programs are run. The key value must be a valid entry in the Integration File Definition table (F34A11). You can enter path names and keys in the APS Integration File Definitions program (P34A11). You can use the commands associated with this key to execute a script (such as an FTP script) to retrieve data, run an external program, or perform most command-line processing.
Specify the key value that is associated with external commands to be executed after any individual extract programs are run. The key value must be a valid entry in the Integration File Definition table (F34A11). You can enter path names and keys in the Integration File Definitions program (P34A11). You can use the commands associated with this key to execute a script (such as an FTP script) to send data, run an external program, or perform most command-line processing.
Specify the version of the SCP Sales History Extract program (R34A425) that the system runs in this batch. The SCP Sales History Extract program selects information from the Sales Order History table (F42119). For the version of the SCP Sales History Extract program that you enter in this processing option, you can set the data selection for this table and the processing options that are specific to this extract. If you leave this processing option blank, the system does not run the extract in this batch.
Specify the version of the SCP F4211 Sales History Extract program (R34A435) that the system runs in batch. The SCP F4211 Sales History Extract program selects information from the Sales Order Detail table (F4211). For the version of the SCP F4211 Sales History Extract program that you enter in this processing option, you can set the data selection for this table, and the processing options that are specific to this extract. If you leave this processing option blank, the system does not run the extract in this batch.
Specify whether the system clears the extract file from the previous batch before it adds new data that it extracted in this batch. Values are:
Blank: Do not clear the extract file before adding new data to this batch. Append the new data to any existing data in the extract file.
1: Clear the extract file before adding new data to this batch.
|
Note: If you enter 1 in this field but leave the Inventory Balance Extract Version (R34A460) processing option blank, the system still clears the extract file. |
Specify the key value that is associated with the path name of the extract file. The key value must be a valid entry in the Integration File Definition table (F34A11). You enter path names and keys in the Integration File Definitions program (P34A11). You must enter a key value in this processing option if you specified a version for the SCBM Work Order Package program (R34A910).
Specify the key value that is associated with external commands to be executed immediately before this extract program is run. The key value must be a valid entry in the Integration File Definition table (F34A11). You enter path names and keys in the Integration File Definitions program (P34A11). You can use the commands that are associated with this key to execute a script (such as an FTP script) to retrieve data, run an external program, or perform most command-line processing.
Specify the key value that is associated with external commands to be executed immediately after this extract program is run. The key value must be a valid entry in the Integration File Definition table (F34A11). You enter path names and keys in the Integration File Definitions program (P34A11). You can use the commands associated with this key to execute a script (such as an FTP script) to retrieve data, run an external program, or perform most command-line processing.
Specify the key value that is associated with the path name of the extract file. The key value must be a valid entry in the Integration File Definition table (F34A11). You enter path names and keys in the Integration File Definitions program (P34A11). You must enter a key value in this processing option if you specified a version for the Sales History Table (F42119) (R34A425) or the Sales Detail Table (F4211) (R34A435) extracts.
Specify the version of the SCP Item UOM Extract program (R34A480) that the system runs in this batch. The extract program selects item and branch information from the Item Branch File table (F4102) and item unit of measure information from both the Item Master (F4101) and the Unit of Measure Standard Conversion table (F41003). The extract program creates two separate extract files. You must enter keys for both extract files on this tab to run the extract program. For the version of the SCP Item UOM Extract program that you enter in this processing option, you can set the data selection for this table. If you leave this processing option blank, the system does not run the extract within this batch.
Specify whether the system clears the extract file from the previous batch before it adds newly extracted data to the batch. Values are:
Blank: Do not clear the extract file before adding new data to this batch. Append the new data to any existing data in the extract file.
1: Clear the extract file before adding new data to this batch.
|
Note: If you enter 1 in this field and leave the Inventory Balance Extract Version (R34A460) processing option blank, the system still clears the extract file. |
Specify the key value that is associated with the path name of the extract file. The key value must be a valid entry within the Integration File Definition table (F34A11). You enter path names and keys in the Integration File Definitions program (P34A11). You must enter a key value in this processing option if you specified a version for the SCBM Work Order Package program (R34A910).
Specify the key value that associated with the path name of the extract file. The key value must be a valid entry within the Integration File Definition table (F34A11). You enter path names and keys in the Integration File Definitions program (P34A11). You must enter a key value in this processing option if you specified a version for the SCBM Work Order Package program (R34A910).
Specify the key value that is associated with external commands to be executed immediately before the extract program is run. The key value must be a valid entry in the Integration File Definition table (F34A11). You enter path names and keys in the Integration File Definitions program (P34A11). You can use the commands associated with this key to execute a script (such as an FTP script) to retrieve data, run an external program, or perform most command-line processing.
Specify the key value that is associated with external commands to be executed immediately after the extract program is run. The key value must be a valid entry in the Integration File Definition table (F34A11). You enter path names and keys in the Integration File Definitions program (P34A11). You can use the commands associated with this key to execute a script (such as an FTP script) to retrieve data, run an external program, or perform most command-line processing.
Specify the version of Process Branch Information program (R34A470) that the system runs in this batch. The Process Branch Information extract program selects branch and plant information from the Inventory Constants table (F41001). You set the data selection for the Inventory Constants table for the version of the Process Branch Information program that you enter in this field. If you leave this field blank, the system does not run the extract in batch.
Specify whether the system clears the extract file from the previous batch before it adds new data that it extracted in this batch. Values are:
Blank: Do not clear the extract file before adding new data to this batch. Append the new data to any existing data in the extract file.
1: Clear the extract file before adding new data to this batch.
|
Note: If you enter 1 in this field but leave the Inventory Balance Extract Version (R34A460) processing option blank, the system still clears the extract file. |
Specify the key value that is associated with the path name of the extract file. The key value must be a valid entry in the Integration File Definition table (F34A11). You enter path names and keys in the Integration File Definitions program (P34A11). You must enter a key value in this processing option if you specified a version for the SCBM Work Order Package program (R34A910).
Specify the key value that is associated with external commands to be executed immediately before this extract program is run. The key value must be a valid entry in the Integration File Definition table (F34A11). You enter path names and keys in the Integration File Definitions program (P34A11). You can use the commands associated with this key to execute a script (such as an FTP script) to retrieve data, run an external program, or perform most command-line processing.
Specify the key value that is associated with external commands to be executed immediately after this extract program is run. The key value must be a valid entry on the Integration File Definition table (F34A11). You enter path names and keys in the Integration File Definitions program (P34A11). You can use the commands associated with this key to execute a script (such as an FTP script) to retrieve data, run an external program, or perform most command-line processing.
Specify the version of the SCP Customer Master Information Extract program (R34A530) that the system runs in batch. The extract program selects customer information from the Customer Master by Line of Business table (F03012). For the version of the SCP Customer Master Information Extract program that you enter in this processing option, you can enter data selection for the table. If you leave this processing option blank, the system does not run the extract within this batch.
Specify whether the system clears the extract file from the previous batch before it adds new data that it extracted to the batch. Values are:
Blank: Do not clear the extract file before adding new data to this batch. Append the new data to any existing data in the extract file.
1: Clear the extract file before adding new data to the batch.
|
Note: If you enter 1 in this field but leave the Inventory Balance Extract (R34A460) version processing option blank, the system still clears the extract file. |
Specify the key value that is associated with the path name of the extract file. The key value must be a valid entry in the Integration File Definition table (F34A11). You enter path names and keys in the Integration File Definitions program (P34A11). You must enter a key value in this processing option if you specified a version for the SCBM Work Order Package program (R34A910).
Specify the key value that is associated with external commands to be executed immediately before the extract program is run. The key value must be a valid entry in the Integration File Definition table (F34A11). You enter path names and keys in the Integration File Definitions program (P34A11). You can use the commands associated with this key to execute a script (such as an FTP script) to retrieve data, run an external program, or perform most command-line processing.
Specify the key value that is associated with external commands to be executed immediately after the extract program is run. The key value must be a valid entry in the Integration File Definition table (F34A11). You enter path names and keys in the Integration File Definitions program (P34A11). You use the commands associated with this key to execute a script (such as an FTP script) to retrieve data, run an external program, or perform most command-line processing.
Specify whether the processor is called for the Oracle Demantra integration. Values are:
Blank: Not used for Oracle Demantra integration.
1: Used for Oracle Demantra integration. The system uses the MDE date format, semicolon (;) flat file delimiter, and double quotation mark (") text qualifier to format the extracts. This formatting overrides the formatting set in the Planning Integration Constants, hard-coding the output to be compatible with Oracle Demantra applications.
Selecting this option also augments the sales order history and item extracts to better integrate with Oracle Demantra Demand Management.
Specify the version of the Future List Price Extract program (R45529) that the system runs in this batch. This extract program selects information from the Item Base Price table (F4106). For the version of the Future List Price Extract program that you enter in this processing option, you can set data selection for this table. If you leave this option blank, the system does not run the extract in this batch.
Specify whether the system clears the extract file from the previous batch before it adds new data that it extracted in this batch. Values are:
Blank: Do not clear the extract file before adding new data to this batch. Append the new data to any existing data in the extract file.
1: Clear the extract file before adding new data to this batch.
|
Note: If you enter 1 in this field and leave the Future List Price Extract Version (R45529) processing option blank, the system clears the extract file. |
Specify the key value that is associated with the path name of the extract file. The key value must be a valid entry in the Integration File Definition table (F34A11). You enter path names and keys in the Integration File Definitions program (P34A11). You must enter a key value in this option if you specified a version for the Future List Price Extract program (R45529).
Specify the key value that is associated with external commands to be executed immediately before this extract program is run. The key value must be a valid entry in the Integration File Definition table (F34A11). You enter path names and keys in the Integration File Definitions program (P34A11). You use the commands associated with this key to execute a script (such as an FTP script) to retrieve data, run an external program, or perform most command-line processing.
Specify the key value that is associated with external commands to be executed immediately after this extract program is run. The key value must be a valid entry on the Integration File Definition table (F34A11). You enter path names and keys in the Integration File Definitions program (P34A11). You use the commands that are associated with this key to execute a script (such as an FTP script) to retrieve data, run an external program, or perform most command-line processing.
Specify the version of the Item Cost Extract (R41053) the system runs when the SCP Outbound Processor (R34A400) program runs. If you leave this processing option blank, the extract does not run.
Enter a 1 to clear the file before running extract
Use this processing option to specify the key value associated with the path name of the extract file. The key value must be a valid entry in the Integration File Definition table (F34A11). You enter path names and keys in the Integration File Definitions program (P34A11). You must enter a key value in this processing option if you specified a version for the Item Cost Extract program (R41053).
Specify a user-defined key that is associated with a file definition (such as a flat file path name) or a command line for an external function that is stored in the Integration File Definition table (F34A11).
Specify a user-defined key that is associated with a file definition (such as a flat file path name) or a command line for an external function that is stored in the Integration File Definition table (F34A11).
This section provides an overview of the SCP Inbound Process program and discusses how to:
Run the SCP Inbound Processor program.
Set processing options for the SCP Inbound Processor (R34A410).
The SCP Inbound Processor program (R34A410) program transfers flat-file imports from the Oracle Demantra system to the JD Edwards EnterpriseOne system.
Select Planning & Scheduling (G34A), Planning Inbound Processor.
Processing options enable you to specify the default processing for programs and reports.
Specify the key value that is associated with the path name of the EnterpriseOne inbound control file. The key value must be a valid entry in the Integration File Definition table (F34A11). You can enter path names and keys in the Integration File Definitions program (P34A11). This processing option is required.
Specify the key value that is associated with the path name of the inbound control file. The key value must be a valid entry in the Integration File Definition table (F34A11). You can enter path names and keys in the Integration File Definitions program (P34A11). You must set a key value in this field if you set the Batch Control processing option to 1.
Activate EnterpriseOne-related batch control. Values are:
Blank: Do not verify that the previous JD Edwards EnterpriseOne batch is done before starting the batch. Start a new batch regardless of whether JD Edwards EnterpriseOne has completed processing the previous batch associated with this control file.
1: Verify that the previous JD Edwards EnterpriseOne batch is complete before starting the batch. If the previous batch is not complete, do not run this batch.
|
Note: Turn off batch control only under special conditions, for example for demos and testing when batch control is not needed, the first time you run the batch associated with this control file; or when you must reset the batch control file settings because the control file was deleted. |
Activate SCP-related batch control. Values are:
Blank: Do not verify that SCP sent a new batch before processing the inbound files. Process the inbound files regardless of whether SCP sent a new batch.
1: Verify that SCP sent a new batch before processing the inbound files.
|
Note: Turn off batch control only under special conditions, for example for demos and testing when batch control is not needed, the first time you run the batch associated with this control file; or when you must reset the batch control file settings because the control file was deleted. |
Enter the address book number of the person who receives a notification when an error occurs during batch processing. This person receives messages through the work center. If you leave this option blank, the system does not send out a notification when errors occur.
Specify the key value that is associated with the path name of the error log created in the batch. The key value must be a valid entry in the Integration File Definition table (F34A11). You can enter path names and keys in the Integration File Definitions program (P34A11). The error log is a text file that contains batch status information and record counts. The same information appears on the standard report produced by this batch program. If you leave this option blank, the system does not write the error log text file but still produces the standard report output.
Specify the key value that is associated with external commands to be executed before individual import programs run. The key value must be a valid entry in the Integration File Definition table (F34A11). You can enter path names and keys on the Integration File Definitions program (P34A11). You can use the commands associated with this key to execute a script (such as an FTP script) to retrieve data, run an external program, or perform most command-line processing.
Specify the key value that is associated with external commands to be executed after any individual import programs run. The key value must be a valid entry in the Integration File Definition table (F34A11). You can enter path names and keys in the Integration File Definitions program (P34A11). You can use the commands associated with this key to execute a script (such as an FTP script) to send data, run an external program, or perform most command-line processing.
Specify the version of the SCP Inbound Forecasts program (R34A485) the system runs in this batch. If you leave this processing option blank, the system does not run the import in this batch.
|
Note: This program populates the Forecast table (F3460) with forecast information that is passed in from Supply Chain Planning. You can set processing options that are specific to this import program for the Forecasts Import version (R34A485), which you enter in this field. If you leave this processing option blank, the system does not run the import in this batch. |
Specify whether to clear the import file after the data in the file has been processed. Values are:
Blank: Do not clear the import file after processing the batch. Save the incoming data in the import file.
1: Clear the import file after processing the batch.
|
Note: If you enter 1 in this field but leave the SCP Inbound Forecasts Version processing option blank, the system still clears the import file. |
Specify the key value that is associated with the path name of the import file. The key value must be a valid entry in the Integration File Definition table (F34A11). You can enter path names and keys on the Integration File Definitions program (P34A11). You must enter a key value in this field if you entered a version in the MRP Messages Import Version (R34A490) processing option.
Specify the key value that is associated with external commands to be executed before this import program runs. The key value must be a valid entry in the Integration File Definition table (F34A11). You can enter path names and keys in the Integration File Definitions program (P34A11). You can use the commands associated with this key to execute a script (such as an FTP script) to retrieve data, run an external program, or perform most command-line processing.
Specify the key value that is associated with external commands to be executed after this import program runs. The key value must be a valid entry in the Integration File Definition table (F34A11). You can enter path names and keys in the Integration File Definitions program (P34A11). You can use the commands associated with this key to execute a script (such as an FTP script) to retrieve data, run an external program, or perform most command-line processing.
Specify the version of the Inbound Promotional Pricing (R45640) the system uses to run this batch. If you leave this processing option blank, the system does not run the import in the batch.
|
Note: This program populates the Inbound Promotional Pricing table (F4572Z1) with promotional data. |
Specify whether the system clears the import file after processing the data. Values are:
Blank: Do not clear the import file after processing the batch. Save the incoming data on the import file.
1: Clear the import file after processing the batch.
|
Note: If you enter a 1 in this field but leave the Inbound Promotional Pricing Version (R45640) processing option blank, the system still clears the import file. |
Specify the key value that is associated with the path name of the import file. The key value must be a valid entry in the Integration File Definition table (F34A11). You can enter path names and keys on the Integration File Definitions program (P34A11). You must enter a key value in this field if you entered a version in the MRP Messages Import Version (R34A490) processing option.
Specify the key value that is associated with external commands to be executed before the import program runs. The key value must be a valid entry in the Integration File Definition table (F34A11). You can enter path names and keys in the Integration File Definitions program (P34A11). You can use the commands associated with this key to execute a script (such as an FTP script) to retrieve data, run an external program, or perform most command-line processing.
Specify the key value that is associated with external commands to be executed after this import program runs. The key value must be a valid entry in the Integration File Definition table (F34A11). You can enter path names and keys in the Integration File Definitions program (P34A11). You can use the commands associated with this key to execute a script (such as an FTP script) to retrieve data, run an external program, or perform most command-line processing.
Specify if the processor is called for Oracle Demantra integration. Values are:
Blank: Not used for Oracle Demantra integration.
1: Used for Oracle Demantra integration.
This section provides an overview of the SCP Inbound Forecasts program and discusses how to:
Run the SCP Inbound Forecasts program.
Set processing options for SCP Inbound Forecasts (R34A485).
A forecast generated in Oracle Demantra originates from data created in the Oracle Demantra Demand Management system or in the Predictive Trade Planning system. Generally, customers who use both Demand Management and Predictive Trade Planning, most often use Predictive Trade Planning data for forecasting. However, you can use the Inbound Forecast program (R34A485) to denote a different forecast by changing the forecast type if multiple forecasts are desired.
A forecast consists of information such as base, lift, and cannibalization numbers that together comprise a final forecast number. The base represents the standard expected forecast quantity, and the lift represents the additional demand expected due to promotions. The Oracle Demantra system sends this information in the form of a consolidated number as part of the out-of-box workflow. Cannibalization information is also likely to be too granular to require a separate forecast; however the same solution can be applied. The JD Edwards EnterpriseOne Forecasting system provides the functionality to consolidate these different forecast types
Select Planning & Scheduling (G34A), Planning Inbound Processor.
Complete the following steps:
On the Available Versions form, select a version of SCP Inbound Processor (R34A410).
From the Row menu, select Processing Options.
On the Processing Options form select Forecasts tab
Indicate which version of the SCP Inbound Forecasts program you want the system to run.
Click OK.
Processing options enable you to specify the default processing for programs and reports.
Specify the default forecast type the system uses when adding new forecasts.
Specify the fiscal date pattern.