## Transferring Data Between JD Edwards EnterpriseOne and Demantra Products

This chapter discusses how to:

- Customize RunUBE commands.

- Customize scripts for integrating JD Edwards EnterpriseOne and Oracle Demantra products.

- Model the integration solution.

- Configure JD Edwards EnterpriseOne for integration.

- Run the SCP Outbound Processor program.

- Run the SCP Inbound Processor program.

- Run the SCP Inbound Forecasts program.

### Customizing RunUBE Commands

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

Generating XML Files

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:

1. From the command line of the JD Edwards EnterpriseOne server, select the e1_system_bin32 folder.

2. In the command line, enter runubexml G CREATE_XML jdeRequest.xml. The system creates the jdeRequest.xml file in the same folder.

3. 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 that you want 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.

4. Save the changes to the jdeRequest.xml file.

5. 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.

6. For the incremental report (R34A400_incr.xml, which only extracts SalesOrderHistory 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 at the end of the file:

   Field | Description
   FromDays | 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 FromDays and ThruDays fields are left blank, the value is assumed to be 0, which will extract only today's historical data.
   ThruDays | 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 FromDays and ThruDays fields are left blank, the value is assumed to be 0, which will extract 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 FromDays and ThruDays fields.

   Note. Initially, use these FromDays and ThruDays 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 will have to re-create the XML template.

### Customizing Scripts for JD Edwards EnterpriseOne Integration with Oracle Demantra Products

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.

#### Customizing Scripts for JD Edwards EnterpriseOne Integration With Oracle Demantra Demand Management

Three series of scripts are used 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: runubexml_full.bat runubexml_incr.bat runubexml_item.bat runubexml_loc.bat backup_forecast.bat upload_forecast.bat
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: runextracts_full.bat runextracts_incr.bat runextracts_item.bat runextracts_loc.bat runupload.bat
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): R34A400_full.xml R34A400_incr.xml R34A400_item.xml R34A400_loc.xml R34A410_fcst.xml 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): postextract.bat postupload.bat

Scripts Called by the Oracle Demantra Demand Management Workflows

For the Oracle Demantra Demand Management integration, the following six scripts are called by five Oracle Demantra workflows:

Oracle Demantra Workflow | Oracle Demantra Script | Result
E1 Full Download Purpose: Download all five extracts from JD Edwards EnterpriseOne: Branch.txt, Customer.txt, Item.txt, ItemBranch.txt, and SalesOrderHistory.txt | runubexml_full.bat | Removes all old extracts, done.txt, and ube_errors.txt files from the demantra_install_folder\ e1_integration\e1_files folder. Calls the runextracts_full.bat script in the e1_environment_ube_launch_script_folder on the JD Edwards EnterpriseOne server.
E1 Incremental Download Purpose: Download the SalesOrderHistory extract from JD Edwards EnterpriseOne. | runubexml_incr.bat | Removes all old extracts, done.txt, and ube_errors.txt files from the demantra_install_folder\ e1_integration\e1_files folder Calls the runextracts_incr.bat script in the e1_environment_ube_launch_script_folder on the EnterpriseOne server.
E1 Items Download Purpose: Download two extracts from JD Edwards EnterpriseOne: Item.txt and ItemBranch.txt | runubexml_item.bat | Removes all old extracts, done.txt, and ube_errors.txt files from the demantra_install_folder\ e1_integration\e1_files folder Calls the runextracts_item.bat script in the e1_environment_ube_launch_script_folder on the EnterpriseOne server.
E1 Locations Download Purpose: Download three extracts from JD Edwards EnterpriseOne: Branch.txt, Customer.txt, and SalesOrderHistory.txt | runubexml_loc.bat | Removes all old extracts, done.txt, and ube_errors.txt files from the demantra_install_folder\ e1_integration\e1_files folder Calls the runextracts_loc.bat script in the e1_environment_ube_launch_script_folder on the EnterpriseOne server.
E1 Upload Purpose: Back up old forecasts to a backup folder. Generate a new forecast from Oracle Demantra Demand Management into the demantra_install_folder\ e1_integration\e1_files folder. Upload the forecast to JD Edwards EnterpriseOne with the name Forecast.txt. | backup_forecast.bat and upload_forecast.bat | The backup_forecast.bat script moves all old forecasts in the demantra_install_folder\e1_integration\e1_files folder to a backup folder. The upload_forecast.bat script: Deletes the old synchronization file (upload_done.txt) and error file (forecast_errors.txt) from the demantra_install_folder\ e1_integration\e1_files folder. Copies the new forecast file (forecast*.txt) from the demantra_install_folder\ e1_integration\e1_files to the E1_input_forecast_folder on the EnterpriseOne server with the name Forecast.txt.

Note. All scripts are located in the demantra_install_folder\e1_integration folder.

UBE Launch Scripts in the JD Edwards EnterpriseOne Server for Demand Management

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.

Oracle Demantra Workflow and Script | UBE Launch Scripts | Results
Workflow: E1 Full Download Script: runubexml_full.bat | runextracts_full.bat | Removes all old extracts in the e1_output_folder Removes the synchronization file (done.txt) from the e1_output folder. Runs the runubexml R34A400_full.xml command where "full" is the name of the version customized to include the Branch, Customer, Item, ItemBranch and SalesOrderHistory extracts. Places generated extracts in the e1_output folder.
Workflow: E1 Incremental Download Script: runubexml_incr.bat | runextracts_incr.bat | Removes all old extracts in the e1_output_folder. Removes the synchronization file (done.txt) from the e1_output folder. Runs the runubexml R34A400_incr.xml command where "incr" is the name of the version customized to include the SalesOrderHistory extract. Places generated extracts in the e1_output folder.
Workflow: E1 Items Download Script: runubexml_item.bat | runextracts_item.bat | Removes all old extracts in the e1_output_folder. Removes the synchronization file (done.txt) from the e1_output folder. Runs the runubexml R34A400_item.xml command where "item" is the name of the version customized to include the Item and ItemBranch extracts. Places generated extracts in the e1_output folder.
Workflow: E1 Loc Download Script: runubexml_loc.bat | runextracts_loc.bat | Removes all old extracts in the e1_output_folder. Removes the synchronization file (done.txt) from the e1_output folder. Runs the runubexml R34A400_loc.xml command where "loc" is the name of the version customized to include the Branch, Customer, and SalesOrderHistory extracts. Places generated extracts in the e1_output folder.
Workflow: E1 Upload Scripts: backup_forecast.bat and upload_forecast.bat | runupload.bat | Removes the synchronization file (forecast_done.txt) from the e1_input_forecast_folder. Runs the runubexml R34A410_fcst.xml command where "fcst" is the name of the version customized to upload the forecast.txt file into JD Edwards EnterpriseOne from the e1_input_forecast_folder.

Note. All UBE launch scripts are located in the e1_environment_ube_launch_ script_ folder

Postprocessing Scripts for Demand Management

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 | Removes the previous synchronization file (done.txt) and error status file (ube_errors.txt) from the e1_output_folder. Copies extracts in the e1_output folder to the demantra_install_folder\ e1_integration\e1_files folder. Creates a new synchronization file (done.txt) in the e1_output_folder. Parses the E1 extract control file for errors (control.txt) and creates an error status file (ube_errors.txt) in the e1_output folder if any errors are found. Copies done.txt and ube_errors.txt (if applicable) to demantra_install_folder\ e1_integration\e1_files folder from the e1_output folder.
Planning Inbound Processor (R34A410) | postupload.bat | Removes the previous synchronization file (upload_done.txt) and error status file (forecast_errors.txt) from the e1_input_forecast_folder. Creates a new synchronization folder (upload_done.txt) in the e1_input_forecast_folder. Parses the E1 extract control file for errors (control.txt) and creates an error status file (forecast_errors.txt) if any errors are found. Copies upload_done.txt and forecast_errors.txt (if applicable) to the demantra_install_folder\ e1_integration\e1_files folder.

Note. Both postprocessing scripts are located in the e1_postprocessing_scripts_ folder.

#### Customizing Scripts for JD Edwards EnterpriseOne Integration With Oracle Demantra Predictive Trade Planning

Three series of scripts are used 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 customization, the scripts need to 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: runubexml_full.bat runubexml_incre.bat runubexml_listprice.bat runubexml_itemcost.bat backup_promotion_pricing.bat upload_promotion_pricing.bat upload_delete_promopricing.bat
demantra_install_folder\e1_files | Demantra | Location for all extracts, Oracle Demantra promotion, deduction, synchronization, and error files.

Scripts Called by the Oracle Demantra Predictive Trade Planning Workflows

For the Oracle Demantra Predictive Trade Planning integration the following seven scripts called by five Oracle Demantra workflows:

Oracle Demantra Workflow | Oracle Demantra Script | Results
E1ToPTP_FullDownLoad Purpose: Download six extracts from JD Edwards EnterpriseOne: Branch.txt, Customer.txt, Item.txt, ItemBranch.txt, SalesOrderHistory. txt, and PriceHistory.txt | runubexml_full.bat | Removes all old extracts, done.txt, and ube errors.txt files from the demantra install folder\ e1_ integration\e1 files folder. Calls the runextracts full.bat script in the e1_ environment ube launch script folder on the JD Edwards EnterpriseOne server.
E1ToPTP_incre_download Purpose: Increment download of four extracts from JD Edwards EnterpriseOne: Customer.txt, Item.txt, SalesOrderHistory. txt, and PriceHistory.txt | runubexml_incr.bat | Removes all old extracts, done.txt, and ube errors.txt files from the demantra install folder\ e1_ integration\e1 files folder. Calls the runextracts incr.bat script in the e1_ environment ube launch script folder on the EnterpriseOne server.
E1ToPTP_PromoPrice_DownLoad Purpose: Download one extract from JD Edwards EnterpriseOne: ListPrice.txt | runubexml_listprice.bat | Removes all old extracts, done.txt, and ube errors.txt files from the demantra_install_folder\e1_integration files folder. Calls the runextracts_listprice.bat script in the e1_ environment ube launch script folder on the EnterpriseOne server.
E1ToPTP_PromoCost_DownLoad Purpose: Download one extract from JD Edwards EnterpriseOne: ItemCost.txt | runubexml_itemcost.bat | Removes all old extracts, done.txt, and ube errors.txt files from the demantra_install_folder\e1_integration files folder. Calls the runextracts_itemcost.bat script in the e1_ environment ube launch script folder on the EnterpriseOne server.
PTPToE1_UploadPromotionPrices Purpose: Backup old promotion price to a backup folder. Generate the deleted promotion price from Oracle Demantra Demand Management into the demantra_install_folder\e1_integration files folder. Delete_PromoPricing*.txt. Deleted Promotional pricing consists of promotions that were deleted, canceled, or removed in the Demantra system. Launch the upload_delete_promopricing.bat. Generate the edited and new promotion pricing from Oracle Demantra into the Demantra install folder \e1_integration files folder. PromotionPricing*.txt Launch the upload_promotion_pricing.bat | backup_promotion_pricing.bat upload_promotion_pricing.bat upload_delete_promopricing.bat | The backup_promotion_pricing.bat script moves all old edited and deleted promotion price files in the demantra_install_folder\el_integration files folder to a backup folder. The upload_promotion_pricing.bat and upload_delete_promopricing.bat scripts : Delete the old synchronization file and error file from the demantra_install_folder\el_integration files folder. Copy the edited and deleted promotion price files (PromotionPricing*.txt and Delete_PromoPricing.txt) from the demantra_install_folder\el_integration files to the E1_ input PromotionPricing folder on the EnterpriseOne server with the name PromotionPricing.txt and Delete_PromoPricing.txt

Note. All scripts are located in the demantra_install_folder\e1_integration folder.

Postprocessing Scripts for Predictive Trade Planning

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 | Removes the previous synchronization file (done.txt) and error status file (ube errors.txt) from the e1_ output folder. Copies extracts in the e 1 output folder to the demantra install folder\ e1_integration\e1_files folder. Creates a new synchronization file (done.txt) in the e1 output folder. Parses the E1 extract control file for errors (control.txt) and creates an error status file (ube errors.txt) in the e1 output folder if any errors are found. Copies done.txt and ube errors.txt (if applicable) to demantra install folder\ e1_ integration\e1_files folder from the e1 output folder.
Planning Inbound Processor (R34A410) | Postupload_delete.bat | Removes the previous synchronization files (upload_done.txt) (upload_delete_promopricing_done.txt) and error status file (promopricing_errors.txt) from the e1 input pricing folder. Creates new synchronization files (upload done.txt) and (upload_delete_promopricing_done.txt) in the e1 input pricing folder. Parses the E1 extract control file for errors (control.txt) and creates an error status file (promopricing_errors.txt) if any errors are found. Copies (upload_done.txt) and upload_delete_promopricing_done.txt and promopricing_errors.txt (if applicable) to demantra install folder\ e1_integration\e1_files folder.
Planning Inbound Processor (R34A410) | Postupload.bat | Removes the previous synchronization files (upload_done.txt) and (upload_promopricing_done.txt) and error status file (promotions_errors.txt) from the e1 input pricing folder. Creates new synchronization file (upload_done.txt) and (upload_promopricing_done.txt) in the e1 input pricing folder. Parse the E1 extract control file for errors (control.txt) and creates an error status file (promotions_errors.txt) if any errors are found. Copies upload_done.txt and upload_promopricing_done.txt and promotions_errors.txt (if applicable) to Demantra install folder \e1_integration\e1_files folder.

Note. All three postprocessing scripts are located in the e1_postprocessing_scripts_ folder.

#### Customizing Scripts for JD Edwards EnterpriseOne Integration With Oracle Demantra Deductions and Settlement Management

Three series of scripts are used 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 customization, the scripts need to 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: runubexml deduction.bat runubexml confirm.bat backup deduction.bat backup claim.bat upload claim.bat upload deduction.bat
e1_integration\el files | Demantra | Location for all extracts, Oracle Demantra forecast, synchronization, and error files.

Scripts Called by the Oracle Demantra Deductions and Settlement Management Workflows

For the Oracle Demantra Deductions and Settlement Management integration there are six scripts called by four Oracle Demantra workflows:

Oracle Demantra Workflow | Oracle Demantra Script | Result
E1ToDSM New Deduction Download Purpose: Download deduction extracts from JD Edwards EnterpriseOne: Deduction.txt. | runubexml_deduction.bat | Removes all old extracts, done.txt, and ube errors.txt files from the demantra_install_folder\ e1_integration\e1 files folder. Calls the RunExtract_Deductions.bat script in the e1_ environment ube launch script folder on the JD Edwards EnterpriseOne server.
E1 APConfirm Import Purpose: Download approve payment deduction extracts from JD Edwards EnterpriseOne: APConfirm.txt. | runubexml_confirm.bat | Removes all old extracts, done.txt, and ube errors.txt files from the demantra install folder\ e1_ integration 1 files folder Calls the RunExtract_Claims.bat script in the e1_ environment ube launch script folder on the EnterpriseOne server.
DSMToE1 Deduction Export Purpose: Backup old deduction to a backup folder. Generate new deduction from Oracle Demantra Demand Management into the demantra install folder\ e1_ integration\e 1 files folder. Upload new deduction to JD Edwards EnterpriseOne with the DeductionDispositions .txt. file | backup_deduction.bat upload_deduction.bat | The backup_deduction.bat script moves all old deduction files in the demantra install folder\el integration^ 1 files folder to a backup folder. The upload_deduction.bat script does the following: Deletes the old synchronization file (upload_deduction_done.txt) and error file (deduction_errors.txt) from the demantra install folder\el integration^ 1 files folder. Copies the deduction files (DeductionDispositions .txt) from the demantra install folder\el integration^ 1 files to the E1_ input DeductionDispositions folder on the EnterpriseOne server with the name DeductionDispositions .txt
DSMToE1 Claim Export Purpose: Backup old claim to a backup folder. Generate new claim from Oracle Demantra Demand Management into the demantra install folder\ e1_ integration\e 1 files folder. Upload new deduction to JD Edwards EnterpriseOne with the Claim .txt file | backup_claim.bat upload_claim.bat | The backup_claim.bat script moves all old claim files in the demantra install folder\el integration^ 1 files folder to a backup folder. The upload_claim.bat script does the following: Deletes the old synchronization file (upload_claim_done.txt) and error file (claim_errors.txt) from the demantra install folder\el integration^ 1 files folder. Copies the claim files (Claim .txt) from the demantra install folder\el integration^ 1 files to the E1_ input claim folder on the EnterpriseOne server with the name Claim .txt

Note. All scripts are located in the demantra_install_folder\e1_integration folder.

### Modeling the Integration Solution

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.

#### Levels in JD Edwards EnterpriseOne

JD Edwards EnterpriseOne requires only three leaf levels: item , customer/company and branch. Each of these leaf levels can have several significant attributes which need to be mapped to the parent level. This mapping is not fixed and varies by implementation.

Category Codes as Levels

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 pre-configured 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:

1. Map the information that is held in each category code in JD Edwards EnterpriseOne.

2. 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.

3. 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:

1. Open the Integration Template model.

2. 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.

3. 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.

4. Upgrade the existing model. Do not build a new model.

5. Open Oracle Demantra Demand Management and grant full control to the category code levels that are used.

Changing Levels and Hierarchy

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 will maintain 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 will be ejected during loading.

- Always upgrade the existing model instead of building a new model.

#### Customer and Company Mapping in JD Edwards EnterpriseOne

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.

#### Multi-Site Recommendations

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.

#### Null Handling During Integration

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, they are replaced by a different string. 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

"Open With" worksheets should be unfiltered. If you wish 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 will be null.

#### Worksheet Filters

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.

#### Analytic Engine Guidelines

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 is used to generate or regenerate 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 a number of 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 are 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.

### Configuring JD Edwards EnterpriseOne for Integration

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.

#### Understanding JD Edwards EnterpriseOne Configuration

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.

#### Customizing JD Edwards EnterpriseOne Applications to Support Oracle Demantra Workflows

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)

#### Planning Integration Constants and Planning File Definitions

This section discusses Planning Integration Constants and Planning File Definitions.

Planning Integration Constants

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.

Planning File Definitions

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 filename translation is made. For example, if a batch program is set up to run on a Windows NT EnterpriseOne server, the filenames that the program uses must be NT-compliant filenames. 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 filenames 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.

#### Forms Used to Set Up Planning Integration Constants and Planning File Definitions

Form Name | FormID | 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.

#### Setting Up Planning Integration Constants

Access the Integration Constants form.

Select the General tab.

Date Format | 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.
Flat File Delimiter | 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.
Text Qualifier | 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.
Weekly/Monthly Forecast | 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.

#### Setting Up Planning File Definitions

Access the Integration File Definitions form.

Key | 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.
File Definition | Specify the name of the flat file, including the directory path where the file exists or where the system executes a command line.

### Running the SCP Outbound Processor Program

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).

#### Understanding the SCP Outbound Processor Program

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: Inventory Constants (F41001). Business Unit Master (F0006). Address Book (F0101). Address By Date (F0116).
SCP Customer Master Information Extract (R34A530) | Demand Management Predictive Trade Planning | Use this batch program to retrieve: Customer master information from the Address Book Master table (F0101). Customer information from the Customer Master by Line of Business table (F03012). Information from the Address by Date table (F0116). Information from the Address Book - Contact Phone Numbers table (F0115). Information from the Address Book - Who's Who table (F0111).
SCP Item UOM Extract (R34A480) | Demand Management Predictive Trade Planning | Use this batch program to retrieve: Item branch/plant and unit of measure information that is extracted from the Item Branch table (F4102) and the Item Master table (F4101), thus creating two separate extract files Items by category codes (and other item branch information) from the Item Branch table Planning unit of measure, using the user-specified planning unit of measure Shipping unit of measure, using the user-specified aggregate shipping unit of measure Weight and volume units of measure and conversion factors 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: Sales history information that is extracted from the Sales Order History table (F42119) Sales orders with specific item category codes (and other sales detail information) from the Sales Order History File table Sales orders by document type, line type, and status, using the Supply/Demand Inclusion Rules program (P34004) 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: Sales order information that is extracted from the Sales Order Detail File table (F4211) Sales orders with specific item category codes (or other sales detail information), using data selection from the Sales Order Detail File table Sales orders by document type, line type, and status, using the Supply/Demand Inclusion Rules program (P34004) 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 that you want 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.

#### Running the SCP Outbound Processor Program

Select Planning & Scheduling (G34A), Planning Outbound Processor.

#### Setting Processing Options for the SCP Outbound Processor (R34A400)

Processing options enable you to specify the default processing for programs and reports.

Process 1

1. Control File Definition - EnterpriseOne | 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.
2. Control File Definition - SCP | 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.
3. Batch Control - EnterpriseOne | 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 need to reset the batch control file settings because the control file was deleted.
4. Batch Control - SCP | 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 need to reset the batch control file settings because the control file was deleted.

Process 2

1. Recipient for error notification | 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.
2. Error Log Definition | 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 is produced by this batch program. If you leave this processing option blank, the system does not write the error log text file, but still produces the standard report output.
3. External Function Definition (Beginning of Processing) | 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). The commands that are associated with this key can be used to execute a script (such as an FTP script) to retrieve data, run an external program, or perform most command-line processing.
4. External Function Definition (End of 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). The commands that are associated with this key can be used to execute a script (such as an FTP script) to send data, run an external program, or perform most command-line processing.

Sales History

1. History Extract Version - Sales History Table (F42119) (R34A425) | 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.
2. History Extract Version - Sales Detail Table (F4211) (R34A435) | 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.
3. Clear Extract File | 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.
4. Sales History Extract File Definition | 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).
5. External Function Definition (Beginning of Processing) | 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). The commands that are associated with this key can be used to execute a script (such as an FTP script) to retrieve data, run an external program, or perform most command-line processing.
6. External Function Definition (End of 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). The commands that are associated with this key can be used to execute a script (such as an FTP script) to retrieve data, run an external program, or perform most command-line processing.
7. Price History Extract File Definition | 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.

Items

1. Item Extract Version (R34A480) | 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 if you want 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.
2. Clear Extract File | 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.
3. Extract File Definition - Item Information | 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).
4. Extract File Definition - Units of Measure | 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).
5. External Function Definition (Beginning of Processing) | 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). The commands that are associated with this key can be used to execute a script (such as an FTP script) to retrieve data, run an external program, or perform most command-line processing.
6. External Function Definition (End of 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). The commands that are associated with this key can be used to execute a script (such as an FTP script) to retrieve data, run an external program, or perform most command-line processing.

Branch Plant

1. Branch Plant Extract Version (R34A470) | 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.
2. Clear Extract File | 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.
3. Extract File Definition | 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).
4. External Function Definition (Beginning of Processing) | 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). The commands that are associated with this key can be used to execute a script (such as an FTP script) to retrieve data, run an external program, or perform most command-line processing.
5. External Function Definition (End of 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). The commands that are associated with this key can be used to execute a script (such as an FTP script) to retrieve data, run an external program, or perform most command-line processing.

Customer Master

1. Customer Master Extract Version (R34A530) | 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.
2. Clear Extract File | 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.
3. Extract File Definition | 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).
4. External Function Definition (Beginning of Processing) | 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). The commands that are associated with this key can be used to execute a script (such as an FTP script) to retrieve data, run an external program, or perform most command-line processing.
5. External Function Definition (End of 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). The commands that are associated with this key can be used to execute a script (such as an FTP script) to retrieve data, run an external program, or perform most command-line processing.

Demantra

1. Indicate if the processor is used for Demantra Integration | 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 MDE date format, semicolon (;) flat file delimiter, and double quotation mark (") text qualifier is used 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.

List Price

1. Future List Price Extract Version (R45529) | 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.
2. Clear Extract File | 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.
3. Extract File Definition | 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).
4. External Function Definition (Beginning of Processing) | 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). The commands that are associated with this key can be used to execute a script (such as an FTP script) to retrieve data, run an external program, or perform most command-line processing.
5. External Function Definition (End of 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). The commands that are associated with this key can be used to execute a script (such as an FTP script) to retrieve data, run an external program, or perform most command-line processing.

Item Cost

1. Item Cost Extract Version (R41053) | 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.
2. Clear Extract File | Enter a 1 to clear the file before running extract
3. Extract File Definition | 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).
4. Extract Function Definition (Beginning of Processing) | 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).
5. External Function Definition (End of Processing) | 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).

### Running the SCP Inbound Processor Program

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).

#### Understanding the SCP Inbound Processor Program

The SCP Inbound Processor program (R34A410) program transfers flat-file imports from the Oracle Demantra system to the JD Edwards EnterpriseOne system.

#### Running the SCP Inbound Processor Program

Select Planning & Scheduling (G34A), Planning Inbound Processor.

#### Setting Processing Options for the SCP Inbound Processor (R34A410)

Processing options enable you to specify the default processing for programs and reports.

Process 1

1. Control File Definition - EnterpriseOne | 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.
2. Control File Definition - SCP | 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.
3. Batch Control - EnterpriseOne | 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 need to reset the batch control file settings because the control file was deleted.
4. Batch Control - SCP | 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 need to reset the batch control file settings because the control file was deleted.

Process 2

1. Recipient for error notification | 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.
2. Error Log Definition | 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.
3. External Function Definition (Beginning of Processing) | 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). The commands that are associated with this key can be used to execute a script (such as an FTP script) to retrieve data, run an external program, or perform most command-line processing.
4. External Function Definition (End of 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). The commands that are associated with this key can be used to execute a script (such as an FTP script) to send data, run an external program, or perform most command-line processing.

Forecasts

1. Forecast Import Version (R34A485) | Specify the version of the SCP Inbound Forecasts program (R34A485) that you want the system to run 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.
2. Clear import file | 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.
3. Import File Definition | 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.
4. External Function Definition (Beginning of Processing) | 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). The commands that are associated with this key can be used to execute a script (such as an FTP script) to retrieve data, run an external program, or perform most command-line processing.
5. External Function Definition (End of 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). The commands that are associated with this key can be used to execute a script (such as an FTP script) to retrieve data, run an external program, or perform most command-line processing.

Promotional Pricing

1. Inbound Promotional Pricing Version (R45640) | 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.
2. Clear import file | 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.
3. Import File Definition | 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.
4. External Function Definition (Beginning of Processing) | 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). The commands that are associated with this key can be used to execute a script (such as an FTP script) to retrieve data, run an external program, or perform most command-line processing.
5. External Function Definition (End of 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). The commands that are associated with this key can be used to execute a script (such as an FTP script) to retrieve data, run an external program, or perform most command-line processing.

Demantra

1. Indicate if the processor is used for Demantra Integration | 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.

### Running the SCP Inbound Forecasts Program

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).

#### Understanding the SCP Inbound Forecasts Program

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

#### Running the SCP Inbound Forecasts Program

Select Planning & Scheduling (G34A), Planning Inbound Processor.

Complete the following steps:

1. On the Available Versions form, select a version of SCP Inbound Processor (R34A410).

2. From the Row menu, select Processing Options.

3. On the Processing Options form select Forecasts tab

4. Indicate which version of the SCP Inbound Forecasts program you want the system to run.

5. Click OK.

#### Setting Processing Options for SCP Inbound Forecasts (R34A485)

Processing options enable you to specify the default processing for programs and reports.

Defaults

1. Default Forecast Type | Specify the default forecast type that you want the system to use when adding new forecasts.
2. Fiscal Date Pattern | Specify the fiscal date pattern.