Skip to main content

Orderful to iPaaS.com Purchase Order Acknowledgement Mapping Documentation

Orderful purchase order acknowledgements (EDI 855) can be transferred to iPaaS.com as transactions, including their addresses and line items. The integration records the acknowledgement header along with the Orderful EDI detail and message status. The transaction type is set to Hold.

ID Format

Manual Sync ID Format

On the iPaaS.com Manual Sync page, enter the Orderful transaction ID. Example: 1009.

External ID Format

iPaaS.com saves the Orderful transaction ID as the external ID on a dedicated external-ID record (the primary match for later updates). The transaction number is also stored for visibility and fallback matching.

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

The Orderful EDI detail is captured into iPaaS.com custom fields. No additional custom-field configuration is required.

Mapping Collection Status

  • Status: Enabled (filtered to acknowledgement documents)

  • Trigger Events: Retrieved by polling from Dashboard / Integration Monitoring / Events.

Duplicate or Conflicting Mappings

  • Add Orderful Purchase Order TO iPaaS.com brings in the original purchase order.

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

Review 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 Acknowledgement Address TO iPaaS.com — the addresses on the acknowledgement.

  • Add Orderful Purchase Order Acknowledgement Line TO iPaaS.com — the line items on the acknowledgement.

System Caveats

Orderful Caveats

Orderful does not provide an email address in standard EDI fields, so a static placeholder email is used (replace if a real address is needed). The acknowledgement transaction type is set to Hold.

iPaaS.com Caveats

Addresses and line items are recorded through the child collections. The transaction status is set from the Orderful status through a lookup translation.

Integration Flow

  1. A purchase order acknowledgement (855) is retrieved from Orderful by polling (or on demand via Manual Sync).

  2. The integration creates the iPaaS.com transaction with the acknowledgement header and the Orderful EDI detail.

  3. The acknowledgement's addresses and line items are recorded through the child collections.

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

Mappings

Add Orderful Purchase Order Acknowledgement TO iPaaS.com

Mapping Filter: Type.Name == "855_PURCHASE_ORDER_ACKNOWLEDGMENT" — only transactions whose type is an 855 acknowledgement are processed; transactions of any other type are skipped.

The acknowledgement header.

Mapping Type

Source Field (Orderful)

Destination Field (iPaaS.com)

Description

Static

EmailAddress

Placeholder — Orderful does not provide an email in EDI; replace before go-live.

Field

BusinessNumber

Orderful BusinessNumber

The trading-partner relationship the acknowledgement belongs to.

Field

BeginningSegmentForPurchaseOrder_Date

Orderful Date

The purchase order date on the acknowledgement.

Field

Delivered_DateTimeReference_Date

Orderful Delivered DateTimeReference Date

The date corresponding to the delivered qualifier.

Field

Delivered_DateTimeReference_DateTimeQualifier

Orderful Delivered DateTimeReference DateTimeQualifier

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

Field

href

Orderful href

The Orderful API address of the transaction message, for reference.

Field

AcknowledgmentStatus

Orderful Message Acknowledgement Status

APPROVED or REJECTED.

Field

DeliveryStatus

Orderful Message Delivery Status

DELIVERED or FAILED.

Field

BeginningSegmentForPurchaseOrder_PurchaseOrderTypeCode

Orderful Purchase Order Code Type

Type of order; SA means Standalone.

Field

BeginningSegmentForPurchaseOrder_PurchaseOrderNumber

Orderful Purchase Order Number

The purchase order number being acknowledged.

Field

Receiver_IsaId

Orderful Receiver IsaId

The receiver's ISA interchange ID.

Field

Receiver_IsaIdQualifier

Orderful Receiver IsaIdQualifier

The qualifier for the receiver's ISA interchange ID.

Field

Receiver_Name

Orderful Receiver Name

The name of the party receiving the acknowledgement.

Field

ReferenceIdentificationQualifier

Orderful Reference ID Qualifier

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

Field

ReferenceIdentification

Orderful Reference Identification

The reference identification value.

Field

Sender_IsaId

Orderful Sender isaID

The sender's ISA interchange ID.

Field

Sender_IsaIdQualifier

Orderful Sender IsaIdQualifier

The qualifier for the sender's ISA interchange ID.

Field

Sender_Name

Orderful Sender Name

The name of the party sending the acknowledgement.

Field

Shipped_DateTimeReference_Date

Orderful Shipped DateTimeReference Date

The date corresponding to the shipped qualifier.

Field

Shipped_DateTimeReference_DateTimeQualifier

Orderful Shipped DateTimeReference DateTimeQualifier

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

Field

Stream

Orderful Stream

The Orderful stream the transaction was received on, such as TEST or LIVE.

Field

TransactionSetHeader_TransactionSetControlNumber

Orderful Transaction Set Control Number

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

Field

BeginningSegmentForPurchaseOrder_TransactionSetPurposeCode

Orderful Transaction Set Purpose Code

Purpose of the order; 00 means Original.

Lookup

Lookup Translation: Orderful Transaction Status To iPaaS

Status

Converts the Orderful transaction status to the iPaaS.com transaction status.

Dynamic Formula

Sum of line quantity times unit price

Subtotal

The subtotal, computed across the line items.

Dynamic Formula

iPaaS.com subscription

SystemId

The subscription that owns the transaction.

Dynamic Formula

Sum of line quantity times unit price

Total

The total, computed across the line items.

Dynamic Formula

Sum of line quantity

TotalQty

The total quantity, computed across the line items.

Dynamic Formula

Acknowledgement transaction number

TransactionNumber

The transaction number, stored for visibility and fallback matching. The Orderful transaction ID is the external-ID link.

Static

"Hold"

Type

Sets the iPaaS.com transaction type to Hold.

The Orderful Transaction Status To iPaaS lookup translation maps each Orderful transaction status to the corresponding iPaaS.com transaction status; the value pairs are maintained in that translation collection.

Add Orderful Purchase Order Acknowledgement Address TO iPaaS.com

The addresses on the acknowledgement. Each address links to the parent transaction by a composite external ID made of the entity identifier code and the parent transaction ID (for example, ST then 4).

Mapping Type

Source Field (Orderful)

Destination Field (iPaaS.com)

Description

Field

AddressInformation

Address1

The first line of the address.

Field

CityName

City

The city of the address.

Field

Name

FirstName

The party name on the address.

Dynamic Formula

Entity identifier code

IsPrimaryBilling

Marks the billing address; BT means Bill To.

Dynamic Formula

Entity identifier code

IsPrimaryShipping

Marks the shipping address; ST means Ship To.

Field

EntityIdentifierCode

Orderful Entity Identifier Code

The address role; for example BT, ST, BY.

Field

PostalCode

PostalCode

The postal code of the address.

Field

StateOrProvinceCode

Region

The two-character state or province code.

Add Orderful Purchase Order Acknowledgement Line TO iPaaS.com

The line items on the acknowledgement. Each line links to the parent transaction by a composite external ID made of the line number and the parent transaction ID (for example, 1 then 4).

Mapping Type

Source Field (Orderful)

Destination Field (iPaaS.com)

Description

Field

Description

Description

A free-form product description.

Dynamic Formula

Quantity times unit price

ExtendedPrice

The extended price for the line.

Field

AssignedIdentification

Orderful Assigned Identification

The line number of the item.

Field

ItemDescriptionTypeCode

Orderful Item Description Code Type

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

Field

ProductServiceID

Orderful Product Service ID

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

Field

ProductServiceID1

Orderful Product Service ID 1

The second product/service identifier value (PO107).

Field

ProductServiceIDQualifier

Orderful Product Service ID Qualifier

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

Field

ProductServiceIDQualifier1

Orderful Product Service ID Qualifier 1

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

Field

UnitOrBasisForMeasurementCode

Orderful Unit

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

Field

Quantity

Qty

The quantity acknowledged.

Field

ProductServiceID

Sku

The product/service identifier used as the line SKU (PO105).

Static

"Pending"

Status

Sets each line's status to Pending.

Static

"Product"

Type

Sets each line's type to Product.

Field

UnitPrice

UnitPrice

The price of the item for the unit of measure.

Error Handling

See the Orderful Error Messages article for the full catalog. This inbound flow surfaces "The Transaction Type is not valid" when the returned transaction is empty or unsupported — resolution: confirm the transaction type is supported and the transaction ID exists in Orderful.

Testing & Validation

Test Scenarios

  1. Sync an Orderful acknowledgement by its transaction ID and verify the iPaaS.com transaction is created with type Hold, its addresses, and line items.

  2. Verify the acknowledgement status (APPROVED or REJECTED) is recorded.

  3. Re-sync an updated acknowledgement and verify children match by their composite keys rather than duplicating.

Validation Checklist

  • The acknowledgement header, addresses, and line items transfer.

  • The transaction type is set to Hold and the acknowledgement status is recorded.

  • The Orderful transaction ID is the external ID.

Related Documents

Did this answer your question?