Custom API-based OM Processing Constraints for Order Import

In a 12.2.4 EBS instance (DB v12.1.0.2), I have written a proof of concept package that I can reference in OM Processing Constraints. This works a treat on both the Sales Orders Form and when attempting to import from the OM Open Interface.

I am able to reference FND_PROFILE.VALUE ('USER_ID') in a procedure and use that for a simple logical check, keeping a named application user from creating Order Headers. I am not able to perform discrete validation on individual records, though I believe that the components to do so exist. During a run of Order Import, it seems reasonable that table data should be available record-by-record by referencing a global variable initialized by the standard process.