Posts

Data Mapping NCPDP SCRIPT


EDI (Electronic Data Interchange) standards allow participants with different roles in an industry to communicate clearly and rapidly, and date back to the earliest implementations of electronic communication in the 1950s, long before modern business technologies such as ERP, CRM, and many others. Yet even today, EDI standards continue to evolve to support new requirements and opportunities.

MapForce has long supported data mapping to and from ANSI X12, UN/EDIFACT and other popular EDI standards, and now in the latest release adds support for data mapping NCPDP SCRIPT.

SCRIPT is the state of the art EDI standard developed by the National Council for Prescription Drug Programs (NCPDP) for electronically transmitting medical prescriptions, also known as ePrescribing (eRX) in the United States.

Read more…

Tags: , , ,

MapForce Server Accelerator Edition Achieves a New Level of Data Transformation Performance


MapForce Server automates recurring execution of data mappings and transformations designed and tested using Altova MapForce. Every day, MapForce Server is employed in business communication, financial reporting, database ETL, and many other applications to transform critical data between any of XML, JSON, database, EDI, XBRL, flat file, CSV, Excel, and/or Web service formats.

Now, MapForce Server Accelerator Edition offers even faster throughput for high-performance server platforms.

Read more…

Tags: , ,

How to Debug XSLT and XQuery


Nothing’s more frustrating than getting unintended results from an XSLT or XQuery transformation and having to spend hours tracking down the issue – especially if you’ve inherited the project from another developer or haven’t looked at the code in a few months.  Of course, XMLSpy has long included an XSLT debugger and XQuery debugger for setting break points and stepping through transformations to identify problems. However, the debugging process just got even more interactive and precise with the introduction of XSLT/XQuery back-mapping.

With back-mapping enabled, you can simply click on or hover over the portion of your output document you want to zero in on, and XMLSpy will immediately highlight the source XML and XSLT or XQuery instruction that is responsible. Let’s see how it works.

Debug XSLT with back-mapping

Read more…

Tags: , , , , , , , ,

A Typical MapForce Server Use Case


Envision a manufacturing company that controls costs by exploiting a just-in-time assembly process with a very low supply of parts inventory on hand. New customer orders are logged in a sales database and at the end of every day the components needed to assemble that day’s sales are tabulated.

The IT department runs a SQL query to identify the required parts and transforms the list into a purchase order in JSON format to be transmitted to the supply chain.

Sound familiar? Our recent blog series on JSON tools and JSON data mapping were based on this real-life scenario. In this post we describe a MapForce Server use case that automates the repetitive task of generating each day’s purchase order.

Read more…

Tags: , , ,

JSON Data Mapping and Transformation with MapForce


JSON is a popular format for transferring data between systems thanks to its simple markup, small footprint, and heritage based on the JavaScript programming language. MapForce supports JSON as both an input and output format for JSON data mapping and transformation. For instance, MapForce can extract information from any popular database and produce a JSON file ready for transfer.
The Requirement: Here is an example of a typical need for JSON data mapping: A manufacturing company controls costs by exploiting a just-in-time assembly process with very little parts inventory on hand. New customer orders are logged in a sales database, and at the end of every day the components needed to assemble that day’s sales are tabulated via a query into the database. The required parts will be ordered from suppliers via a purchase order transferred in JSON format.

Read more…

Tags: , , ,

EDI Data Mapping with MapForce


Any computer industry standard that promotes reliability and clear communication between independent enterprises will have a long life. EDI (Electronic Data Interchange) originated in the 1960s to enable automated transactions between corporate computer systems. EDI remains in widespread use today and continues to evolve to meet modern requirements, under the administration of the UN/EDIFACT and ANSI standards bodies.

Altova MapForce supports EDI data mapping between EDI messages and XML, JSON, relational databases, flat files, Excel, or other data formats to bridge between commonly used information interchange and in-house technologies.

MapForce includes support for the latest EDIFACT versions 2015B and 2016A including the new VERMAS message. Mapping and translating EDIFACT messages to other usable data types for transfer, storage, and management is a common business requirement solved by MapForce.

container_ship1

Read more…

Tags: , , , ,

MapForce Offers Dynamic Access to Node Names


There are situations, especially when encountering loosely structured data, where you may want to map and transform structural components of a data stream along with content. MapForce 2017 includes a new feature to dynamically access node names of XML elements, attributes, or text file columns such as the contents of CSV files, to target components.

Dynamic access to node names allows creation on the fly of target elements and attributes whose names do not need to be known beforehand or specifically identified in the data mapping. This feature lets you create much more generic, flexible, and reusable mappings that require less manual intervention if data models evolve.

News about Dynamic Access to Node Names in MapForce 2017

Read more…

Tags: , , ,