Integration Software & Toolsets
iEDIGroup creates proprietary software in the form of toolsets, conversion programs, and solutions written in open ended technology (such as XML and JAVA), legacy technology (such as COBOL or EASYTRIEVE), ERP languages (such as ABAP), C, C++, Visual Basic, and a variety of other programming languages. For iEDIHub™ clients requiring Enterprise Resource Planning (ERP) or Enterprise Information Systems (EIS) formats, there are iEDIGroup ENABLERS designed to work in harmony with iEDIHub™ . Additionally, if the client needs a program to 'load' the transaction to its back-end system, iEDIGroup provides the consultants to write the code for the client, or iEDIGroup writes the code and offers it via an ASP model to the client. The client has the choice of purchasing the solution or using the solution on a pay-per-use basis.

Proprietary Integration Software : VBConvert
iEDIGroup developed a Visual Basic application-to-application integration program to convert (map) a private format flat file to a static transaction flat file. This software is used to manage private data formats not in X12 format and was built to support the common private format used for reporting inventory positioning in the retail b2c arena. This data converter also support private formatted purchase orders, invoices, and shipping notices.

Proprietary Toolsets: SAP EDI/ALE IDOC Toolset
A set of 15 programs designed to extract IDOCs from SAP for download to the desktop (inbound SAP EDI transactions are translated to an IDOC format as required by the SAP system). The following ten utility programs have already been developed and are available for sale. Please contact iEDIGroup for more information.

• ZXECTK01
  This tool is used to retrieve IDOCs from R/3 and download them to a local text file. IDOCs can be selected individually or by an IDOC number range. This tool is primarily used during the test preparation phase. Test data can be created using this tool, as can unit and system test documentation. By default, the IDOCs are written to the local drive, however this default path can be overwritten at execution time.
• ZXECTK02
  This tool is a variation of the ZXECTK01 tool. It too extracts IDOCs from R/3 and writes the IDOCs to the local or network PC storage device, however the selection criteria have been expanded. The user can select by IDOC number, creation date/time message type and message status ranges. This more developed tool facilitates the creation of like test documents. Again a default drive\path\name are provided but can be overwritten.
• ZXECTK03
  Program ZXECTK03 tool is a further variation of the ZXECTK01 and ZXECTK02 tools. It extracts the specified IDOC from R/3 and downloads it to disk. The drive\path\filename are defaulted but can be changed by the user.
• ZXECTK04
  Program ZXECTK04 will upload an IDOC from a local text file and will place it in the inbound directory on the SAP server. The inbound process is then triggered and the IDOC will be processed as though it arrived via normal EDI processing. This tool is used in concert with ZXECTK01 and ZXECTK02 to cycle test documents back into R/3 to complete the test cycle process.
• ZXECTK05
  This tool provides documentation for SAP IDOC segments. The user supplies the IDoc segment name and the tool generates a formatted report describing the segment detail. This tool is used during the development phase and can also be used to provide system documentation.
• ZXECTK10
  This program reads through the IDOC control record table interrogating entries for those documents with status indicated by the user at program startup. The IDOC status is then modified to status IDOC is ready to be passed to the application'. For outbound IDOCs this status is 30 and for inbound IDOCs, this status is 64. This in effect 'readies' a document for application processing.
• ZXECTK11
  This program reads through the IDOC control record table looking for those IDOCs indicated by the user at program startup. It is a variation of tool ZXECTK10 except that the selection criteria have been expanded. The IDOC status is then modified to the status specified on the initial user selection screen. IDoc number, date/time, message type and/or IDOC status may select iDOCs.
• ZXECTK12
  The ZXECTK12 tool will read through the IDOC control record looking for those IDOCs having the status indicated by the user. Those IDOCs matching the status code criteria will have their status modified to an archival status. Archival status codes are '31' for outbound and '68' for inbound processing. This tool is primarily used to 'retire' those IDOCs, which for whatever reason remain in a non-standard status and require removal from the online IDOC pool.
• ZXECTK14
  This tool interrogates several of the internal R/3 communication configuration tables to determine whether the RFC table entries and port definitions are out of synch. Port definitions may become orphaned when new client builds are performed. This tool attempts to identify where referential integrity of the communication entries has been compromised.
• ZXECTK15
  This tool provides EDI/ALE system documentation. It analyzes several internal R/3 communication tables building linkages for ports, partner profiles, IDoc types, message types, process codes and function modules. Unused configuration can then be identified and removed.

Back