Skip to main content

iPaaS.com to Orderful Purchase Order Mapping Documentation

iPaaS.com transactions can be sent to Orderful as EDI 850 purchase orders, including their line items and addresses. The integration builds the purchase order header plus its children so a complete order is created in Orderful.

ID Format

Manual Sync ID Format

On the iPaaS.com Manual Sync page, enter the iPaaS.com transaction ID.

External ID Format

After the order is created, iPaaS.com saves the Orderful transaction identifier as the external ID on a dedicated external-ID record, which is the primary match for later updates to the same order.

Deleted Record Support

Outbound delete is not supported. Deletions are not propagated to Orderful, and delete mappings are not included in the default templates.

Custom Field Support

Several Orderful EDI header values are sourced from iPaaS.com custom fields populated by the inbound flow (for example, the Orderful purchase order code type and reference identifiers). No additional custom-field configuration is required.

Mapping Collection Status

  • Status: Enabled (filtered to order transactions)

  • Trigger Events: Enabled under the subscription's Outbound Data Flows by subscribing to the iPaaS.com transaction outbound triggers (transaction created and updated). No orders are sent automatically until those triggers are enabled.

Duplicate or Conflicting Mappings

  • Add Orderful Purchase Order TO iPaaS.com transfers purchase orders in the opposite direction.

  • Update Orderful Purchase Order Status TO iPaaS.com updates the status of an existing purchase order.

Review the filters and Add/Update settings before enabling these together, and decide which system is the source of truth.

Supported Child Collections

  • Add Orderful Purchase Order Line FROM iPaaS.com — the line items sent on the order.

  • Add Orderful Purchase Order Address FROM iPaaS.com — the addresses sent on the order.

System Caveats

iPaaS.com Caveats

A purchase order must include at least one address and at least one line item, or the transfer fails. The order type filter limits this collection to transactions of type Order.

Orderful Caveats

The Orderful stream (TEST or LIVE) must match your target environment; sending to the wrong stream routes the order to the wrong Orderful environment.

Setup Requirements

Enable this transfer under the subscription's Outbound Data Flows by subscribing to the iPaaS.com transaction created and updated triggers. Until those are enabled, no purchase orders are sent to Orderful.

Integration Flow

  1. A transaction of type Order is dispatched from iPaaS.com (by an enabled outbound trigger or Manual Sync).

  2. The integration builds the 850 purchase order header with its addresses and line items and creates it in Orderful.

  3. Orderful returns its transaction identifier, which iPaaS.com saves as the external ID.

Mappings

Add Orderful Purchase Order FROM iPaaS.com

Mapping Filter: Type == "Order" — only transactions whose type is Order are processed; transactions of any other type are skipped.

The 850 purchase order header.

Mapping Type

Source Field (iPaaS.com)

Destination Field (Orderful)

Description

Field

TransactionNumber

BeginningSegmentForPurchaseOrder_PurchaseOrderNumber

The purchase order number, taken from the transaction number.

Field

Orderful Purchase Order Code Type

BeginningSegmentForPurchaseOrder_PurchaseOrderTypeCode

Type of order; SA means Standalone.

Field

Orderful Transaction Set Purpose Code

BeginningSegmentForPurchaseOrder_TransactionSetPurposeCode

Purpose of the order; 00 means Original.

Field

Orderful Delivered DateTimeReference Date

Delivered_DateTimeReference_Date

The delivered date corresponding to the delivered qualifier.

Dynamic Formula

Delivered qualifier

Delivered_DateTimeReference_DateTimeQualifier

Type of date given (DTM02); 002 means Delivery Requested.

Dynamic Formula

Line item count

NumberOfLineItems

The count of line items on the order.

Field

Orderful Receiver isaID

Receiver_IsaId

The receiver's ISA interchange ID.

Field

Orderful Reference Identification

ReferenceIdentification

The reference identification value.

Field

Orderful Reference ID Qualifier

ReferenceIdentificationQualifier

Type of reference (REF01); DP means Department Number.

Field

Orderful Sender isaID

Sender_IsaId

The sender's ISA interchange ID.

Field

Orderful Shipped DateTimeReference Date

Shipped_DateTimeReference_Date

The shipped date corresponding to the shipped qualifier.

Dynamic Formula

Shipped qualifier

Shipped_DateTimeReference_DateTimeQualifier

Type of date given (DTM02) for the shipped date reference.

Field

Orderful Transaction Set Control Number

TransactionSetHeader_TransactionSetControlNumber

A control number unique within the transaction set (length 4 to 9).

Static

"850"

TransactionSetHeader_TransactionSetIdentifierCode

The X12 transaction set identifier code for a purchase order.

Static

"850_PURCHASE_ORDER"

Type_Name

Required to create the purchase order in Orderful.

Field

Orderful Stream

Stream

Placeholder — set to match your environment (TEST for testing, LIVE for production) before go-live.

Add Orderful Purchase Order Line FROM iPaaS.com

The line items sent on the order. Each line links to the parent order by a composite external ID made of the line number and the parent transaction ID (for example, 1 then 4). At least one line item is required.

Mapping Type

Source Field (iPaaS.com)

Destination Field (Orderful)

Description

Field

SequenceNumber

AssignedIdentification

The line number of the item.

Field

Description

Description

A free-form product description.

Field

Orderful Item Description Code Type

ItemDescriptionTypeCode

Type of item description (PID05); F means Free-Form.

Dynamic Formula

Product/service identifier

ProductServiceID

The product/service identifier per the qualifier (PO105).

Field

Orderful Product Service ID 1

ProductServiceID1

The second product/service identifier value (PO107).

Field

Orderful Product Service ID Qualifier

ProductServiceIDQualifier

Type of item reference (PO106); UP means Universal Product Code.

Field

Orderful Product Service ID Qualifier 1

ProductServiceIDQualifier1

The second item reference qualifier (PO108); VN means Vendor's Item Number.

Field

Qty

Quantity

The quantity ordered.

Dynamic Formula

Unit of measure

UnitOrBasisForMeasurementCode

The unit of measure for the quantity (PO102); CA means Case.

Field

UnitPrice

UnitPrice

The price of the item for the unit of measure.

Add Orderful Purchase Order Address FROM iPaaS.com

The addresses sent on the order. Each address links to the parent order by a composite external ID made of the entity identifier code and the parent transaction ID (for example, ST then 4). At least one address is required.

Mapping Type

Source Field (iPaaS.com)

Destination Field (Orderful)

Description

Field

Address1

AddressInformation

The first line of the address.

Field

City

CityName

The city of the address.

Dynamic Formula

Address role

EntityIdentifierCode

The EDI entity identifier code; BT means Bill To, ST means Ship To.

Field

FirstName

Name

The party name on the address.

Field

PostalCode

PostalCode

The postal code of the address.

Field

Region

StateOrProvinceCode

The two-character state or province code.

Error Handling

See the Orderful Error Messages article for the full catalog. This outbound flow surfaces "Transaction could not be created because the Address information is missing." and "Transaction creation failed. No line items were provided." — resolution: ensure the transaction has at least one address and at least one line item before transferring.

Testing & Validation

Test Scenarios

  1. Create an Order transaction in iPaaS.com with at least one address and one line item, transfer it, and verify the 850 is created in Orderful.

  2. Attempt a transfer with no line items and confirm the expected error.

  3. Re-transfer an updated order and verify it updates the existing Orderful order rather than creating a duplicate.

Validation Checklist

  • The 850 is created in Orderful with header, addresses, and line items.

  • The Orderful transaction ID is saved as the external ID.

  • The stream value matches the intended environment.

Related Documents

Did this answer your question?