136 Target Model Syntax Error Cause Resolution Syntax error within the target data model. Error may be in the line above or below the line number reported Edit the data model for any of the following common syntax errors: Check for missing brackets and characters, such as, (,{,},). Check for upper-/lowercase spelling. Make sure the variable labels are spelled correctly. Check for arrow pointers (->) when referencing a MetaLink, Array, or Variable. The target data model specified in the map component file cannot be found. Check the name of the target data model in the map component file. Enter a valid target data model in the map component file. Check that the target data model exists. The access model associated with the given target data model is wrong (Access Obj “Segment for dm not found”). Assign the data model item with the proper item type. Assign a different access model to the map component file. The target data model base filename has not been entered at all or specified correctly. This issue arises when running generic models and the Process Tracking report returns an error of “Bypass with error 136". Check the target data model base filename at the Trading Partner lowest level-outbound values. Ensure that the target data model exists on the system.
16.2 release. Updated October 23, 2016