Reducing manual steps in the cost roll/cost copy utilizing XML and RUNUBEXML Prepared by Name: John Howe Title: Senior Business Systems Analyst Company: Dober Dober searched for an easier way to update the cost of many finished good items when the cost changed on a common raw material. The old process was to export a multi-level BOM, then manually enter each item into cost roll R30812 data selection, followed by another manual entry to cost copy R Dober modified the where used application to get top level items only. Next, we used RUNUBEXML to generate a standard XML template. The XML template is populated with top level items in the data selection, which is then called via the command line via ERW. Session ID#: JDE #JDEINFOCUS

Who is Dober? ■Dober is family owned chemical manufacture producing the cleaning, water treatment and corrosion & scale inhibitors ■We service the following industries ▪Pharmaceutical ▪Engine Coolant Additives ▪Oil & Gas Industries ■Spindle (division of Dober) produces operations management software to track productivity and reduce utility costs for industrial laundries ■Went live with XE in Upgraded to 9.0 in 2011

Business Problem ■Cost roll process was vary manual and time consuming ■Projected/forecasted costs were being calculated in Excel with data copied out of JDE ■Many raw materials are very sensitive to market conditions causing price fluctuations ■Some customers allow price increases or force decreases based on market indices ■Dober has been using a yearly cost roll methodology with a fixed standard for the year

Proposed Solutions ■Build Access database to handle cost modeling ■Move from yearly complete cost roll to quarterly ■Evaluate actual costing in JDE ■Review current method to find efficiencies ▪Review method was selected!

Old method – Step 1 Run P30201 Where used for raw material

Old method – Step 2 Change view to multi-level

Old method – Step 3 Export to Excel

Old method – Step 4 Filter top level items only

Old method – Step 5 Run R30812 simulated cost using copy/paste for each item into data selection

Old method – Step 6 ■Repeat copy/paste from previous step for R30835 frozen cost ■Repeat copy/paste from previous step for R30835 frozen update (08) ■Finished Now on to finding a better way!

Limitations of current R30812/R They do not support report interconnects 2.RUNUBE supports text inputs but does not allow data selection changes 3.Considered possibility of calling R30812 once for each item but approach would have been resource intensive 4.RUNUBEXML supports XML (text) input with data selection changes

The quest to use RUNUBEXML (Could the solution be this easy?) ■Reference: Overview of Using RUNUBEXML Command (Doc ID ) ■Build test XML file to understand how it works ■Add data selection lines to XML and verify it works ■Could XML be generated from FDA/ERW? ■Can FDA/ERW call command on logic server?

RUNUBEXML - Steps to build and test ■Built version of R30812 with similar data selection ▪R30812|DOB020XML ■File path: D:\JDEdwards\E900\DDP\system\bin32\RUNUBEXML.EXE ■Generate base XML file – run: ▪RUNUBEXML G CREATE_XML “D:\Temp\R30812_DOB020XML_Base.xml“ ■Edit base XML file

RUNUBEXML - Generate base XML file ■Generate base XML file – run: ■RUNUBEXML G CREATE_XML “D:\Temp\R30812_DOB020XML_Base.xml“

RUNUBEXML – Edit base XML file ■Edit base XML file: “D:\Temp\R30812_DOB020XML_Base.xml“ ▪Edit the following tags: ▪user='MYUSERID' ▪pwd='MYPASSWD' ▪environment='MYENV' ▪role='MYROLE' ▪REPORT_NAME VALUE='R30835' ▪REPORT_VERSION VALUE='DOB02XML‘

RUNUBEXML - Build Batch Request XML ■Generate base XML file – run: ■RUNUBEXML S “D:\Temp\R30821_DOB020XML_Base.xml" “D:\Temp\R30821_DOB020XML_Request.xml“ ■Edit “R30821|DOB020XML_Request.xml” and add data selection lines ■Submit job on logic server – run: ■RUNUBEXML S “D:\Temp\R30821_DOB020XML_Request.xml" “D:\Temp\R30821_DOB020XML_Result.xml“ ■Verify data selection worked via work submitted jobs ■RUNUBEXML with modified XML works!

RUNUBEXML – Now How Do We Incorporate? Populate F55XML with static XML lines (SQL import) Populate F55XML with static XML lines (SQL import) Output F55XML file to xml file on logic server (R30812_User_DateTime.xml) Output F55XML file to xml file on logic server (R30812_User_DateTime.xml) Call RUNUBEXML (R30812_User_DateTime.xml) Delete XML (R30812_User_DateTime.xml) Populate non static F55XML (ERW data selection, user info)

Create F55XML Table

Edit Request.xml for SQL import 1.Edit “D:\Temp\R30821_DOB020XML_Request.xml” ▪Remove carriage return line feed “CRLF” (ASCII 13)(ASCII 10) from processing option descriptions ▪Format XML — Notepad++... XML Tools... Pretty Print (XML only - with line breaks) ▪Delete comment lines (3 & 30 in example) ▪Clear out lines that will be populated later with FDA/ERW — Line 2 leaving line blank — Line 14 - Line used for branch plant data selection — Line 22,23 leaving blank line ▪Remove indents “TABS” (ASCII 09)

Paste edited XML to Excel for SQL import

Copy SQL statements from “SQL Import” column to query tool

New ERW Code added to P ■Added password field ▪Top Level ■Call cost roll UBE ▪Populate F55XML ▪Generate XML file ▪Call cost application ▪Delete XML

Please complete the session evaluation We appreciate your feedback and insight Session ID# JDE