To facilitate the integration, certain one-time setup steps and configurations must be performed to the Oracle EBS planning server.
Additional Information: For additional information, see the Oracle Value Chain Planning Implementation Guide.
This chapter covers the following topics:
To set up the Oracle EBS planning server for this integration
Log in with the Advanced Planning Administrator responsibility.
Create the Oracle VCP Partition by completing the following steps:
Run the concurrent process Create VCP Partitions.
Set the plan partition count to 0.
Set the instance count to 1.
Create the Oracle VCP Planning instance by completing the following steps:
Navigate to Admin, Instances.
Set the instance type to Others.
Ensure that the Enable ATP option is not selected.
Note: Planners must be set up in Oracle EBS and given the appropriate permissions.
Set the following integration profile parameters:
Parameter | Default Value |
---|---|
MSC: E1 Concatenation Character | + |
In the Parameters.txt file, set the Source_Instance parameter to the Oracle VCP Planning instance you created.
Additional Information: For additional information, see User-Maintained Data.
Navigate to Application Developer, Flexfield, Descriptive, Segments.
Enable the descriptive flex field to have the collection name.
In the Application field, enter Advanced Supply Chain Planning and in the Title field, enter MSC_APPS_INSTANCES.
Click Segments.
In the Segments form, make the following entries:
Number | Name | Column |
---|---|---|
1 | Collection Name | ATTRIBUTE15 |
11 | Data Path | ATTRIBUTE13 |
12 | Control File Path | ATTRIBUTE12 |
Click Save.
Navigate to Admin, Instances.
In the Instances form, complete the following fields:
Field | Description |
---|---|
Collection Name | The name of the ERP instance. |
Data Path | The directory on the server that hosts the VCP application server, where the VCP concurrent program locates the DemHistory.dat file.
|
Control File Path | The directory on the server that hosts the VCP application server. This directory contains the T_SRC_SALES_TMPL.ctl control file that loads DemHistory.dat. This is typically in APPL_TOP for msc in the sub- directory msc/12.0.0/patch/115/import. |
Navigate to Advanced Supply Chain Planner, Collections, JD Edwards EnterpriseOne or PeopleSoft, Collect Planning Data.
Run the Collections program.
To view data in the Collections Workbench, select the category set collected from the ERP system.
Click Save.
To retain released data, set the value of the MSC: Retain Released Data to Yes.
The following profile parameters are used by the JDE E1 integration:
Profile Parameter | Description | Default Value | Data Type |
---|---|---|---|
MSC: E1 APS FC URL | URL for the web service used to Launch ODI scenarios from collections program | String | |
MSC: E1 APS ODI URL | URL for the web service used to Launch ODI scenarios from collections program | String | |
MSC: E1 Concatenation Character | Delimiter character in the generated flat files from JDE | + | Character |
MSC: E1APS_BATCH_SIZE | Transaction batch size used in Legacy Collections | 1000 | Integer |
MSC: E1APS_DEM_END_DATE_I N_MONTHS | End date offset in months from the current date used for Demantra Price List collections | Integer | |
MSC: E1APS_DEM_START_DATE _IN_MONTHS | Start date offset in months from the current date used for Demantra Price List collections | Integer | |
MSC: E1APS_DEM_WF_TIME_OU T | Timeout value for Demantra Workflow in seconds | Integer | |
MSC: E1APS_NO_OF_WORKERS | Number of workers for Legacy Collections concurrent program | 3 | Integer |
MSC: E1APS_TIME_OUT | Timeout value in minutes for Legacy collections pre- processor and ODS Load programs | 180 | Integer |
MSC: E1APS_WS_TIME_OUT | Timeout value in seconds for ODI web service | Integer | |
MSC: E1_DBLINK | Database link to ODI Work repository from the apps schema | String |