MappSci Corporation


Mission

Efficiently create and modify JD Edwards EnterpriseOne reports, interactive applications, and interoperability solutions that serve as valuable tools for key decision makers.

Unique Value Proposition

Maintainable and responsive JD Edwards Enterprise One solutions that are created in a systematic fashion and with a transparent method that reduces runaway cost.

Disclaimer: MappSci Corporation is not affiliated with, endorsed by, or authorized by Oracle or DSI. All product and company names are the registered trademarks of rightful owners. Trademark or tradename use is for reference purposes only and does not suggest any association with the trademark holder of its product brand.

Consulting


MappSci provides JD Edwards EnterpriseOne consulting services per its` mission definition. Its ability to efficiently exceed customers' expectations is an outgrowth of 20 years of experiences working with accounting, finance, order-entry, warehouse, shop floor, stock room, education, human resources, marketing, information technology, and compliance professionals.

MappSci produces proof-of-work artifacts that are emblematic of its "work hard and work smart" philosophy.

These artifacts are concise documents (i.e. requirements, technical, unit testing, user testing, and approval), multiple related business functions in single business function objects (i.e. source files), easy to maintain level break reports, transparent back end ubes (i.e. business functions instead of NER in invisible sections), interactive applications that follow MVC principles (i.e. business functions instead of NER in invisible buttons), and easy to maintain Java objects.

The concise nature of these artifacts is a result of MappSci's comprehension of standard business operations, proficiency in procedural software engineering, knowledge of information technology operations, dedication to "do not repeat yourself" principles, and belief in achievement with focused activity.


JD Edwards EnterpriseOne C Development Packages


The C language is omnipresent in JD Edwards EnterpriseOne. NER business functions ultimately end up being C source code. And business functions are in dlls that are utlized by interactive applications, ubes, and interoperability. JD Edwards developers who struggle with C greatly outnumber those who already have adequate experiences. On the opposite end of the spectrum are outstanding C programmers who do not have adequate experiences with JD Edwards' C APIs, data structures, and coding style.

The project delays that can be attributed to lack of "C on JD Edwards" resources vary. In some cases, it leads to reduction of scope and value to the end user. And in extreme cases, projects are scrapped due to the shortfall. Moreover, "NER only" implementations often produce code bloat, violate MVC, and bring about difficult to maintain applications and reports.

For occasions when knowing JD Edwards EnterpriseOne C functions and Visual Studio is necessary and when there is not enough time to overcome the learning curve (i.e. data structures, file io, dynamic memory, pointers, casting, text line parsing and formation, software engineering standards, and business process flow) or the cognitive effort (i.e. switching from NER editing and MDDebug to Visual Studio navigation and debugging), MappSci offers the following packages:

Producing an audit trail of data structure members' values that go in and out of business functions requires analysis of the JD Edwards EnterpriseOne log files.

Analysts tasked with the job know the difficulties involved with deciphering the entries in these log files. To speed up the process of finding the root cause, analysts can use business functions that output the data members' values to easier-to-read custom log files.

Easier-to-read files are time savers for testing, trouble shooting, and proof-of-concept projects (e.g. Business Service and Orchestration), . Specifically, diff (or windiff), grep (regex), and sed can be utilized for analysis.

Delivery of this package requires a MappSci consultant to complete the tasks on the following check list.

  1. Create a text file that contains business function documentation
  2. Attach technical document via OMW
  3. Create C business function object
  4. Create business function (calls 2 internal functions)
  5. Create internal function for "row display" - all members of data structure
  6. Create internal function for "column display" - all members of data structure
  7. Create jdeCallObject code that calls the business function
  8. Create test document
  9. Test "row display" internal function - fill test document
  10. Test "column display" internal function - fill test document
  11. Create user documentation

The average time of completion is 10 hours. The package's value is $1000

The keyboard and "recompile/edit" effort required to use jdeCallObject can be tedious, especially for functions with big data structures.

Delivery of this package requires a MappSci consultant to complete the tasks on the following check list.

  1. Analyze "input to data structure" file (provided by client)
  2. Analyze test data and test procedure (provided by client)
  3. Create a text file that contains business function modification documentation
  4. Attach modification documentation to OMW
  5. Create internal function that contains JDECallObject
  6. Modifiy the business function to call the internal function
  7. Create test document
  8. Test modification - fill test document
  9. Comment calls to internal function (optional)
  10. Create notes for in-house technical resource (optional)

The average time of completion is 10 hours. The package's value is $1000

Working with JDECache requires 3 days to a month. Using jdeCache functions is arguably the most difficult thing to do even for the most experienced technical consultant. jdeCache underpins almost all vanilla BeginDoc, EditDoc, and EndDoc business functions - i.e. the foundation of interactive applications that use header detail forms and of subsystem processing ubes). Delivery of this package requires a MappSci consultant to complete the tasks on the following check list.

  1. Analyze "cache structure to io data structure" file (provided by client)
  2. Create a text file that contains business function documentation
  3. Attach business function documentation
  4. Create business function object
  5. Create "cache io" business function
  6. Create "cachie io constants" business function
  7. Create "print contents of cache" business function
  8. Create internal function that contains low level cache IO code
  9. Create internal function that contains cache initilalization code
  10. Create test application for "cache io", "cache io constants", and "print contents of cache" business functions
  11. Create test document
  12. Test "cache io" business function - fill test document
  13. Create user documentation
  14. Attach user documentation to OMW

The average time of completion is 20 hours. The package's value is $2000

jdeLaunchUBE is a valuable tool, especially for interoperability projects. Delivery of this package requires a MappSci consultant to complete the tasks on the following check list.

  1. Analyze the business case (provided by client)
  2. Create a text file that contains business function documentation
  3. Attach business function documentation
  4. Create business function object
  5. Create "launch ube" business function that wrapse jdeLaunchUBE
  6. Create test application that calls the business function
  7. Create test document
  8. Test "launch ube" business function - fill test document

The average time of completion is 10 hours. The package's value is $1000

There are times when a table column is filled with a list delimited by a specific character (e.g. bank tape data). These columns can be processed (i.e. split or slice) via named event rules. But if the related logic is complex, the container of the named event rules will appear clutered and will be difficult to maintain. This type of requirement is better served by a C business function. Delivery of this package requires a MappSci consultant to complete the tasks on the following check list.

  1. Analyze the business case (provided by client)
  2. Create a text file that contains business function documentation
  3. Attach business function documentation
  4. Create internal function that parses a delimited line
  5. Create business function object
  6. Create business function
  7. Create test application that calls the business function
  8. Create test document
  9. Test business function - fill test document

The average time of completion is 10 hours. The package's value is $1000


Upgrade projects (i.e. from World to E1 and OW to E1) would greatly benefit from the packages described above. They serve as good models for RPG and NER programmers. Moreover, it should give them an idea how to minimally modify vanilla source code for future upgrade purposes.

MappSci consultants use these packages at engagements. These packages reduce project delays and show stoppers. Moreover, they increase throughput - e.g. root causes identified, business functions tested, and applications and reports promoted to production.

The clock starts from when a MappSci consultant initially accesses the fat client on the customer's network and ends with the completion of the last delivery item. Moreover, the work done for these packages are performed only in DEV. Delivery date, therefore, depends on the customer's completing the following tasks before the agreed upon work date:

  1. Create and test credentials so that a MappSci consultant can remotely log into the client's network
  2. Dedicate a fat client to a MappSci consultant
  3. Create E1 credentials for a MappSci consultant
  4. Restrict MappSci consultant's access to all E1 environments other than DEV
  5. Verify that Visual Studio is installed on the fat client
  6. Using credentials to be assigned to MappSci consultant, verify that a business function can be compiled on the fat client
  7. Using credentials to be assigned to MappSci consultant, verify that a test application can be created on the fat client
  8. Send access instructions, for network login and fat client login, to MappSci consultant after invoice payment.
  9. Prepare test data and steps


Documentation


MappSci can perform analysis and create the following documents for applications and solutions that need better documentation (i.e. read by developers and auditors):

  1. Flow Charts
  2. Wire Frames
  3. Test Documents
  4. Training Guides
  5. User Guides
  6. Procedure Guides
  7. Test/Sign-Off Documents
  8. Proof-of-Concept Documents
  9. Attachments (e.g. application, ube, and business function documentation via OMW)

JD Edwards EnterpriseOne Foundation


The foundation of MappSci's JD Edwards Enterprise One technical practice is rooted in its experiences with C functions (JDE foundation, JDECache, master business functions, and industry standard), event driven programming, MFC, MVC, Java (BSSV), Javascript, DRY practices, CRUD requirements, client-server systems, distributed computing, Apache, XML, JSON, FTP, HTTP, containers, Windows, Unix, and Oracle RDBMS.

These experiences are made up of many hours working on:

  1. Visual Studio
  2. JDEDebugger
  3. Object Librarian
  4. Object Management Workbench (OMW)
  5. Form Design Aid
  6. Report Design Aid
  7. Business Function (BSFN) Design Aid
  8. Table Design Aid
  9. Business View Design Aid
  10. Data Dictionary
  11. Oracle JDeveloper
  12. OC4J (BSSV)
  13. BI Publisher.
  14. Visio
  15. Google Sheets
  16. Excel
  17. Software Development Life Cycle (SDLC)
  18. vi
  19. bash
  20. regex
  21. curl
  22. exe
  23. bin
  24. lib
  25. dll
  26. DOM
  27. HTML
  28. CSS
  29. WebStorm
  30. AWS

Moreover, these experiences comprise:

  1. Design sessions
  2. Technical documentation
  3. Coding time
  4. Debugging time
  5. Testing time
  6. Configuration time
  7. Research time (undocumented features)
  8. Technical support sessions with Oracle and DSI (discrepancy between vendor documentation and actual system behavior

Because of this foundation, MappSci's consultants are able to efficiently conduct root cause analysis for problems encountered by change management coordinators, system administrators, auditors, subject matter experts, data analysts, application configurators, etl architects, interactive/batch application developers, and CNC personnel.

On average, MappSci produces tested OMW objects faster than the rest.

Moreover, the execution times of JDE E1 applications and interoperability solutions designed and created by MappSci execute faster (low latency) and are easier to maintain because of its foundation.

Furthermore, the "efficiency" products described in the services section would not exist without this foundation. This foundation continues to grow as JD Edwards EnterpriseOne evolves.


Chronology of Principal's Progress - Technical Skills


  • In 1999, transitioned from 4 1/2 years of Unix/csh/C/Java/Oracle/NT/VisuaStudio/MFC/SQL Server into JD Edwards One World.
  • From 1999 until 2006, attained expert level competence on JD Edwards One World:
    1. Development Tools - grid row document attachment, where used report, Object Librarian, Data Dictionary, Table Design Aid, Business View Design Aid, Business Function Design Aid (Named Event Rules and C), Form Design Aid, Report Design Aid (Table Conversions), JDE Debug, Visual Studio
    2. Interoperability - Windows DLL (inbound and outbound), Gencom, ODBC/Z-files/Subsystem processing, EDI, Bank Transfer File.
    3. Clients - Citrix, Windows RDP, Windows VM
  • From 2007 to 2008, create C#.Net forms applications for Windows desktops.
  • From 2008 to present, attaining expert level competence on JD Edwards Enterprise One:
    1. Development Tools - Object Management Work Bench, Oracle JDeveloper, BI Publisher
    2. CNC - Package Build Definition Director, Object Configuration Manager, Package Deploy Definition Director, Security Matrix, QSoftware, Weblogic, Enterprise One AIS Server.
    3. Interoperability - Business Services (inbound and outbound), OC4J, WSDL, OC4J, SOAP, RESTful, JSON
  • 2010, attained intermediate level competence on CreateForm
  • From 2008 to 2015, attained expert level competence (Administration and Scripting) on Data System's International's dcLINK radio frequency data collection system and mobile enterprise platform.
  • From 2018 to 2019, attained expert level skills on Excel VBA macros.
  • From 2015 to present, attaining expert level competence on bash and Mac OSX.
  • From 2015 to present, attaining intermediate level competence on Oracle Orchestator, PHP, Python, Go, Javascript, VB, Swift, React, React Native, JSX, Android (Java), iOS (Swift), HTTP, RESTful, Jupyter
  • From 2018 to present, attaining intermediate level competence on AWS Cloud (CLI, Javascript SDK, Lambda, Gateway, EC2, RDS, EBS, S3, Cloudfront, Route 53)
  • October 6, 2020 AWS Cloud Practitioner Certified


Foundation


The foundation of MappSci's functional practice is rooted in its experiences with data, data structures, entity relationship models, various file formats, listening, explaining, relationship building, proof-of-work artifacts, software development life cycle, user interface design, segregation of duties, compliance, marketing, accounting, purchasing, distribution operations, mro, and manufacturing.

These experiences are made up of many hours working on:

  1. CNC
  2. System Administration
  3. Address Book
  4. Sales Order
  5. Procurement
  6. DRP
  7. WMS
  8. General Accounting
  9. Accounts Payable
  10. Accounts Receivable
  11. Cooperative Advertising
  12. EDI
  13. VMI
  14. Master Data Management
  15. RFID
  16. Time Keeping
  17. Security
  18. MRO
  19. Quality Control
  20. Production Scheduling
  21. Manufacturing
  22. MRP
  23. Bar Coding
  24. Asset Management
  25. Blend Management
  26. UTB
  27. Databrowser
  28. PL/SQL

Moreover, these experiences comprise:

  1. Design sessions
  2. Entity relationship modeling
  3. Requirements gathering
  4. Flowchart creation
  5. Wireframe creation
  6. Design documentation
  7. Conference room pilots
  8. Training sessions
  9. Data mapping
  10. Data retrievals
  11. System administration
  12. Functional support sessions with Oracle (discrepancy between vendor documentation and actual system behavior

Because of this foundation, MappSci's consultants are efficient at:

  1. Gathering requirements
  2. Evaluating requests to modify existing applications.
  3. Evaluating requests to create new applications.
  4. Creating entity relationship models.
  5. Creating flowcharts
  6. Creating wire frames
  7. Creating design documents
  8. Creating sign-off documents
  9. Creating training documents
  10. Creating user manuals.
  11. Creating operations manuals.


Chronology of Principal's Progress - Functional Skills


  • In 1999, transitioned from user support and software engineering to business systems analysis
  • From 1999 to 2006 - Excel, User Overrides, Version Overrides, UTB, Batch Version, Interactive Version, Processing Options, Data Selection, Cooperative Advertising Management System, UDC, Sales Order Processing, Order Activity Rules, Sales Revenue Allocation, Automatic Accounting Instructions, Accounts Payable, Accounts Receivable, EDI, Ansi X12, Bank Transfers, Vendor Managed Inventory, Master Data Management, Warehouse Management System, Work Center, SQL, PL/SQL.
  • From 2007 to present - QSoftware/Security, DSI Bar Coding, CreateForm, BarTender, MRO, Asset Management, Purchase Order Processing, Shop Floor, Warehouse Management System, Data Browser, XML, JSON, CSS, NoSql, Excel Macros, Google Sheets, Google Sheets Macros


Products of curiosity, research, experimentation, and perseverance.


  1. Concise and well written documents (e.g. requirements, approval, design, and test)
  2. Concise flowcharts
  3. Descriptive wire frames
  4. Procedure document for fat client development, testing, and debugging of OMW objects.
  5. Procedure document for fat client development, testing, and debugging of published business services objects.
  6. Sensible best practices and standards document that increase developer throughput and produce maintainable solutions that exhibit low latency.
  7. Bolt on interactive and Z-processing applications that are made up of "BeginDoc, EditDoc, EndDoc" business functions.
  8. "MVC guided" and "upgrade friendly" modifications to vanilla JD Edwards objects.

email: mappsci@gmail.com

phone: (562) 348-5653


What is MappSci's billing rate for traditional JD Edwards techno-functional consulting services?

$100/hr.


What we expect to see in your initial email or hear in your initial voice mail?

Preferably, your interest in one of our C packages. If it is something else, then a brief description of what you have in mind. It would also be nice if you leave your phone number and the best time to call you back.


What happens during the initial conversation?

If you are interested in one of the C packages, we discuss your assumptions and expectations. If you come to the conclusion that our service is worth the price, we inform you of the days when we can perform the work. After you pick a day, we remind you that we require fat client access on your VPN. We do the work in 10 or 20 hours. We then send you the invoice.

If you are interested in something else (e.g. wrapping vanilla business functions in business services, bolt on header detail applications, level break reports, and subsystem processes related to integration and edi), we will discuss.



What other services can MappSci provide?

  1. DSI dcLink and Mobile Enterprise Platform Radio Frequency Bar Coding Application Design and Scripting
  2. PL/SQL Scripting
  3. Amazon Web Services Integration