Find new rcvX12_3040_850.wsdl?

Question

I am trying to setup Oracle BPEL/B2B POs using 3040 standard. 4010s are working fine. My best guess right now is that I need WSDL written especially for 3040, because what we have deployed is a version that supports 4010. We deploy using JDEV.
Can anyone help me find a file similar to the below, but supports the 3040 standard? Obviously, I hope I don't have to write one of my own.
I do have a X12_3040_850.xsd file which I would like to put in place of the X12_4010_850.xsd mentioned below.
I am using a project that has this file supporting 4010 already defined. I need to add the 3040 standard to my project.
Anyone have a clue where I can get a 3040 version this file? (below)
==========================
<definitions name="rcvX12_4010_850"
targetNamespace="http://xmlns.oracle.com/pcbpel/adapter/aq/rcvX12_4010_850/"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://xmlns.oracle.com/pcbpel/adapter/aq/rcvX12_4010_850/"
xmlns:plt="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:jca="http://xmlns.oracle.com/pcbpel/wsdl/jca/"
xmlns:pc="http://xmlns.oracle.com/pcbpel/"
xmlns:imp1="urn:oracle:integration:b2b:719EF3F3221345ABA0FFBB4F5AB0D5FD"
xmlns:obj1="http://xmlns.oracle.com/xdb/B2B">
<types>
<!-- Define AQ Headers = Payload Headers + Static Queue Headers -->
<schema attributeFormDefault="qualified" elementFormDefault="qualified"
targetNamespace="http://xmlns.oracle.com/pcbpel/adapter/aq/rcvX12_4010_850/"
xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:tns="http://xmlns.oracle.com/pcbpel/adapter/aq/rcvX12_4010_850/"
xmlns:hdr="http://xmlns.oracle.com/pcbpel/adapter/aq/inbound/"
xmlns:obj1="http://xmlns.oracle.com/xdb/B2B">
<import namespace="http://xmlns.oracle.com/xdb/B2B"
schemaLocation="B2B_IP_MESSAGE_TYPE.xsd"/>
<import namespace="http://xmlns.oracle.com/pcbpel/adapter/aq/inbound/"
schemaLocation="aqAdapterInboundHeader.xsd"/>
<complexType name="HeaderCType">
<sequence>
<!-- static header -->
<element name="QueueHeader" type="hdr:HeaderType"/>
<!-- payload header -->
<element name="PayloadHeader" type="obj1:IP_MESSAGE_TYPE"/>
</sequence>
</complexType>
<element name="Header" type="tns:HeaderCType"/>
</schema>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="urn:oracle:integration:b2b:719EF3F3221345ABA0FFBB4F5AB0D5FD"
schemaLocation="X12_4010_850.xsd"/>
</schema>
</types>
<message name="Transaction-850_msg">
<part name="Transaction-850" element="imp1:Transaction-850"/>
</message>
<message name="Header_msg">
<part name="Header" element="tns:Header"/>
</message>
<portType name="Dequeue_ptt">
<operation name="Dequeue">
<input message="tns:Transaction-850_msg"/>
</operation>
</portType>
<binding name="Dequeue_binding" type="tns:Dequeue_ptt">
<pc:inbound_binding/>
<operation name="Dequeue">
<jca:operation ActivationSpec="oracle.tip.adapter.aq.inbound.AQDequeueActivationSpec"
QueueName="IP_IN_QUEUE" DatabaseSchema="B2B"
ObjectFieldName="PAYLOAD" PayloadHeaderRequired="true"
Consumer="X12_4010_850_PO" OpaqueSchema="false"></jca:operation>
<input>
<jca:header message="tns:Header_msg" part="Header"/>
</input>
</operation>
</binding>
<service name="rcvX12_4010_850">
<port name="Dequeue_pt" binding="tns:Dequeue_binding">
<!--Your runtime connection is declared in
J2EE_HOME/application-deployments/default/AqAdapter/oc4j-ra.xml
These mcf properties here are from your design time connection and
save you from having to edit that file and restart the application server
if eis/AQ/aq is missing.
These mcf properties are safe to remove.-->
</port>
</service>
<plt:partnerLinkType name="Dequeue_plt">
<plt:role name="Dequeue_role">
<plt:portType name="tns:Dequeue_ptt"/>
</plt:role>
</plt:partnerLinkType>
</definitions>

Answer 1

after much stumbling, I went into the Partner Link in my JDev bpel project, clicked upon 'Define Adapter Service' which allowed me to create a new aq adapter, which would allow me to import the 3040 schema and point to the b2b on the server.
I hope this will save somebody else time.
Does anybody have a link to really, really good documentation for jdev bpel projects, helping to build B2 EDI over GENERIC EXCHANGE?
right now it looks like I hav to make a new project and bpel process for every standard: ie: one for 4010. one for 3040. one for 3020. one for 3010. different mappings and processes for each.
am I right about that?