B2B Gateway processes

Processes for EDI X12 and EDIFACT messages

EDI X12 message versions

The pre-packaged EDI processing mappings support EDI message versions:

• - 2001
• - 2002
• - 3010
• - 3020
• - 3030
• - 4010
• - 4020
• - 4030
• - 4040
• - 4050
• - 4060
• - 5010
• - 5020
• - 5030
• - 5040
• - 5050
• - 6020
• - 6040
• - 6050
• - 7010

EDI X12 messages

The pre-packaged EDI processing mappings support the following message types for EDI X12 messages:

Message description	Message type
Air Freight Details and Invoice	110
Return Merchandise Authorization and Notification	180
Secondary Mortgage Market Investor Report	203
Motor Carrier Load Tender	204
Motor Carrier Freight Details and Invoice	210
Motor Carrier Bill of Landing	211
Transportation Carrier Shipment Status Message	214
Motor Carrier Pickup Manifest	215
Logistics Service Response	220
Response to a Cartage Work Assignment	225
Motor Carrier Package Status	240
Account Assignment/Inquiry and Service/Status	248
Residential Mortgage Insurance Explanation of Benefits	259
Application for Mortgage Insurance Benefits	260
Mortgage or Property Record Change Notification	266
Medicare Benefits Inquiry	270
Medicare Benefits Response	271
Salvage transaction	272
Booking Request	300
Booking Confirmation	301
Shipping Instructions	304
Customs Manifest	309
Freight Receipt and Invoice	310
Status Details (Ocean)	315
Customs Status Information	350
Customs Events Advisory Details	353
U.S. Customs Acceptance/Rejection	355
U.S. Customs In-Bond Information	357
Customs Consist Information	358
Rail Carrier Shipment Information	404
Rail Carrier Freight Details and Invoice	410
Shipment Weights Transaction Set	440
Routing Request	753
Routing Instructions	754
Invoice	810
Consolidated Service Invoice/Statement	811
Credit/Debit Adjustment	812
General Request, Response or Confirmation	814
Cryptographic Service Message	815
Organizational Relationships	816
Remittance Advice	820
Lockbox	823
Application Advice	824
Planning Schedule with Release Capability	830
Price/Sales Catalog	832
Procurement Notices	836
Trading Partner Profile	838
Product Transfer Account Adjustment	844
Price Authorization Acknowledgment/Status	845
Inventory Inquiry/Advice	846
Response to Product Transfer Account Adjustment	849
Purchase Order	850
Product Activity Data	852
Purchase Order Acknowledgment	855
Advance Ship Notice	856
Purchase Order Change Request	860
Receiving Advice/Acceptance Certificate	861
Shipping Schedule	862
Text Message	864
Purchase Order Change Acknowledgment/Request	865
Product Transfer and Resale Report	867
Order Status Report	870
Grocery Products Purchase Order	875
Grocery Products Purchase Order Change	876
Grocery Products Invoice	880
Item Maintenance	888
Warehouse Shipping Order	940
Warehouse Stock Transfer Shipment Advice	943
Warehouse Stock Transfer Receipt Advice	944
Warehouse Shipping Advice	945
Warehouse Inventory Adjustment Advice	947
Response to a Load Tender	990
EDI Functional Acknowledgment	997
EDI Technical Acknowledgment	TA1

EDIFACT messages

The pre-packaged EDI processing mappings support the following message types for EDIFACT messages:

Message Description	Message Type
Application Error and Acknowledgement	APERAK
Invoice	INVOIC
Remittance Advice	REMADV
Planning Schedule with Release Capability	DELFOR
Purchase Order	ORDERS
Purchase Order Acknowledgment	ORDRSP
Advance Ship Notice	DESADV
Purchase Order Change Request	ORDCHG
Purchase Order Change Acknowledgment/Request	ORDRSP
EDIFACT Acknowledgment	CONTRL
Instruction to Dispatch	INSDES
Order Status Report	OSTRPT
Receiving Advice	RECADV
Balance of Payment Information from Customer	BOPINF
Price/sales Catalogue Message	PRICAT
Customs Response Message	CUSRES
Customs Conveyance Report Message	CUSREP
International Multimodal Status Report Message	IFTSTA
Inventory Report Message	INVRPT
Sales Data Report Message	SLSRPT
Container Announcement Message	COPARN
Container Discharge/Loading Order Message	COPRAR
Customs Cargo Report Message	CUSCAR
Firm Booking	IFTMBF
Instruction Message	IFTMIN
Forwarding and Transport Schedule	IFTSAI
Instruction Contract Status Message	IFTMCS
Dangerous Goods Notification Message	IFTDGN
Forwarding and Consolidation Summary Message	IFCSUM
Container Discharge/Loading Report Message	COARRI
Container Gate-In/Gate-Out Report Message	CODECO
Bayplan/Stowage Plan Occupied and Empty Locations Message	BAPLIE

EDIFACT message versions

The pre-packaged EDIFACT processing mappings support the following EDIFACT message versions:

• - D00B
• - D00A
• - 95B
• - 96B
• - 98B
• - 99B
• - 02B
• - 01A

Inbound process for EDI messages

1. 1When an inbound process runs, B2B Gateway runs the B2B Gateway pre-packaged, EDI processing mapping. The source and target of the mapping are based on the source and target details from the partners definition metadata. The source of the mapping is the location from where to read the incoming messages, and the target of the mapping is an interface file on B2B Gateway.
2. 2The mapping converts the EDI messages to XML interface files, one file for each functional group, and places the files on B2B Gateway.
3. 3B2B Gateway validates the incoming messages. If any of the validations fail, B2B Gateway rejects the message and creates an error event.
4. 4If during partner configuration you selected to send technical or functional acknowledgments to the partner, B2B Gateway sends an EDI functional and technical acknowledgment to the partner.
5. 5If during partner configuration you assigned a process-to-backend custom mapping for the inbound flow, B2B Gateway runs the mapping. If you assigned values to mapping parameters during partner configuration, B2B Gateway uses the values in the mapping flow.
If you did not assign a mapping, the inbound process ends with the placement of the interface files on B2B Gateway. You can use your own method to processes the interface files to your backend systems.

Outbound process for EDI messages

1. 1When an outbound process starts, B2B Gateway first runs the custom process from the backend mapping that you defined in the partner definition. The output of the mapping should be interface files that include the messages to send to your partners. The mapping places the files on B2B Gateway.
2. 2B2B Gateway uses the pre-packaged, EDI processing mapping to read the interface files, and then enriches the data in the interface file with the partner metadata and creates valid EDI messages. If you assigned values to mapping parameters during partner configuration, B2B Gateway uses the values in the mapping flow.The mapping source and target details are based on the partner definition metadata. The source of the mapping is the interface files, and the target of the mapping is the location where to send the messages.

Processes for custom files with custom mappings

Inbound process for custom files

• •Two-step processing, using two custom mappings. An inbound mapping reads the file that the partner sends, processes it, and writes the file to an interface file on the B2B Gateway document store. A process-to-backend mapping then writes the data to the backend system. When you use two-step processing, you can use a single process-to-backend mapping to process all inbound custom files to your backend system from a single interface file.
• •Single-step processing. A single custom mapping reads the file that the partner sends, processes it, and writes the file directly to the backend system. When you use single-step processing, you must write the logic of writing the data to the backend system for every inbound custom file from each partner.
• •Intelligent Structure Discovery processing. Use Intelligent Structure Discovery to discover the file structure of a custom input file, and auto-generate a parsing process that creates an interface CSV file with the discovered content. The Intelligent Structure Discovery parsing process replaces a custom inbound mapping. You can also create a custom process-to-backend mapping to process the auto-generated interface file to the backend system.

1. 1When an inbound process runs, B2B Gateway runs the inbound mapping that you assigned the partner. The source and target of the mapping are based on the source and target details from the partners definition metadata. The source of the mapping is the location from where to read the incoming files. The target of the mapping can be either an interface file on B2B Gateway or the backend system.
2. 2If the target of the inbound mapping is an interface file on B2B Gateway, and if during partner configuration you assigned a process-to-backend mapping for the inbound flow, B2B Gateway runs the defined mapping. If you assigned values to mapping parameters during partner configuration, B2B Gateway uses the values in the mapping flow.The mapping writes the data to the backend system.
If you did not assign a process-to-backend mapping, the inbound process ends with the placement of the interface file on B2B Gateway. You can use your own method to write the data to the backend system.
3. 3If the target of the inbound mapping is the backend system, B2B Gateway writes the data to the backend system.

Outbound process for custom files

1. 1When an outbound process starts, B2B Gateway first runs the custom process from the process-from-backend mapping that you defined in the partner definition and reads the data from the backend system. If you assigned values to mapping parameters during partner configuration, B2B Gateway uses the values in the mapping flow.
2. 2The mapping writes the data to an interface file on B2B Gateway.
3. 3If during partner configuration you assign an outbound mapping for the flow, B2B Gateway runs the mapping and sends the files to your partner. If you assigned values to mapping parameters during partner configuration, B2B Gateway uses the values in the mapping flow. If you did not assign an outbound mapping, the outbound process ends with the placement of the interface files on B2B Gateway. You can use your own method to send the files to your partner.

Process for inbound custom files with Intelligent Structure Discovery