Compliance checking and data mapping

Table 26-1 illustrates the compliance checking and data mapping processes that ECMap performs.

The switches are for running the RTP from a batch command file script.

**Table 26-1: Compliance checking and data-mapping processes**
Type of verification	Description of verification activity	Checked automatically
Valid Data Type	Checks datatype attribute of both fields to verify compatibility when source is mapped to destination.	RTP
Valid Data Size	Checks to see if an EDI element is mapped to a data field smaller than the element’s maximum width. Generates a warning message that can be suppressed by selecting the Truncate box on the Mapping – Element window.	RTP
Matching Control Counts	Checks control counts for mismatches on inbound maps. Generates a warning message.	RTP
Mandatory Segments	Checks for mandatory segments. On inbound maps, segments that cause a level change are usually mandatory. On outbound maps, mandatory segments are typically associated with mandatory records. Generates a warning message.	Compliance Map [-k switch or defined flow] [user override allowed]
Mandatory Elements	Checks for mandatory elements. Elements are mandatory unless the Mandatory check box is unchecked on the Mapping – Element window.	RTP [user override allowed]
Valid Standards Code List Value	Verifies that elements defined as ID data types have valid code values using a cross reference table.	Compliance Map
Correct Segment Sequence	Checks to see whether the segments are in the correct sequence in inbound transaction maps.	Compliance Map [-k switch]
Correct Number of Segments	Verifies that the transaction contains the correct number of segments. This can also be checked by attaching to the flow a rule command that determines the number of included segments by querying the SE01 value.	Compliance Map [-k switch]
Correct Element Usage According to Syntax Rules	Verifies that elements conform to the syntax rules of the standards with user-created rules in the compliance map Once the rules are created, the rule definitions can be imported into other maps.	Compliance Map
Correct Number of Elements in a Segment	Verifies that the number of elements in the segment does not exceed the EDI Standards definition.	Compliance Map [-k switch]
Correct Number of Loop Counts	Verifies that the number of loops for the segment does not exceed the EDI Standards definition.	Compliance Map [-k switch]

Table 26-2 illustrates the compliance checks that you can perform at the application level.

**Table 26-2: Compliance checks performed at the application level**
Type of verification	Description of verification activity	Checked automatically
Valid Data	ECMap provides the flexibility for the user to create “programming logic” that defines unique editing criteria for compliance and data validation using the extended command set provided in the rule function. Once you have developed the rules, performing them at precise stages of map execution can achieve the results dictated by user requirements. Myriad map components can be used to develop “programming logic” for compliance and data validation, including application record and file definitions, segment and element map assignments, rule definitions, flow definitions and rule assignments, and runtime switch and option settings.	RTP [user override allowed]
Valid Trading Partner	For both inbound and outbound transactions, you must associate a valid trading partner with the map by setting up a trade agreement that links the trading partner with the map. To override the assigned trading partner, select the ALL TradePartner default box on the Run Inbound or Outbound Map window.	RTP [user override allowed]