QAD has given us the standard files to use with the current gateway programs. You should have received these files as part of Ecommerce. I don't know if these we had to pay for this, probably not. Once you get the standard definitions you should be able to process any type of document. We were told by QAD, that these definitions should never be changed because of how the gateway programs work. So take note if you plan on changing the MFG/PRO Definition and Exchange definition.
Again, the reason why you probably can't read a segment in to MFG/PRO is because it was not initally defined in the gateway programs.
We too are now using EDIFACT and X12, and have learned to use other segments that are not in use to populate other feilds and map to these feilds to output/input data that is not standard EDIFACT.
You should have received the following definitions when you got Ecommerce from QAD:
Exchange Def. Maintenace:
schedule in/out version 2
TASN out version 1
invoice out version 1
Purchase Order, out, version 1
MFG/PRO Def. Maint
Customer-schd, version 1/2, In
Invoice, version 1/2, Out
MFG856, version 1,Out/In
Ship-schd, version 1, In
Shipping-Notice, version 1, Out
there are more...
Once you have these, you can do as you please in Ecommerce from inbound to outbound transformation.
hope this clears some stuff up.
r
P.S.
A big part of this, is creating the implementation definitions and transformation maps using, 35.21.15.13 and 35.21.15.17. This is where you are having problems I take it, because that's were we also stumbled on once we started using EDI from MFG/PRO.