Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
November 9, 2011: The E1 - VCP Integration (Part 2 of 2) (Doc Id 837233.1). November 17, 2011: Oracle Support Detailed Review of VCP Resources Available from Support (Doc Id 837233.1).
North America: (866) 627-3315 International: +1-706-679-7972 Other Global Toll Free: Doc ID: 1148600.1 For complete details Value Chain Planning Webcast Events, please see Note 837233.1. For complete details on All Other upcoming Oracle Advisor Webcast Events, please Note 398884.1. Do you have any requests for future Advisor Webcast Events? Please email your suggestions to bonnie.adam@oracle.com, subject: Topics of Interest.
Agenda
Overview of Collections and VCP Planning Cycle Overview of the integration Components The Directories Technology Components UBEs and XMLs User Defined Files Staging Tables and Work Repository Tables Implementation Tips Roadmap Product Information Center Troubleshooting Tips Q&A
Acronyms
PIP = Process Integration Pack AIA = Application Integration Architecture ODI = Oracle Data Integrator SOA = Service Oriented Architecture VCP = Value Chain Planning ODS = Operation Data Store PDS = Planning Data Store
Centralized vs. De-centralized (distributed) installation Doc ID145419.1 is excellent resource Stages of Data Collections Refresh Snapshot Process Planning Data Pull moves the data from snapshots and view to the staging tables all named MSC_ST% ODS load Moves the data from MSC_ST% to MSC_% Launches Planning Data Collections Purge Staging Tables to remove data from the MSC_ST staging tables Operation Data Store (ODS) vs. Planning Data Store (PDS)
10
11
AIA
JD Edwards EnterpriseOne AIA PIP Linux 32-bit Windows 32-bit Value Chain Planning Linux 32-bit, 64-bit Windows 32-bit HP UX 64-bit AIX 64-bit SUN Solaris 64-bit Client: Desktop apps SNO and PS
12
12
Chain Planning
13
Architecture Overview
14
Planning
15
Demand Management
16
17
Prior to loading the sales history information into Demantra the Collect Planning Data program loads ODS with base data such as Items, Locations, Customers, Units of Measure, and Price Lists The Collect Sales History program then loads Sales History into Demantra The analytical engine can then be run to generate a statistical forecast The forecast can be reviewed, revised, approved in Demantra and then published back to JDE E1 ERP or to other VCP applications Demantra details will be covered in the Nov webcast
18
19
20
JD Edwards EnterpriseOne
E1 Output Directory
21
E1 Input Directory
Contains the files from VCP/Demantra prior to being loaded into JDE E1
22
Required Components
See note 1363791.1 and PIC 08 E1 VCP Integration Installation Training
JDE-E1 9.0 WLS 11g Database 11g RCU SOA 11g AIA-FP 11g AIA-3.1 ODI 11g JDE-VCP PIP 3.1 Demantra VCP 12.1.3*
E1 9.0
Wolfram
Ptolemy
23
24
If you are using only Demantra products, then only Base.xml, Customer.xml and Calendar.txt are needed from this list
25
PTP
DSM
26
All the above files are assumed to be ; separated value files. Also each of the above User Defined txt files should have a header record otherwise the 1st record will be considered as header and will be ignored and not collected.
27
28
Staging Tables
29
An Example
VCP staging tables VCP base tables Demantra staging tables Demantra base tables
And back
30
An Example
31
32
33
34
Collections
35
36
37
38
Run ASCP
39
Implementation Tip
Skill sets required: VCP Application Consultant / Apps DBA to install EBS (VCP) and apply patches. Middleware Consultant JDE Skills in UBEs & CNC (configurable Network Computing) Set realistic expectations start with an unconstrained plan in phase 1. --- Personal observation Not an Oracle official statement! -- Middle tier requires about 200 GB Middle tier : +/- 10gb RAM to run comfortably EBS (VCP) requires 300 GB which includes db Entire installation would take about a week with the right resources. Patch OS, install middle tier, install VCP configure SOA, weblogic, and ODI run sample data.
40
Restrictions
This integration focuses on discrete manufacturing. For process manufacturing, certain features such as Co-Products, BiProducts and material substitutions are not supported This integration does not support Configure-To-Order or GOP coming in next release (mid 2012) Single sign-on across Value Chain Planning instances and ERP instances is not supported. PIC presentation includes limitations Sourcing rules are not imported for this release. Sourcing rules can be defined on the planning server. Multi-currency is not supported. See 07 E1 VCP Integration JDE EBS Differences on PIC page
41
EDGE
7.1 7.2 7.3
FUSION
42
Roadmap
43
44
References
Product matrix Note 1081971.1 ASCP PIC Note 1349838.1 Demantra PIC Note 1157065.1 ASCP Profile Plan Option Matrix Note 803583.1
45
Troubleshooting
The Integration of E1 VCP has various Oracle application products as described earlier. In the following slides we share the basic troubleshooting techniques which can be used during implementation or during production
46
Troubleshooting
1. Generating Trace and Log for the Collection process
Before we start the collection we need to perform the following steps for enabling trace. Log into System administrator Navigation : System administrator > Profiles > System > select the User SYSADMIN and query the following profile.. Initialization SQL Statement Custom% Set the value of the profile at user level as follows.. ALTER SESSION SET TRACEFILE_IDENTIFIER='SR' max_dump_file_size=unlimited EVENTS='10046 TRACE NAME CONTEXT FOREVER, LEVEL 12 Now log into Advanced planning administrator and launch collections. The concurrent request launched will generate a trace and a log file for itself and for all its spawned requests
47
Troubleshooting
2. Locating trace and log. The concurrent collect planning data launched will create a log file in following location and can be identified by running following query on sql on connecting to VCP database Select * from applsys.fnd_concurrent_requests where request_id =&request_id The above output will provide you the log file path and the oracle_process_id which is the trace id generated. The trace will be located in user_temp_trace parameter path defined in V$parameter Locate the path and get the trace file from the path in v$parameter table Log into unix and get the trace file which has the oracle_process_id from the path in unix.
48
Troubleshooting
3. Accessing ODI data: Click on the operator window and the execution button to know the scenarios listed which are running and which are completed normal/error Expanding the steps shows the details of the scenario and its details Double click on one of the steps shows the details of the step and the execution message box shows the error/message. .
49
Troubleshooting
50
Troubleshooting
4 Generic issues during Implementation Time out error in accessing the machines
The issue could be due to network connectivity and probably checking the connecting cables of machines can resolve time out issues Also can try an option of increasing timeout parameters for the ODI user preference to 20000 so that ODI does not fail with time out Checked for the stats on the tables and analyzing the tables by running gather schema stats. Also can check the load balancing of requests Correct requests time out settings and incompatibility between different concurrent requests of planning to ensure that the requests do not fail with time out errors
51
Troubleshooting
Agent connectivity issue in ODI
Check for the host setup for APS agent on ODI to point to correct host server . Also check the jbdc connector details for JDEOutbound and DTD files for XML on topology manager of ODI Check for wild characters in xml files which can cause the ODI synchronization to fail. Purge old data from VCP which can cause error in pre process monitor ODI may error with unable to read file from JDEOutbound directory and file permissions for the files in JDEOutbound needs to be corrected
Purging data
File permissions
.
2009 Oracle Corporation Proprietary and Confidential 52
Troubleshooting
Knowledge references in MOS for assisting Troubleshooting: NOTE.117129.1 How to get a Trace for And Begin to Analyze a Performance NOTE.141532.1 How To Gather Schema Statistics for Oracle Applications 11i NOTE.280295.1 REQUESTS.sql Script for Parent/Child Request IDs and Trace NOTE.246150.1 APSCHECK.sql Provides Information Needed in Diagnosing GOP NOTE.215187.1 SQLTXPLAIN.SQL - Enhanced Explain Plan and related NOTE.245974.1 FAQ - How to Use Debug Tools and Scripts for the APS Suite NOTE.220115.1 Managing MSCD and MSCX Table spaces for APS Implementations NOTE.137293.1 How to Manage APS Partitions in the MSC Schema NOTE.552415.1 INSTALL ALERT - Setting Up The APS Partitions and Data NOTE.216205.1 Database Initialization Parameters for Oracle Applications NOTE.746824.1 ALERT! - Value Chain Planning (aka Advanced Planning - APS) NOTE. 1357290.1 error in LOADE1UNITSOFMEASUREDATATOAPSPKG NOTE. 1357860.1 UOM Tables Not Correctly Collected In VCP From JDE - No Base UOM And Conversions NOTE. 1357900.1 Site Code Coming In As Null NOTE . 1364049.1 PO Errors Out In msc_st_trading_partners When Supplier Has Multiple Sites
53
To ask a question on the phone line, select *1 on your phone. To ask a question online, use the Q&A area.
Your question will be read aloud in the order received. Question can also be asked on the Value Chain Planning Community
54
Visit the My Oracle Support Community now!! 1. 2. 3. 4. Log into My Oracle Support. Select the Community tab. Select the Enter Here button. Select the Community Name link under the E-Business Suite section of the My Communities Menu on the left side of the window.
55
56
57
58
THANK YOU
59
This document lists 1. 2. 3. 4. 5. The shared directories and their contents The data retrieved by R34A705: The work repository tables used in the integration The staging tables used in the integration The variables used in the integration
1.
The Shared Directories and their contents: a. JDE OUTBOUND Target Application APS staging tables APS staging tables APS staging tables APS staging tables APS staging tables APS staging tables APS staging tables APS staging tables APS staging tables APS staging tables APS staging tables APS staging tables APS staging tables APS staging tables APS staging tables APS staging tables APS staging tables APS staging tables APS staging tables APS staging tables APS staging tables APS staging tables APS staging tables Demantra Demantra Demantra Demantra Demantra Demantra Source User-defined User-defined User-defined User-defined User-defined User-defined User-defined User-defined User-defined User-defined User-defined ERP extract ERP extract ERP extract ERP extract ERP extract ERP extract ERP extract ERP extract ERP extract ERP extract ERP extract ERP extract ERP extract ERP extract ERP extract ERP extract ERP extract ERP extract
File Name Parameters.txt TranslationTable.txt ShiftInformation.txt ShiftInformationDetails.txt ResourceGroups.txt ResourceGroupDetails.txt ForecastDesignators.txt SetupDefinitions.txt SetupTransitions.txt StandardOperationResources.txt StandardUOMConversions.txt Calendar.txt Supplier.xml Customer.xml Base.xml Manufacturing.xml BeginningInventory.xml Distribution.xml PurchaseOrders.xml WorkOrders.xml SalesOrders.xml TransferOrders.xml TimeSeries.xml SalesOrderHistory.txt ListPrice.txt ItemCost.txt PriceHistory.txt APConfirm.txt Deductions.txt
b.
JDE INBOUND JDE E1 JDE E1 JDE E1 JDE E1/PeopleSoft JDE E1 JDE E1 JDE E1 JDE E1 APS extract APS extract APS extract Demantra (transformed file) Demantra (transformed file) A copied file of a Demantra extract A copied file of a Demantra extract A copied file of a Demantra extract
c.
APS INBOUND
DemHistory.dat is the only flat-file written to the APS Input directory. ODI takes SalesOrderHistory.txt files from the JDE E1 Output directory, transforms the file to the correct format, and creates the DemHistory.dat file. In a shared directory environment, the ODI and APS servers must be able to access this directory.
DemHistory.dat
Demantra
d.
DEMANTRA INPUT
Input files for Demantra, PTP, and DSM are written to the Demantra Input directory. ODI reads files from the JDE E1 Output directory, transforms them if necessary, and writes them in this directory. In a shared directory environment, the ODI server and the Demantra database server must be able to access this directory. ListPrice.txt PriceHistory.txt ItemCost.txt APConfirm.txt Deductions.txt Demantra Demantra Demantra Demantra Demantra JDE E1 transformed file JDE E1 transformed file JDE E1 transformed file A copied file of an JDE E1 extract A copied file of an JDE E1 extract
e.
DEMANTRA OUTPUT
Outbound files from Demantra are written to the Demantra Output directory. ODI transforms the files if necessary and stores them in the JDE E1 Input directory before they are imported into JD Edwards EnterpriseOne. In a shared directory environment, the ODI server and the Demantra database server must be able to access this directory. forecast.txt PromotionPricing.txt Delete_PromoPricing.txt DeductionDispositions.txt claim.txt ERP JDE E1 JDE E1 JDE E1 JDE E1 Demantra transformed file Demantra transformed file A copied file of a Demantra extract A copied file of a Demantra extract A copied file of a Demantra extract
2.
Data Retrieved This batch program retrieves information from: Address by Date (F0116) Inventory Constants (F41001) Item Branch File (F4102) Item Cost File (F4105) Item Location File (F41021) ItemMaster table (F4101) Item Units of Measure Conversion Factors (F41002) LocationMaster (F4100) Unit of Measure standard conversion (F41003) Use this batch program to retrieve information from: Item Location File (F41021) Lot Master (F4108) Address BookMaster (F0101) Address by Date (F0116) Item Base Price File (F4106) Item Cross Reference File (F4104) Preference Profile - Inventory Sourcing (F40306) Branch Relationships Master File (F3403) Routing Entries (F4950) User Defined Codes (F0005) Routing Restrictions (F4952) R34A785 Routing Master File (F3003) Bill of Material Master File (F3002) F34A110 F34A120 F34A190 (resource set info) F30008/F30006 (tool, machine, crew calendar information) Purchase Order Detail File table (F4311). Sales Order Detail File table (F4211) Sales Order Header File table (F4201) You can also specify a date in the processing options before which any sales orders with earlier promised dates are excluded from the extraction. WO Supplemental Data Types (F48090) Address Book Master (F0101) Address By Date (F0116) Item Branch (F4102) R34A930 R34A940 Purchase Order Detail File (F4311) Sales Order Header File (F4201) LotMaster (F4108) Work Order Master File (F4801) Work Order Routing (F3112) Work Order Parts List (F3111) Bill of Material Master File (F3002) Work CenterMaster File (F30006) F34A150/F34A120 (resource information) R34A610 The JD Edwards EnterpriseOne calendar information flat file.
VCP Purchase Order Package (R34A750) VCP Sales Order Package (R34A730)
OBDWCAL
The VCP Inbound Processor (R34A820) transfers XML packages from Supply Chain Planning to JD Edwards EnterpriseOne. It is associated with the VCP Outbound Processor (R34A705), which exports JD Edwards EnterpriseOne supply chain management data to Supply Chain Planning. The VCP Inbound Processor can export depending on the configuration of the VCP Inbound Processor, all or part of the data listed: Detailed production plans Forecasts Purchase order messages Transfer order messages This table identifies the data that is retrieved by using each of the import programs: VCP Inbound Detailed Production Plan Package (R34A900) Use this batch program to import detailed production plans from VCP that contain scheduled routings, operations, resources, and the consumed and produced items. Upon receipt, E1 creates, updates, or cancels related manufacturing execution transactions, work order headers, parts list, and routing instructions based on the recommended optimized production plan from VCP. Resource assignments per routing instruction from the production plan are also persisted within E1. The following tables are updated: Work Order Master File (F4801) Work Order Master Tag File (F4801T) Work Order Parts List (F3111) Work Order Routing (F3112) Work Order Routing Resource (F34A150) Item Location File (F41021) Use a processing option to specify the default work order type, a reason code for fixed work orders, and the version of the Manufacturing Work Order Processing program (P48013) to use. Use this batch program to import forecasting information created by SCP Demand Management into the Forecast File table (F3460) after the data is formatted by VCP. Use a processing option to specify the default forecast type if the forecast type is not included in the record. Before it adds new forecasts, the VCP Inbound Forecasts Package program deletes from the Forecasts table any existing forecasts that are within the specified date range, which is determined by the fiscal date pattern. The first and last records in the file establish the date range, and all records are deleted within that range. Use this batch program to import purchase order messages from VCP into the MPS/MRP/DRP Message File table (F3411). The system then processes the purchase order messages and updates the Purchase Order Detail File table (F4311). Use a processing option to specify the default purchase order type. Before it adds new messages, this program deletes from the MPS/MRP/DRP Message File table (F3411) any existing messages for the specified item, branch and order type.
3.
We have to create some tables in the work repository for staging some of the data used in some complex mappings. Without these tables being created it is difficult for us to map directly from the Model of the xml file or the flat file. The list of work repository tables created and where they are used is given in the below table. S.No Table Name 1 WR_DVM 2 WR_PARAMETER Used In Which Entities DVM Parameter Used In the Interface DVMInterface ParameterInterface CustomerDemandClassInterface BaseOperatingUnitInterface BaseLegalEntityInterface Trading Partners 3 WR_CUSTOMER_BRANCH_GROUP TradingPartner Sites Forecast demands BaseBusinessUnitInterface CustomerOperatingUnitInterface CustomerDemandClassInterface CustTRDPCustCodeParent1 CustTRDPCustCodeParent2 4 WR_CUST_TRDP_CUSTCODEPARENT 5 WR_CALENDAR_TRDPAT_CALCODE Trading Partners Trading Partners Units of measure Conversion , Units of measure class conversion 7 WR_BASE_UOM_NONPLANUOM Units of measure Conversion , Units of measure class conversion 8 WR_BASE_UOM_PLANUOM TradingPartnerCustomerInterface CalendarCodeInterface BaseUOMNonPlanUomListInterface
9 WR_BASE_UOM_TOUOMLIST
BaseUOMToUomListInterface
10 WR_BASE_UOM_UOMCOLUMNS
Units of measure,Units BaseUOMNonPlanUomListInterface of measure Conversion , Units of measure class conversion BaseUomListInterface Units of measure Conversion , Units of measure class conversion UOMConversionInterface UOMClassConversionInterface BaseUOMConversionInterface BaseUomListInterface UnitsOfMeasureInterface
11 WR_BASE_UOM_UOMCONVERSION
12 WR_BASE_UOM_UOMLIST
Units of measure,Units of measure Conversion Units of measure Conversion , Units of measure class conversion
17 WR_SUPPLIER_ITEM_PRIMARYSUPP
Items
18 WR_SUPPLIER_ITEM_STANDARDCOST
Items
Items 19 WR_TIMEVARYING 20 WR_COL 21 WR_MANUFACTURING_TIMEVAR Work Order Supplies Trading Partners Resources
SupplierTimeVaryingInterface SupplierStandardCostInterface TradingPartnerCustomerInterace ManufTimeVaryingCrewInterface ManufTimeVaryingMachineInterface ResourceShiftMachineInterface ManufTimeShiftVaryingToolInterface ResourceShiftToolInterface ResourceShiftsCrewInterface ResourceShiftsMachineInterface
Resource Shifts Routing Operation Operation Resources Price List shipping method
DemHistory.dat
SalesOrderHistory1Interface ListPriceInterface
List Price
OperatingUnitInterface PriceHistoryInterface
Price History Execution Status Work Order Supply Forecast demands Sales Orders Dvm Exception
4.
The staging tables Entity Name Calendar Table Name MSC_ST_CALENDARS Source File(s) Calendar.txt, Parameters.txt Calendar.txt, Parameters.txt, ShiftInformation.txt, Calendar.txt, Parameters.txt,ShiftInformation.txt, Calendar.txt, Parameters.txt Calendar Exceptions, ShiftInformation.txt, Customer.xml, Parameters.txt Customer.xml, Parameters.txt Base.xml, Parameters.txt Base.xml, Parameters.txt Base.xml, Parameters.txt Supplier.xml, Customer.xml, Base.xml, Parameters.txt Supplier.xml, Customer.xml, Base.xml, Parameters.txt Supplier.xml, Customer.xml, Base.xml, Parameters.txt Base.xml, Supplier.xml, Parameters.txt Base.xml, Parameters.txt Base.xml, Parameters.txt Base.xml, Parameters.txt BeginningInventory.xml Base.xml, Parameters.txt ResourceGroups.txt, ResourceGroupDetails.txt, Manufacturing.xml, ResourceGroupDetails.txt, Manufacturing.xml, Parameters.txt Manufacturing.xml. Base.xml, Parameter s.txt Manufacturing.xml, Parameters.txt Manufacturing.xml, Parameters.txt Manufacturing.xml, Base.xml, Parameters.txt Manufacturing.xml, Base.xml, Parameters.txt Distribution.xml,Parameters.txt Supplier.xml, Base.xml,Parameters.txt Supplier.xml, Distribution.xml, Customer.xml,
Business Object Calendars Calendars Calendars Calendars Calendars Analysis Analysis Analysis Unit of Unit of Unit of Trading Trading Trading Item Item Item Item Item Item Resources Resources Resources Routing Routing Routing BOM BOM Distr.& Distr.& Distr.&
Workday Patterns MSC_ST_WORKDAY_PATTERNS Shift Times Calendar Shift Exceptions Demand Classes Sales Channel Planners Unit of Measures UOM UOM Class Trading Partners Trading Partner Location Items Category Sets Item Categories Safety Stocks Price List Resources Resource Shifts Routing Routing Operation BOM Headers BOM Item Suppliers Item Sourcing MSC_ST_SHIFT_TIMES MSC_ST_CALENDAR_EXCEPTIONS MSC_ST_SHIFT_EXCEPTIONS MSC_ST_DEMAND_CLASSES MSC_ST_SR_LOOKUPS MSC_ST_PLANNERS MSC_ST_UNITS_OF_MEASURE MSC_ST_UOM_CONVERSIONS MSC_ST_TRADING_PARTNERS MSC_ST_TRADING_PARTNER_SITES MSC_ST_LOCATION_ASSOCIATIONS MSC_ST_SYSTEM_ITEMS MSC_ST_CATEGORY_SETS MSC_ST_ITEM_CATEGORIES MSC_ST_SAFETY_STOCKS MSC_ST_PRICE_LIST MSC_ST_DEPARTMENT_RESOURCES MSC_ST_RESOURCE_SHIFTS MSC_ST_ROUTINGS MSC_ST_ROUTING_OPERATIONS MSC_ST_OPERATION_RESOURCES MSC_ST_BOMS MSC_ST_BOM_COMPONENTS MSC_ST_ITEM_SUPPLIERS MSC_ST_ITEM_SOURCING
5.
6. Variables Following is the list of variables set within ODI to support E1-VCP integration. Variables are set when E1-VCP Integration Pack is installed. Users can change the values of variables, if needed, after installation of the pack. Variable Name PVV_APS_HOST_NAME PVV_APS_HOST_PWD PVV_APS_HOST_USER PVV_APS_INPUT_DIR PVV_APS_OUTPUT_DIR PVV_APS_TARGET_DIR PVV_DEM_HOST_NAME The ftp password of the ASCP server The ftp user of the ASCP server The path of the input directory for ASCP The path of the output directory for ASCP The path of the ASCP directory where we have to FTP the files from PVV_APS_INPUT_DIR The Host name of the Demantra server where we want to move the DemHistory.dat file. The ftp password of the Demantra server The ftp user of the Demantra server The path of the input directory for Demantra The path of the output directory for Demantra The path of the Demantra directory where we have to FTP the files to PVV_DEM_OUTPUT_DIR The path of the Demantra directory where we have to FTP the files from PVV_DEM_INPUT_DIR The path of the input directory for JDE E1 The path of the output directory for JDE E1 The path of the log directory will be refreshed every time the collection is run. Variable to hold CC mail addresses to whom the log file needs to be sent. Variable to hold Sender mail addresses from whom the log file needs will be sent. Host name of the mail server Variable to hold TO mail addresses to whom the log file needs to be sent. The variable that holds the Base date being passed from The UI. Variable to hold the begin time of the step in any Scenario. Every time the collection is run this variable holds the unique refresh id so as to append to the log file. The Instance id of the E1 instance The Instance code of the E1 instance The Plan Id for a particular plan The variable to hold the value for post process The variable to hold the value for pre process Always 1 Flag for enabling FTP for VCP Flag for enabling FTP for Demantra Description The Host name of the ASCP server where we want to move the DemHistory.dat file.
PVV_E1_INPUT_DIR PVV_E1_OUTPUT_DIR PVV_LOG_FILE_PATH PVV_MAIL_CC PVV_MAIL_SENDER PVV_MAIL_SERVER PVV_MAIL_TO PVD_BASE_DATE PVD_BEGIN_TIME PVN_LOG_REFRESH_ID