This Howto tries to show a proven, manual procedure for system analysis/revision. Practice shows that EDI landscapes are subject to frequent changes or adaptations to given situations. Therefore, the extensions tend to make a system confusing and often even contain obsolete artifacts, which then make the overview even more difficult. eBiss offers suitable methods to keep where-used lists for the most important objects and to follow the processes from A-Z via hyperlink through the different process instances. Nevertheless, certain things remain somewhat hidden and only become apparent through further analysis.

Note: With the module Analytics many of the following steps can already be prepared automatically and inserted into your own system documentation under My system.

The system revision is a Reverse engineering which reverses and/or opens up the process described under Set up a data link with conversion.

Note: A consistent application of the Naming conventions in eBiss facilitates the system analysis and increases the consistency crucially.

With the following steps it is possible to analyze a system for its actual function.

Identify the active Automations¹⁾

Open the job²⁾ via the link in the active automation and identify its task.³⁾.

1. INBOUND process can be recognized by the direction setting “INBOUND” of the ReceiveChannel or BackendObjectRetriever used in it⁴⁾.
2. OUTBOUND process can be recognized by the direction setting “OUTBOUND” of the ReceiveChannel or BackendObjectRetriever used in it.
3. Other processes like CleanUp, WebServer etc. which have nothing to do with the actual EDI tasks but should run automatically.

1. Identify business logic in the job⁵⁾ and the associated Variable definitions and its Where-used list for variable instances⁶⁾.
2. Note: Trace all DelegatorJob or EventRouter Paths of the job!
3. Take note of the EntitySelector and EntityTransformer selection strategy settings!
4. Take note of the XPATH expressions in the MessageSelectors!
5. Take note of any preselections of the repositories in the EntityAnalyzer!

Identification of integration and involved or effectively used send/receive channels or BackendObjectReceiver/Transmitters and their properties depending on Typsätze and fixed channel settings in system, trading or template partners and in fixed defined ChannelSender.

Note: In addition to Channels, there are also alternative integrations via BackendObjektIntegrationen see Integration types. These integrations can be recognized by the corresponding associated job objects and variable instances on the system partner.

Note: The grouping possibilities in the eBiss Grid-View is very helpful to get an overview of the set endpoints (the system endpoints, which are defined in the channels, are excellent to outline the EDI landscape and to recognize the involved systems). Attention: Backend integrations are defined differently.

Identification of the required message box and their characteristics⁷⁾. The effectively needed message boxes are to be considered in direct dependence with the needed channels⁸⁾.

Identification of the TadingPartner templates and their Typesets

Note: Use where-used list of TemplatePartners!

Identification of the required mappings⁹⁾ via the dependencies in typeset definitions or EntityTransformer

Identification of required Entity Types and their components¹⁰⁾ depending on required Mappings and set Typesets

Identification of the required plugins depending on the required Entity Types¹¹⁾.