e1 vcp integration part 1

© 2009 Oracle Corporation – Proprietary and Confidential 2

Day, Date, 2004 time p.m. ET

Teleconference Access: North America: xxxx International: xxxx Password: Advisor

Wednesday, Oct. 12, 2011 11:00 AM ET / 09:00 MT Teleconference Access: Conference ID: 18552252 or Oracle VCP North America: (866) 627-3315 International: +1-706-679-7972 Other Global Toll Free: Doc ID: 1148600.1

Upcoming Value Chain Planning Community Webcasts:

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

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 [email protected], subject: Topics of Interest.

Value Chain Planning Advisor Webcast

<Insert Picture Here>

The E1 - VCP Integration (Part 1 of 2) Gerry Dewil, Principal Technical Support Engineer Srikanta Nanjundaswamy, Senior Software Engineer


The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decision. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.

Safe Harbor Statement

<Insert Picture Here>

The E1 - VCP Integration (Part 1 of 2) Gerry Dewil, Principal Technical Support Engineer Srikanta Nanjundaswamy, Senior Software Engineer


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


Part 1 of a Two-Session Integration Overview

• The notes of this presentation contain significant details on the integration. Once released, please open the PowerPoint and review the notes for details.

• Also check shared_directories.doc • This is part 1 of a Two-session introduction to the integration. Please provide

feedback after this presentation so that we can tailor Part 2 to your needs Examples:

• Demantra • Installation details • Configuring Weblogic and ODI • Troubleshooting • …

• Send to [email protected] or [email protected]


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


Overview of Data Collections

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

This next couple of slides are intended to give E1 functional and technical users a very high level overview of the collections and planning architecture in VCP.

For VCP functional and technical implementers that need a primer to JDE, please refer to section #4 – JDE Primer to VCP at the E1-VCP Product Information Center – note 1311054.1

https://support.us.oracle.com/oip/faces/secure/km/DownloadAttachment.jspx?attachid=1311054.1:04_JDE_VCP_PRIMER�

https://support.us.oracle.com/oip/faces/secure/km/DownloadAttachment.jspx?attachid=1311054.1:04_JDE_VCP_PRIMER�


ASCP Plan processes

1. Memory Based Snapshot - prepares the list of planned items, performs pre-processing and post-processing tasks

2. Snapshot Monitor - controls the rest of the planning process. Launches the snapshot workers, Delete Workers, Loader Workers, and MBP

3. Snapshot Workers – snapshots WIP, on-hand, PO, Firm Planned Orders, etc . Controlled by MRP:Snapshot Workers

4. Snapshot Delete Workers - deletes the planning data from the last run and checks msc_snapshot_tasks

5. Loader Workers with Direct Load Option loads the tables 6. Memory Based Planner – performs the gross-to-net explosion

and loads the snapshot flat files into memory, then writes the output to flat files.


ASCP Plan processes

7. Analyze Plan Partition – gathers the optimizer statistics and improves SQL performance

8. ASCP Post Plan Program for UI – optimizes the planning tables for faster access in UI

9. ATP Post Plan Processing – prepares availability picture for GOP

10. Refresh One KPI Summary Table – Calculates Key Performance Indicators

11. APCC Post Plan processing – new in R12.1 and 11i RUP #37 12. Auto Release Planned orders – automatically releases planned

orders

© 2009 Oracle Corporation – Proprietary and Confidential 12 12

Integration Components For A Typical System Configuration

Shared Directory/ Mount Point,

or FTP

JD Edwards EnterpriseOne Value Chain Planning Linux 32-bit, 64-bit

Windows 32-bit HP UX 64-bit

AIX 64-bit SUN Solaris 64-bit

AIA PIP Linux 32-bit

Windows 32-bit

Client: Desktop apps SNO and PS

Client: Web Browser

Demantra, IO, ASCP, APCC

AIA


JD Edwards EnterpriseOne ERP Systems

Oracle Value Chain Planning

Planning order recommendations

Promotions and settlement payments

Master Data and Transaction Data

AIA

VCP to JDE E1 ERP Integration Overview


Architecture Overview


Planning


Demand Management


Demand Management (cont’d)


• 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

Demand Management Integration – Process Flow


Predictive Trade Planning


Deductions and Settlement Mgmt


Setup and Configure Integration Directories

JD Edwards EnterpriseOne

E1 Output Directory

E1 Input Directory

Oracle Data Integrator

APS Input Directory

Demantra Input Directory

Demantra Output Directory

Demantra Apps Server

Oracle Value Chain Planning

See shared_directories.doc


VCP-E1 Integration Directories ODI uses six directories for the VCP:E1 Integration • E1 Output Directory

• Contains the extract files from JDE E1 • E1 Input Directory

• Contains the files from VCP/Demantra prior to being loaded into JDE E1 • APS Output Directory

• This directory is currently not used • APS Input Directory

• Contains the transformed Sales Order History file (DemHistory.dat) ready for loading into VCP

• Demantra Output Directory • The Demantra publish files. Files in this directory need to be processed by ODI

prior to loading into JDE E1. • Demantra Input Directory

• Contains the files to be loaded into Demantra. Files in this directory are generated by ODI from E1 files


Required Components

• 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* *requires EBS installation with rapidwiz

VCP 12.1.3.4 Demantra

7.3.1.1

E1 9.0

WLS 10.3 ODI 11g AIA 3.1

Wolfram

Ptolemy

See note 1363791.1 and PIC “08 E1 VCP Integration Installation Training”

https://support.us.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1363791.1�



Minimum Requirements & Patching

• Oracle Data Integrator 10.1.3.4 or higher on rdbms 10g Recommended is 11.1.1.3 or higher on 11g (built on Oracle Fusion Middleware 11.1.1.4.0) • Oracle Value Chain Planning Suite Release 12.1.1 • Oracle Demantra 7.2.0.2 • JDE EnterpriseOne 9.0 + ESU for SAR number 8925532

• As of today (10/12/11)

• Latest VCP = 12.1.3.4 • Latest Demantra = 7.3.1.1 • AIA 3.1 no patches (AIA 3.2 expected in Feb ’12) • For AIA 2.5 we have 2 CU patches

E1VCP PIP PATCH 1 - patch 9217989 E1VCP PIP PATCH 2 – patch 12610866


List of E1 UBEs for VCP-E1 Integration

If you are using only Demantra products, then only Base.xml, Customer.xml and Calendar.txt are needed from this list


List of E1 UBEs for VCP-E1 Integration

DM

PTP

DSM

The above are the E1 UBEs for specific Demantra applications


User Defined Files

• TranslationTable.txt • Parameters.txt • ShiftInformation.txt & ShiftInformationDetails.txt • ResourceGroups.txt & ResourceGroupDetails.txt • SetupDefinitions.txt & SetupTransitions.txt • StandardOperationResources.txt • StandardUOMConversions.txt 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.


Work Repository Tables


Staging Tables


An Example

UBE writes to xml files

Work repositories ODI scenarios

VCP staging tables VCP base tables Demantra staging tables Demantra base tables

And back …


An Example


Data Flow Example

Product Strategist is about to release a TOI in the next couple of weeks on E1 setup


Example of UBE R34705 and R34A715


The corresponding XML file


Collections


Check the ODI server


Check Collections Logs


Check collected data


Run ASCP


Implementation Tip

• Skill sets required: • VCP Application Consultant / Apps DBA to install EBS (VCP) and apply

patches. • Middleware Consultant • JDE Skills in UBE’s & 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.


Restrictions

• This integration focuses on discrete manufacturing. • For process manufacturing, certain features such as Co-Products, Bi-

Products 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

https://support.us.oracle.com/oip/faces/secure/km/DownloadAttachment.jspx?attachid=1311054.1:07_JDE_VCP_EBS_DIFF�


Value Chain Planning – Product Releases 11i.10 12.0 12.1

7.1 7.2 7.3

Demantra

VCP 12.2

FUSION

1.0 2.0

EDGE


Roadmap


Product Information Center - 1311054.1

• Transfer of Information Power Points • Implementation Guides • Installation Guides • Release Notes • White Papers • Start to End Installation Document • Data Mapping Spreadsheet



References

• Product matrix – Note 1081971.1 • ASCP PIC – Note 1349838.1 • Demantra PIC – Note 1157065.1 • ASCP Profile Plan Option Matrix – Note 803583.1






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


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


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.


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.

.


Troubleshooting


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

• Performance issue with requests • Checked for the stats on the tables and analyzing the tables by running gather

schema stats. • Also can check the load balancing of requests

• Requests failing with error • Correct request’s time out settings and incompatibility between different concurrent

requests of planning to ensure that the requests do not fail with time out errors


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

• Issues in ODI running • Check for wild characters in xml files which can cause the ODI synchronization

to fail.

• Purging data • Purge old data from VCP which can cause error in pre process monitor

• File permissions • ODI may error with unable to read file from JDEOutbound directory and file

permissions for the files in JDEOutbound needs to be corrected

.


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


• 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


Collaborate with a large network of your industry peers, support professionals, and Oracle experts to exchange information, ask questions & get answers. Find out how your peers are using Oracle technologies and services to better meet their support and business needs.

• Exchange Knowledge

• Resolve Issues

• Gain Expertise

Visit My Oracle Communities

Visit the My Oracle Support Community now!! 1. Log into My Oracle Support.

2. Select the Community tab.

3. Select the Enter Here button.

4. Select the Community Name link under the E-Business Suite section of the My Communities Menu on the left side of the window.

https://metalink.oracle.com/�


Advisor Webcast Calendar and Archive Doc ID 837233.1)


• Would you like to receive email invites for future Advisor Webcasts?

• Answer “Yes” to receive information the next time you register for a live webcast or webcast recording.

• You can unsubscribe at any time by replying to the invite with “unsubscribe” in the subject line.

Receive Email Webcast Invites


• Your feedback is a valuable part of ensuring the Advisor Webcast program continues to meet your needs.

• Assist Oracle with the consistent delivery of quality webcasts, and to help identify opportunities for improvement.

• Please take a moment to complete the Advisor Webcast Assessment , which will be emailed to you in the next week.

• Your feedback is greatly appreciated.

• You may also contact me directly at [email protected].

Advisor Webcast Assessment

mailto:[email protected]�


THANK YOU

This document lists

1. The shared directories and their contents 2. The data retrieved by R34A705: 3. The work repository tables used in the integration 4. The staging tables used in the integration 5. The variables used in the integration

1. The Shared Directories and their contents:

a. JDE OUTBOUND

File Name Target Application Source Parameters.txt APS staging tables User-defined TranslationTable.txt APS staging tables User-defined ShiftInformation.txt APS staging tables User-defined ShiftInformationDetails.txt APS staging tables User-defined ResourceGroups.txt APS staging tables User-defined ResourceGroupDetails.txt APS staging tables User-defined ForecastDesignators.txt APS staging tables User-defined SetupDefinitions.txt APS staging tables User-defined SetupTransitions.txt APS staging tables User-defined StandardOperationResources.txt APS staging tables User-defined StandardUOMConversions.txt APS staging tables User-defined Calendar.txt APS staging tables ERP extract Supplier.xml APS staging tables ERP extract Customer.xml APS staging tables ERP extract Base.xml APS staging tables ERP extract Manufacturing.xml APS staging tables ERP extract BeginningInventory.xml APS staging tables ERP extract Distribution.xml APS staging tables ERP extract PurchaseOrders.xml APS staging tables ERP extract WorkOrders.xml APS staging tables ERP extract SalesOrders.xml APS staging tables ERP extract TransferOrders.xml APS staging tables ERP extract TimeSeries.xml APS staging tables ERP extract SalesOrderHistory.txt Demantra ERP extract ListPrice.txt Demantra ERP extract ItemCost.txt Demantra ERP extract PriceHistory.txt Demantra ERP extract APConfirm.txt Demantra ERP extract Deductions.txt Demantra ERP extract

b. JDE INBOUND

PurchasePlan.xml JDE E1 APS extract DeploymentPlan.xml JDE E1 APS extract DetailedProductionPlan.xml JDE E1 APS extract forecast.txt JDE E1/PeopleSoft Demantra (transformed file) PromotionPricing.txt JDE E1 Demantra (transformed file) Delete_PromoPricing.txt JDE E1 A copied file of a Demantra extract DeductionDispositions.txt JDE E1 A copied file of a Demantra extract Claim.txt JDE E1 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

ERP transformed file

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 Demantra JDE E1 transformed file PriceHistory.txt Demantra JDE E1 transformed file ItemCost.txt Demantra JDE E1 transformed file APConfirm.txt Demantra A copied file of an JDE E1 extract Deductions.txt Demantra 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 ERP Demantra transformed file PromotionPricing.txt JDE E1 Demantra transformed file Delete_PromoPricing.txt JDE E1 A copied file of a Demantra extract DeductionDispositions.txt JDE E1 A copied file of a Demantra extract claim.txt JDE E1 A copied file of a Demantra extract

2. The following table lists the data retrieved by R34A705:

Outbound Transfer Batch Data Retrieved

VCP Base Package (R34A715) 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)

VCP Beginning Inventory Package (R34A740) Use this batch program to retrieve information from: • Item Location File (F41021) • Lot Master (F4108)

VCP Customer Package (R34A775) • Address BookMaster (F0101) • Address by Date (F0116) • Item Base Price File (F4106) • Item Cross Reference File (F4104) • Preference Profile - Inventory Sourcing (F40306)

VCP Distribution Package (R34A780/R34A785)

• Branch Relationships Master File (F3403) • Routing Entries (F4950) • User Defined Codes (F0005) • Routing Restrictions (F4952) • R34A785

VCP Manufacturing Package (R34A925) • Routing Master File (F3003) • Bill of Material Master File (F3002) • F34A110 • F34A120 • F34A190 (resource set info) • F30008/F30006 (tool, machine, crew calendar information)

VCP Purchase Order Package (R34A750) • Purchase Order Detail File table (F4311).

VCP Sales Order Package (R34A730) • 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.

VCP Supplier Package (R34A810) • WO Supplemental Data Types (F48090) • Address Book Master (F0101) • Address By Date (F0116) • Item Branch (F4102)

TimeSeries Package • R34A930 • R34A940

VCP Transfer Order Package (R34A760) • Purchase Order Detail File (F4311) • Sales Order Header File (F4201) • LotMaster (F4108)

Work Order Package (R34A915) • 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)

OBDWCAL R34A610 The JD Edwards EnterpriseOne calendar information flat file.

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.

VCP Inbound Forecasts Package (R34A860) 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.

VCP Inbound Purchase Order Messages (R34A870) 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. The Work Repository Tables

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 Used In Which Entities Used In the Interface

1 WR_DVM DVM DVMInterface 2 WR_PARAMETER Parameter ParameterInterface

3

WR_CUSTOMER_BRANCH_GROUP

Trading Partners

CustomerDemandClassInterface BaseOperatingUnitInterface BaseLegalEntityInterface BaseBusinessUnitInterface

TradingPartner Sites CustomerOperatingUnitInterface Forecast demands CustomerDemandClassInterface

4

WR_CUST_TRDP_CUSTCODEPARENT

Trading Partners

CustTRDPCustCodeParent1

CustTRDPCustCodeParent2

TradingPartnerCustomerInterface 5 WR_CALENDAR_TRDPAT_CALCODE Trading Partners CalendarCodeInterface

7

WR_BASE_UOM_NONPLANUOM

Units of measure Conversion , Units of measure class conversion

BaseUOMNonPlanUomListInterface BaseUOMConversionInterface

8

WR_BASE_UOM_PLANUOM


BaseUOMPlanUom1Interface

BaseUOMPlanUomInterface BaseUOMConversionInterface

9

WR_BASE_UOM_TOUOMLIST

Units of measure

UnitsOfMeasureInterface

BaseUOMToUomListInterface

10

WR_BASE_UOM_UOMCOLUMNS

Units of measure,Units of measure Conversion , Units of measure class conversion

BaseUOMNonPlanUomListInterface BaseUomListInterface

11

WR_BASE_UOM_UOMCONVERSION


UOMConversionInterface

UOMClassConversionInterface BaseUOMConversionInterface

12

WR_BASE_UOM_UOMLIST

Units of measure,Units of measure Conversion

BaseUomListInterface

UnitsOfMeasureInterface

BaseUOMListUpdate

StandardUOMConvInterface

13

WR_BASE_UOM_UOMTYPE


BaseUOMUomType1Interface

BaseUOMUomTypeInterface

BaseUOMNonPlanUomListInterface

BaseUOMUomTypeInterface 14 WR_BASE_ITEM_ITEMGROUP Items BaseItemGroupInterface 15 WR_BASE_ITEM_ITEMUOM Items BaseItemUomInterface

16

WR_BASE_ITEM_MASTERPLANFAMILY

Items

MasterPlanFamilyInterface

ItemMasterPlanningFamilyInterface

SupplierPrimarySupplierInterface

17 WR_SUPPLIER_ITEM_PRIMARYSUPP Items SupplierPrimarySupplierInterface2

18

WR_SUPPLIER_ITEM_STANDARDCOST

Items

SupplierStandardCostInterface

SupplierPrimarySupplierInterface

SupplierPrimarySupplierInterface2

19

WR_TIMEVARYING

Items

Item Interface

BaseTimeVaryingInterface

WorkOrderSuppliesInterface

SupplierTimeVaryingInterface

Work Order Supplies SupplierStandardCostInterface

20 WR_COL Trading Partners TradingPartnerCustomerInterace 21 WR_MANUFACTURING_TIMEVAR Resources ManufTimeVaryingCrewInterface

ManufTimeVaryingMachineInterface

ResourceShiftMachineInterface

ManufTimeShiftVaryingToolInterface

ResourceShiftToolInterface

22

WR_RESOURCE_SHIFTS

Resource Shifts

ResourceShiftsCrewInterface ResourceShiftsMachineInterface ResourceShiftsToolInterface

23

WR_MANU_TIMEVARYING

Routing Operation RoutingOperationInterface Operation Resources RoutingOpResourcesInterface

24 WR_CUST_PRICELIST_AVGPRICE Price List PriceListInterface

25

WR_DIST_SHIPPINGMETHOD_TVE

shipping method

ShippingMethodDistTVEInterface

DistShipMethodTVECostInterface

26

WR_SALES_ORDER_HISTORY

DemHistory.dat

DemandClassInterface

OperatingUnitInterface

SalesChannelInterface

SalesOrderHistory1Interface

List Price

ListPriceInterface

OperatingUnitInterface

Price History

PriceHistoryInterface OperatingUnitInterface

27 WR_EXECUTION_STATUS Execution Status ExecutionStatusFileInterface

28

WR_WORKORDER_SUPPLY_OPCODE

Work Order Supply

WorkOrderSupplyOpCodeInterface

WorkOrderSuppliesInterface 29 WR_CALENDAR_DAY_EVENT Forecast demands ForecastDemandsInterface 30 WR_SALES_ORDER_TO_CUSTOMER Sales Orders SalesOrderTOInterface 31 WR_DVM_EXCEPTION Dvm Exception

32

WR_BASE_ITEM_ITEMCOST

Item

BaseTimeVaryingItemCostInterface

BaseItemCostInterface

ItemInterface

4. The staging tables

Business Object

Entity Name Table Name Source File(s)

Calendars Calendar MSC_ST_CALENDARS Calendar.txt, Parameters.txt

Calendars Workday Patterns MSC_ST_WORKDAY_PATTERNS Calendar.txt, Parameters.txt, ShiftInformation.txt, Calendars Shift Times MSC_ST_SHIFT_TIMES Calendar.txt, Parameters.txt,ShiftInformation.txt, Calendars Calendar

MSC_ST_CALENDAR_EXCEPTIONS Calendar.txt, Parameters.txt

Calendars Shift Exceptions MSC_ST_SHIFT_EXCEPTIONS Calendar Exceptions, ShiftInformation.txt, Analysis

Demand Classes MSC_ST_DEMAND_CLASSES Customer.xml, Parameters.txt

Analysis

Sales Channel MSC_ST_SR_LOOKUPS Customer.xml, Parameters.txt Analysis

Planners MSC_ST_PLANNERS Base.xml, Parameters.txt

Unit of

Unit of Measures MSC_ST_UNITS_OF_MEASURE Base.xml, Parameters.txt

Unit of

UOM

MSC_ST_UOM_CONVERSIONS Base.xml, Parameters.txt

Unit of

UOM Class

MSC_ST_UOM_CLASS_CONVERSIONS Base.xml, Parameters.txt Trading

Trading Partners MSC_ST_TRADING_PARTNERS Supplier.xml, Customer.xml, Base.xml, Parameters.txt

Trading

Trading Partner

MSC_ST_TRADING_PARTNER_SITES Supplier.xml, Customer.xml, Base.xml, Parameters.txt Trading

Location

MSC_ST_LOCATION_ASSOCIATIONS Supplier.xml, Customer.xml, Base.xml, Parameters.txt

Item Items MSC_ST_SYSTEM_ITEMS Base.xml, Supplier.xml, Parameters.txt Item Category Sets MSC_ST_CATEGORY_SETS Base.xml, Parameters.txt Item Item Categories MSC_ST_ITEM_CATEGORIES Base.xml, Parameters.txt Item Safety Stocks MSC_ST_SAFETY_STOCKS Base.xml, Parameters.txt

Item On hand Supplies MSC_ST_SUPPLIES BeginningInventory.xml

Item Price List MSC_ST_PRICE_LIST Base.xml, Parameters.txt

Resources Resource Groups MSC_ST_RESOURCE_GROUPS ResourceGroups.txt, ResourceGroupDetails.txt, Resources Resources MSC_ST_DEPARTMENT_RESOURCES Manufacturing.xml, ResourceGroupDetails.txt, Resources Resource Shifts MSC_ST_RESOURCE_SHIFTS Manufacturing.xml, Parameters.txt

Routing Routing MSC_ST_ROUTINGS Manufacturing.xml. Base.xml, Parameter s.txt Routing Routing

MSC_ST_ROUTING_OPERATIONS Manufacturing.xml, Parameters.txt

Routing Operation

MSC_ST_OPERATION_RESOURCES Manufacturing.xml, Parameters.txt

BOM BOM Headers MSC_ST_BOMS Manufacturing.xml, Base.xml, Parameters.txt

BOM BOM

MSC_ST_BOM_COMPONENTS Manufacturing.xml, Base.xml, Parameters.txt

Distr.&

Shipping Methods MSC_ST_INTERORG_SHIP_METHODS Distribution.xml,Parameters.txt Distr.&

Item Suppliers MSC_ST_ITEM_SUPPLIERS Supplier.xml, Base.xml,Parameters.txt

Distr.&

Item Sourcing MSC_ST_ITEM_SOURCING Supplier.xml, Distribution.xml, Customer.xml,

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 Description PVV_APS_HOST_NAME The Host name of the ASCP server where we want to move the DemHistory.dat file.

PVV_APS_HOST_PWD The ftp password of the ASCP server

PVV_APS_HOST_USER The ftp user of the ASCP server

PVV_APS_INPUT_DIR The path of the input directory for ASCP

PVV_APS_OUTPUT_DIR The path of the output directory for ASCP

PVV_APS_TARGET_DIR The path of the ASCP directory where we have to FTP the files from PVV_APS_INPUT_DIR

PVV_DEM_HOST_NAME The Host name of the Demantra server where we want to move the DemHistory.dat file.

PVV_DEM_HOST_PWD The ftp password of the Demantra server

PVV_DEM_HOST_USER The ftp user of the Demantra server

PVV_DEM_INPUT_DIR The path of the input directory for Demantra

PVV_DEM_OUTPUT_DIR The path of the output directory for Demantra

PVV_DEM_SOURCE_DIR The path of the Demantra directory where we have to FTP the files to PVV_DEM_OUTPUT_DIR

PVV_DEM_TARGET_DIR The path of the Demantra directory where we have to FTP the files from PVV_DEM_INPUT_DIR

PVV_E1_INPUT_DIR The path of the input directory for JDE E1

PVV_E1_OUTPUT_DIR The path of the output directory for JDE E1

PVV_LOG_FILE_PATH The path of the log directory will be refreshed every time the collection is run. PVV_MAIL_CC Variable to hold CC mail addresses to whom the log file needs to be sent. PVV_MAIL_SENDER Variable to hold Sender mail addresses from whom the log file needs will be sent.

PVV_MAIL_SERVER Host name of the mail server

PVV_MAIL_TO Variable to hold TO mail addresses to whom the log file needs to be sent. PVD_BASE_DATE The variable that holds the Base date being passed from The UI. PVD_BEGIN_TIME Variable to hold the begin time of the step in any Scenario. PVN_LOG_REFRESH_ID Every time the collection is run this variable holds the unique refresh id so as to

append to the log file.

PVN_SR_INSTANCE_ID The Instance id of the E1 instance

PVV_INSTANCE_CODE The Instance code of the E1 instance

PVV_PLAN_ID The Plan Id for a particular plan

PVV_PRE_PROCESS_VAR The variable to hold the value for post process

PVV_POST_PROCESS_VAR The variable to hold the value for pre process

PVN_PROCESS_FLAG Always 1

PVV_APS_FTP_FLAG Flag for enabling FTP for VCP

PVV_DEM_FTP_FLAG Flag for enabling FTP for Demantra

e1 vcp integration part 1

Documents