How the integration imports the resources generating with a prefix of M or L

The resource codes are prefixed with M or L. How does this affect the FactoryMaster / Orchestrate data import integration?

The resources that start with [M] or [L] generate during the import from FactoryMaster (FM) to Orchestrate and are working as designed. The FM views vOrcData_ResourceCodes_3_AssociatedLabour and vOrcData_LabourCodes_3_AssociatedLabour on the FM database controls the resource import and creates these prefixes.

With the new API data import, the data sequences imports the resource codes from FactoryMaster to Orchestrate with the same name (and not the underscrore).
​