Summary

This mapping collection brings the locations maintained in NCR Counterpoint — stores and warehouses — into iPaaS.com. It carries the location's own identifier and its readable description.

ID Format

Manual Sync id: the Counterpoint location id — this collection reads inbound from Counterpoint, so the id entered on the Manual Sync page is the location's Counterpoint-side identifier, not an iPaaS.com value.
External ID saved after transfer: once a location has been transferred, iPaaS.com records the Counterpoint location id as the external ID on a dedicated platform-managed external-ID record. That record — not any field on the location record itself — is the primary match that routes a subsequent transfer of the same location to an update rather than adding it a second time. The Name mapping also writes the Counterpoint location id onto the iPaaS.com location, which gives subscribers visibility of the location in both systems and serves as a fallback collision key where no external-ID record exists yet. Remapping Name to a different source is supported but disables that fallback link for any pre-existing iPaaS.com locations.

Deleted Record Support

This family does not itself carry deletions. Where a separate Delete collection exists for this entity it handles removals from Counterpoint to iPaaS.com; otherwise a removal in Counterpoint is not propagated. See NCR Counterpoint Known Limitations.

Mapping Collection Status

Status: Enabled. No mapping filter is applied.
Trigger Events: see Transfer Methods in the collection description; automatic transfers require the relevant Outbound/Inbound Data Flow subscriptions to be enabled.

System Caveats

NCR Counterpoint Caveats

Descriptions arrive populated and short: Counterpoint holds the location description as text of up to 30 characters and requires it to be populated, so a description always arrives and is never longer than 30 characters. Subscribers replacing this mapping with a formula are not held to that limit by iPaaS.com, but should keep results short enough to stay readable alongside descriptions that came straight from Counterpoint.

Integration Flow

No records are transferred as prerequisites for this collection. The records it references are expected to exist already.
The record is sent to iPaaS.com, where subsequent transfers are routed by the external ID recorded on transfer.

Mappings

Add/Update NCR Counterpoint Location TO iPaaS.com

Mapping Type	Source Field (NCR Counterpoint)	Destination Field (iPaaS.com)	Description
Field	`LOC_ID`	Name	Required. IPaaS.com rejects the location without it.
Field	`DESCR`	Description	Optional. .

Name — Field

Source: LOC_ID · Destination: Name

This is a required field — iPaaS.com rejects the location without it. The location's own identifier in NCR Counterpoint, carried across unchanged and used as the location's name in iPaaS.com.

This is the code subscribers or their MiSP see against the location in Counterpoint, not a longer label — the readable label travels on Description. Counterpoint always supplies it, because it is the location's key.

This value is what other collections match on when they need to attach something to a location. The Add/Update NCR Counterpoint Location Group TO iPaaS.com collection resolves its member locations by looking up locations already transferred by this collection, and the inventory collections attach stock to a location the same way. Locations should therefore transfer before location groups and before inventory.

Description — Field

Source: DESCR · Destination: Description

This is an optional field. The location's readable description as maintained in NCR Counterpoint — typically the store or warehouse name — carried across unchanged. It is the label subscribers recognize where Name carries only the code.

Counterpoint stores this as text of up to 30 characters and requires it to be populated, so a description always arrives and is never longer than 30 characters. Subscribers replacing this mapping with a formula are not held to that limit by iPaaS.com, but should keep results short enough to stay readable alongside descriptions that came straight from Counterpoint.

This collection transfers the location's identity only. Counterpoint holds address and contact details against the location as well, and iPaaS.com can store them, but no mapping in this collection carries them. Subscribers or their MiSP who need location addresses in iPaaS.com should add mappings for them.

Error Handling

Errors raised while transferring these records surface at Dashboard / Integration Monitoring / Error Logs. The specific messages, their causes and their resolutions are documented in NCR Counterpoint Error Messages. A record stopped by an error is not retried automatically; it must be resolved manually.

Testing & Validation

Replace every placeholder value called out above with one from the target Counterpoint installation, and confirm each exists in Counterpoint.
Transfer a single record through Manual Sync and confirm it appears in Counterpoint as expected.
Confirm any child records transferred with the parent.
Enable the relevant triggers and confirm a new record transfers automatically, and that a change updates the same Counterpoint record rather than creating a second one.
Attempt a transfer with a missing required field and confirm the expected error appears at Dashboard / Integration Monitoring / Error Logs.

NCR Counterpoint to iPaaS.com Location Mapping Documentation