Flxpoint Knowledge

Contact us

McKesson as Source

Table of Contents

How To Connect Product Operations Order Operation

McKesson is a leading supplier of medical and healthcare products. Flxpoint integration automates inventory synchronization and fulfillment.

 

How To Connect

📋 Phase 1: Create Your McKesson Source +
Create Source in Flxpoint
Go to Sources → + Add Source. Name it “McKesson”. Select Vendor Warehouse as the Source Type, then assign a vendor (recommended).
Add the Integration
On the Source page, click Start Creating Integrations under Get Inventory [Primary]. This is where you’ll set up your McKesson EDI connection.
Tip: Start with inventory. You can add Send Fulfillment Requests, Get Shipments, and Invoices later.
🔐 Phase 2: Get Your McKesson Credentials +
Where to Find Credentials
McKesson provides EDI credentials through their B2B team. Reach out to your McKesson account manager or EDI Onboarding team and request credentials for your integration. They will provide:
  • B2B Key
  • Identity
  • Shared Secret
  • Account Number
  • Ship To Number
Pro Tip: Ask McKesson to confirm that your account is enabled for Inventory (846) feeds and Order Fulfillment (850/856) if you plan to send orders.
Enter Credentials
In Step 1 of Get Inventory [Primary], click + New Connection. Enter the credentials exactly as provided by McKesson. Then click Test Connection → Save Connection.
⚙️ Phase 3: Configure Settings +
Set Preferences
In Step 2 (Configure Settings):
  • Choose Image Quality Preference (High Res recommended).
  • Enable Archive/Un-Archive Inventory if you want items missing from McKesson’s feed to automatically deactivate/reactivate.
Note: Only enable Archive/Un-Archive once per source (Primary or Secondary) to avoid conflicts.
✅ Phase 4: Mapping & Activation +
Define a Mapping Template
In Step 3, select or create a template (e.g., Get Inventory [Primary]). Map required fields such as SKU, Quantity, Price, and product details.
Save and Run
Click Save and Complete. From the integration overview, you can run the job manually or set up a recurring schedule to keep inventory updated.
Verify: After your first run, check a few SKUs against McKesson’s portal to confirm data accuracy.


Product Operations

Get Inventory (Primary) 

Supported | McKesson (EDI)

Introduction — Get Inventory [Primary] (McKesson)
This integration retrieves the McKesson catalog (products, pricing, quantities, images, categories, attributes) from the McKesson XML API and maps it into your Source Inventory. Use it to keep availability and product details current.

The McKesson Get Inventory [Primary] integration enables you to:
  • Download the full McKesson item catalog in pages and ingest on-hand Quantity per UOM.
  • Import pricing and key identifiers (Item Id, Brand/Manufacturer, Categories).
  • Pull images using your selected Image Quality Preference (High Res, Item Detail, or Thumbnail).

  • 1 Connect & Configure: Create a connection with B2B Key, Identity, Shared Secret, Account, and Ship To. Use Test Connection and then Save Connection.
  • 2 Configure Settings: Choose an Image Quality Preference and set Archive/Un-Archive Inventory behavior.
  • 3 Define a Mapping Template: Select or create your template under Get Source Products and map McKesson fields.
  • 4 Run or Schedule: From the Configure page, toggle Scheduled or click Run Integration to start the import.
Tip: If you also run a Secondary job for this source, enable Archive/Un-Archive in only one job to prevent unexpected archiving.

Connection Fields
Field Description Notes
B2B Key Unique key to build the request URL. Used in the feed URL path.
Identity Identity/username for API auth. Provided by McKesson.
Shared Secret Password/shared secret. Provided by McKesson.
Account Account number to fetch data for. Required.
Ship To Ship-to identifier for the account. Required.
Settings
Setting Options Default What it does
Image Quality Preference high_res, item_detail, thumbnail high_res Controls the base image URL used for building product image links.
Archive/Un-Archive Inventory Yes / No No Archives items not present in the latest feed; restores them when they reappear.
Image Quality is selectable on the Configure step. The default is High Res.

Interface Overview
  • Screen labeled Get Source Products; actions: Delete, Duplicate, Save.
  • Layout: From Value (McKesson Item & McKesson Item UOM) → To Inventory Parent/Variant Field.
Core Parent Mappings (Recommended)
McKesson Field Maps To Example Notes
itemId Parent SKU MK-123456 Main product identifier.
description or itemDescription Title Acetaminophen 500mg Choose the preferred title source.
itemFeatures Description Capsule; Pain Relief; 100 ct Multi-line features become body text.
manufacturerName or itemBrand Brand McKesson Brand Either field is acceptable.
majorCategory Category 1 OTC Top-level category from feed.
minorCategory Category 2 Pain Relief Second-level category.
itemImage + image refs (see below) All Images — Primary from itemImage; additional refs from attributes.
itemAttributes All Attributes UPC, dosage, size… Direct-copy key/value pairs.
Variant (UOM) Mappings
McKesson UOM Field Maps To Example Notes
itemSku SKU MK-123456-CS Variant SKU is typically itemId-units (e.g., PK, CS).
price Cost 12.75 Numeric cost for the UOM.
quantityAvailable Quantity 42 Current stock for the UOM.
(derived from itemAttributes) UPC 012345678905 Populate via a generic rule that looks up the UPC in attributes.
itemImage + image refs Images — Variants inherit parent image set.
units Option Value PK Option Name: UOM; Value from units.
Images
Images are constructed from a base URL determined by your Image Quality Preference and the feed fields:
// Primary
<base-from-image_quality_pref>/{itemImage}

// Additional
For each attribute where name starts with Image Reference Number, append the value to the same base URL.
Note: Each Item can contain multiple Units of Measure (UOM). Each UOM becomes a distinct variant in your Source Inventory.

  • Feed Source: https://mms.mckesson.com/services/xml/{b2b_key}/ItemFeed
  • Pagination: Items are fetched in pages of 50.
  • Parsing & Mapping: Raw XML is transformed into SourceProductDto and SourceVariantDto objects.
  • Save: Batches are saved to the database as they are processed.

Capability Status Notes
Custom Fields NOT SUPPORTED Attributes are saved as direct-copy.
Variations / Options SUPPORTED Variants created per UOM.
Generic Pricing (& Currency) SUPPORTED Single price per UOM.
Client-Specific Pricing NOT SUPPORTED Feed does not include per-client pricing.
Quantity SUPPORTED Uses quantityAvailable.
Multiple Warehouses NOT SUPPORTED No warehouse breakdown in the item feed.
Weights & Dimensions (& Units) SUPPORTED If present, units are normalized.
Images SUPPORTED Primary & additional via image references.
Categories SUPPORTED Two-level categories available.
Delta vs Full Feed FULL FEED Pages of 50 until all items are retrieved.
Archive Support SUPPORTED Use the Archive/Un-Archive toggle in config.

  • 1 Add the Integration: Source ➜ McKesson (EDI) ➜ Get Inventory [Primary].
  • 2 Create Connection: Enter Connection Name, B2B Key, Identity, Shared Secret, Account, Ship To ➜ Test Connection ➜ Save Connection.
  • 3 Configure: Set Image Quality Preference and choose whether to Archive/Un-Archive inventory.
  • 4 Mapping Template: Choose or create Get Inventory [Primary] 1 and map core fields (see tables above).
  • 5 Automate: On the Configure page, toggle Scheduled to Yes or click Run Integration for an on-demand import.

  • Auth failures: Re-check Identity/Shared Secret and verify the B2B Key is correct for the intended account/ship-to.
  • Empty results: Confirm the account and ship-to are authorized for the item feed and that the B2B key matches.
  • Images not showing: Ensure your Image Quality Preference is set and your mapping builds the correct base URL.
  • Unexpected archiving: If both Primary and Secondary jobs have archiving enabled, disable it in one of them.
  • UPC missing: Add a generic rule to extract UPC from itemAttributes when not provided directly.
Diagnostic Tip: Use Post Mapping Workflow in Draft to test enrichment rules before enabling them Live.

  • Feed URL: https://mms.mckesson.com/services/xml/{b2b_key}/ItemFeed
  • UOM ➜ Variants: Each UOM creates a separate variant; option name is UOM, value from units.
  • Titles: Many teams prefer description as the title; others choose itemDescription. Pick one for consistency.
  • Scheduling: Choose a cadence that keeps quantity fresh without overloading rate limits.
Pro Tip: Include UPC, Brand, and both category levels in your mapping template for better downstream matching.

Conclusion
McKesson Get Inventory [Primary] keeps your product catalog up to date through the XML item feed. Connect with valid credentials, map the recommended fields, and schedule the job for continuous updates.
 
 

Get Inventory (Secondary) 

Supported | McKesson (EDI)

Introduction — Get Inventory [Secondary] (McKesson)
This Secondary integration updates inventory variants (UOMs) using the live McKesson XML ItemFeed. It focuses on quantity and price refreshes and can optionally create missing variants.

Use McKesson Get Inventory [Secondary] to:
  • Refresh Quantity Available and Price per UOM frequently.
  • Keep existing Source Variants in sync with McKesson’s availability feed.
  • Optionally create new variants on the fly with Allow Create Variant.

  • 1 Connect & Verify: Add credentials (B2B Key, Identity, Shared Secret, Account, Ship To) and run Test Connection.
  • 2 Configure: Toggle Archive/Un-Archive Inventory and, under Advanced Settings, decide whether to Allow Create Variant.
  • 3 Define a Mapping Template: Select Get Inventory [Secondary] and map McKesson UOM fields to Variant fields.
  • 4 Run or Schedule: From the Configure page, click Run Integration or enable Scheduled for recurring updates.
Tip: If you also run a Primary job for McKesson, enable Archive/Un-Archive in only one job to avoid flip‑flopping item states.

Connection Fields
Field Description Default
b2b_key B2B key used in the endpoint path. None
identity API identity/username. None
shared_secret Password/shared secret for auth. None
account McKesson account number. None
ship_to Ship‑to identifier linked to the account. None
Settings
Setting Options Default What it does
Archive/Un‑Archive Inventory Yes / No No Archives items missing in the latest feed; restores when they reappear.
Allow Create Variant Yes / No No When Yes, variants that don’t exist yet can be created during the run.

Interface Overview
  • Screen labeled Get Inventory [Secondary]; actions: Delete, Duplicate, Save.
  • Layout: From Value (McKesson Item UOM) → To Inventory Variant Field.
Core Variant Mappings
McKesson UOM Field Maps To Processing Logic / Notes
ItemOut.itemId + ItemUom.units SKU A unique SKU is built as {itemId}-{units} (e.g., 123456-EA).
ItemUom.quantityAvailable Quantity Direct Map. Current stock for the specific SKU.
ItemUom.price.value Cost Direct Map. Price for the specific unit of measure.
— MSRP Optional. Not provided by the availability feed; usually left unmapped.
The mapping UI exposes variant fields such as Item SKU, Price, Quantity Available from McKesson Item UOM on the left, mapped to SKU, Cost, Quantity on the right.

Data Flow Summary
  1. Connect & Verify ➜ Test API credentials.
  2. Fetch Data in Batches ➜ Pages of up to 50 items.
  3. Parse & Process ➜ Iterate each item's UOMs.
  4. Map to Standard Format ➜ Transform to SourceVariantDto.
  5. Save to Database ➜ Batch save after each page.
Data Source (Feed)
Feed Location Format Purpose
McKesson ItemFeed API https://mms.mckesson.com/services/xml/{b2b_key}/ItemFeed XML Live “availability” view: stock levels, pricing, status per UOM.

Capability Status Notes
Creates Parent Products NO Secondary focuses on variants only.
Create Variants OPTIONAL Enable Allow Create Variant.
Price & Quantity SUPPORTED Direct map from UOM feed.
Images / Attributes NOT INCLUDED Use Primary for full catalog + images.
Pagination 50 / page Processes and saves by page.
Archive Support SUPPORTED Use the Archive/Un‑Archive toggle in config.

  • 1 Add the Integration: Source ➜ McKesson (EDI) ➜ Get Inventory [Secondary].
  • 2 Create Connection: Enter credentials ➜ Test Connection ➜ Save Connection.
  • 3 Configure Settings: Decide on archiving and whether to allow creating variants.
  • 4 Mapping Template: Choose or create Get Inventory [Secondary] and map SKU, Quantity, and Cost.
  • 5 Automate: Enable Scheduled or use Run Integration for ad‑hoc updates.

  • No quantity updates: Ensure the mapping points to ItemUom.quantityAvailable and the template is selected on Configure.
  • Unexpected archiving: Only one of Primary/Secondary should manage archiving.
  • Variants missing: Enable Allow Create Variant or pre‑seed variants via Primary.
  • Pricing looks off: Confirm you mapped ItemUom.price.value to Cost and that currency assumptions match.

Conclusion
McKesson Get Inventory [Secondary] is the lightweight, high‑cadence updater for UOM‑level stock and price. Pair it with Primary for full‑catalog enrichment.
 
 

 

Order Operation

Send Fulfillment Requests

Supported | McKesson (EDI)

Introduction — Send Fulfillment Requests
Use this integration to transmit Fulfillment Requests (FRs) to McKesson over EDI via FTP/FTPS. It packages your order and line items into McKesson’s expected fields (e.g., Patient Account Number, ShipTo Number, Buyer's Item Number (IN), Quantity, and Unit Measurement Code) and drops the outbound file on McKesson’s FTP. Optionally, it can hold requests for review and send only during business hours.

The McKesson Send Fulfillment Requests integration enables you to:
  • Connect to McKesson’s EDI FTP endpoint and authenticate.
  • Place outbound files into the Outbound Remote File Folder and (optionally) retrieve inbound responses from the Inbound Remote File Folder.
  • Map your order and item fields—SKU, Quantity, UOM, Cost—to McKesson’s order format.
  • Control when requests are sent (hold X hours, business-hours only).

  • 1 Connect: Create an FTP/FTPS connection by entering Host, Port, User, and Password. Advanced options include maintaining a constant connection and using an unbuffered private data channel for certain FTPS servers.
  • 2 Configure: Provide remote folders and EDI identifiers (qualifier + ID for both sender and receiver), along with your McKesson Customer Account Number. Optionally set a hold period and business-hours only sending.
  • 3 Map: Choose or create the Send Fulfillment Requests mapping template and map order-level and item-level fields (see tables below).
  • 4 Run or Schedule: Save and complete the setup, then send requests manually or on an automated cadence.
Tip: If you set ShipTo Number the address will not be sent with the order (per McKesson’s expectations for coded ship-to locations).

Field Description Notes
FTP Protocol Protocol for file transport (FTP / FTPS). Use FTPS if required by McKesson security.
FTP Host Server hostname provided by McKesson. e.g., ftp.mckesson.com (example).
FTP Port Port for the selected protocol. 21 for FTP; FTPS may vary.
FTP User Username issued for your account. Required.
FTP Password Password for the above user. Required.
Maintain Constant Connection Keeps a persistent connection across transfers. Default behavior reconnects between batches.
Use Unbuffered Private Data Channel Troubleshooting option for FTPS servers that return policy/SSL errors. Use only when needed.

Config What it is Guidance
Outbound Remote File Folder Remote path where the FR files are deposited. Provided by McKesson.
Inbound Remote File Folder Remote path to pull any inbound responses/files. Optional, per your setup.
Our Sender/Receiver Qualifier ISA qualifier for your (Flxpoint) EDI ID. Typically “ZZ” (mutually defined) or “01” (DUNS).
Our Sender/Receiver ID Your ISA identifier for EDI. Matches the above qualifier.
Their Sender/Receiver Qualifier McKesson’s ISA qualifier. Typically “ZZ” or “01”.
Their Sender/Receiver ID McKesson’s ISA identifier. Provided during onboarding.
Customer Account Number Your McKesson customer account number. Required.
Hold for X Hours Delays sending for the specified hours. Useful for manual review prior to send.
Only Send During Business Hours Restricts sending to normal business hours. Optional; reduces after-hours transmissions.

Interface Overview
  • Screen labeled Send Fulfillment Requests; actions: Delete, Duplicate, Save.
  • Layout: From Value (your Order / FR Item fields) → To McKesson Order / Order Item Field.
Order-Level (Header) Mappings
Your Field Maps To Notes
Order Number (or unique ID) Patient Account Number Must be unique; values cannot repeat.
Ship-To Code ShipTo Number If set, the ship-to address will not be sent.
Item-Level Mappings
Your Field Maps To Example Notes
SKU Buyer’s Item Number (IN) 123456-EA Primary item identifier McKesson expects.
Quantity Quantity 2 Units to ship for the selected UOM.
Unit of Measure Unit Measurement Code EA, BX, CS Send a valid UOM code supported by McKesson.
Cost (optional) Cost 9.99 Include if required for your workflow.
The mapping UI exposes Patient Account Number, ShipTo Number, and item fields like Buyer’s Item Number (IN), Quantity, Unit Measurement Code, and Cost under the Send Fulfillment Requests template.
Tip: Validate your template with a small test order before going live.

  • 1 Add Integration: Source ➜ McKesson (EDI) ➜ Send Fulfillment Requests.
  • 2 Create Connection: Enter FTP details ➜ Test Connection ➜ Save Connection.
  • 3 Configure: Fill in folders, qualifiers/IDs, and your McKesson Customer Account Number. Optionally set hold hours and business-hours only.
  • 4 Mapping Template: Choose or create Send Fulfillment Requests 1; map header + line fields as above.
  • 5 Automate or Run: Save and complete, then run manually or enable scheduling.

  • FTP auth/connection errors: Re-test with the correct protocol (FTP vs FTPS), host, and port. Toggle the Unbuffered Private Data Channel only for specific FTPS policy errors.
  • Files not showing at McKesson: Confirm the exact remote folder paths and credentials. Verify the job ran and has access permissions.
  • Rejected orders: Ensure Patient Account Number is unique and Buyer’s Item Number (IN), Quantity, and UOM are mapped.
  • Ship-to address missing: If you set ShipTo Number, the address is intentionally omitted.
Diagnostic Tip: Start by sending a single order with one line, check the remote outbound directory, then scale up.

  • Identifiers: Qualifiers are commonly ZZ (mutually defined) or 01 (DUNS).
  • Uniqueness: Patient Account Number must be unique per order.
  • UOM: Send valid codes (e.g., EA, BX, CS) that match McKesson’s item/UOM setup.
  • Scheduling: Use Hold for X Hours and Only send during business hours to manage timing.

Conclusion
The McKesson (EDI) Send Fulfillment Requests integration lets you securely send FRs to McKesson and control timing and mapping with a predictable, repeatable workflow.
 
 

Get Shipments

Supported | McKesson (EDI)

Introduction — Get Shipments
This integration retrieves shipment confirmations from McKesson via 856 EDI downloaded from your configured inbound FTP directory, maps them to Flxpoint shipments, and (on success) posts a 997 functional acknowledgment back to the configured outbound directory.

Use Get Shipments to automatically:
  • Poll McKesson’s FTP for new 856 files and parse shipment details.
  • Attach tracking (including multiple tracking numbers) to the related Fulfillment Requests (FRs) / orders.
  • Send back a 997 acknowledgment after a successful import.

  • 1 Connect: Create an EDI FTP connection with your McKesson FTP host, port, user, and password.
  • 2 Configure: Provide Outbound/Inbound remote directories, your Customer Account Number, and both parties’ ISA Qualifiers and IDs. Choose the FR Lookback Period (default 3 months) to match shipments to recent FRs.
  • 3 Map: In the Get Shipments mapping template, map the line item identifier from McKesson Shipment Item → Buyer’s Item Number (IN) to the Flxpoint SKU. You may also use vendorItemNumber depending on your catalog.
  • 4 Run / Schedule: Save and Complete, then run manually or enable scheduling from the Configure screen.
Tip: If your items use vendor item numbers rather than SKUs, switch the mapping to vendorItemNumber to ensure proper line-level matching.

Config What it is Guidance
Outbound Remote File Folder Where the system uploads the 997 acknowledgment. Provided by McKesson.
Inbound Remote File Folder Where the job reads inbound 856 files. Provided by McKesson.
Customer Account Number Your McKesson customer account number. Required to associate shipments.
Our Sender/Receiver ID & Qualifier Your EDI ISA identifier + qualifier. Qualifier is typically “ZZ” (mutually defined) or “01” (DUNS).
Their Sender/Receiver ID & Qualifier McKesson’s EDI ISA identifier + qualifier. Provided during onboarding.
FR Lookback Period for Get Shipments How far back to search for matching FRs. Default is 3 months (≈90 days).

Interface Overview
  • Screen labeled Get Shipments; actions: Delete, Duplicate, Save.
  • Layout: From Value (McKesson Shipment Item) → To Shipment Item Field.
Core Line Mapping
McKesson Field Maps To Notes
Buyer’s Item Number (IN) SKU Use this or vendorItemNumber for line matching.
Operation Workflow
  • Reads 856 EDI files from the inbound directory.
  • Purchase Order Number is read from PRF01 (e.g., PRF*49527293-4~).
  • Line item match can use either sku or vendorItemNumber based on your mapping.
  • When multiple tracking numbers are present, they are stored as a comma‑separated value.
  • On successful processing, a 997 is uploaded to the outbound directory.

Overview

McKesson sends 856 EDI files to provide shipment info. Flxpoint now supports multiple tracking numbers per shipment.

New Behavior
  • If an 856 contains more than one tracking number, Flxpoint stores all of them.
  • Tracking values appear in the shipment record as a comma‑separated list.
  • No UI changes required; values appear in the existing tracking field.
  • Improves visibility when shipments are split across carriers/packages.
Example
EDI input: 123456789, 987654321
Shipment record: 123456789, 987654321
Limitations / Notes
  • Multiple tracking numbers are associated with a single shipment record.
  • No changes required to order flows or UI usage.
  • Verified in production (AID #3170, Order #19280409).
Related Enhancements
  • INT‑47739 — Add multiple tracking number support.
  • INT‑48469 — Confirm expected behavior for McKesson 856 EDI files.

Capability Status Notes
Inbound Format EDI 856 Read from inbound FTP directory.
Outbound Ack EDI 997 Uploaded to outbound directory after success.
Tracking Numbers Multiple Stored comma‑separated when 856 includes more than one.
Line Matching SKU or Vendor Item # Configure via mapping template.
Lookback Configurable Default 3 months (90 days).

  • 1 Add Integration: Source ➜ McKesson (EDI) ➜ Get Shipments.
  • 2 Create Connection: Enter FTP details and save.
  • 3 Configure: Folders, account number, EDI IDs/qualifiers, and lookback period.
  • 4 Mapping Template: Map Buyer’s Item Number (IN) → SKU (or vendorItemNumber).
  • 5 Automate / Run: Save and Complete, then enable scheduling or run on demand.

  • No shipments created: Verify inbound directory path and that 856 files exist; confirm lookback window covers the FR’s create date.
  • Lines not matching: Ensure your mapping uses the correct identifier (Buyer’s Item Number (IN) vs vendorItemNumber).
  • No tracking on shipments: Check the 856 content; when multiple tracking numbers are present they will appear comma‑separated in the tracking field.
  • 997 not posting: Confirm outbound folder permissions and connectivity.
Diagnostic Tip: Test with a single 856 and inspect the created shipment record to confirm PO (PRF01), line match, and tracking values.

Conclusion
The McKesson (EDI) Get Shipments integration automates 856 intake, supports multiple tracking numbers, and closes the loop with a 997 acknowledgment—keeping your orders up‑to‑date with accurate shipment details.
 
 

Get Invoices

Supported | McKesson (EDI)

Introduction — Get Invoices
This integration retrieves 810 EDI invoices from McKesson via your EDI FTP connection, maps them to invoice items, and (on success) uploads a 997 acknowledgment to your outbound directory.

The Get Invoices job allows you to:
  • Download and parse McKesson 810 invoices from the configured inbound folder.
  • Generate invoice line items with SKU, quantity, and per‑unit cost.
  • Post a 997 acknowledgment to the outbound folder after a successful import.

  • 1 Connect: Use your McKesson (EDI) — EDI FTP credentials to create the connection.
  • 2 Configure: Set the Outbound/Inbound remote folders, Customer Account Number, both parties’ ISA IDs and Qualifiers, and the FR Lookback Period for Invoice Processing (default 1 Month / ~30 days).
  • 3 Map: In your Get Fulfillment Request Invoices template, map McKesson invoice fields (see recommendations below).
  • 4 Run / Schedule: Save and Complete, then run on demand or enable scheduling from the Configure screen.
Tip: Align the invoice line SKU mapping with your catalog identifier (Buyer’s Item Number (IN) is typical for McKesson).

Config What it is Guidance
Outbound Remote File Folder Folder where the job uploads the 997 acknowledgment. Provided by McKesson.
Inbound Remote File Folder Folder from which the job reads inbound 810 invoice files. Provided by McKesson.
Customer Account Number Your McKesson customer account number. Required.
Our Sender/Receiver ID & Qualifier Your EDI ISA identifier + qualifier. Qualifier is usually “ZZ” (mutually defined) or “01” (DUNS).
Their Sender/Receiver ID & Qualifier McKesson’s EDI ISA identifier + qualifier. Provided during onboarding.
FR Lookback Period for Invoice Processing How far back the job will search for FRs to invoice against. Default 1 Month (30 days).

Interface Overview
  • Screen labeled Get Fulfillment Request Invoices; actions: Delete, Duplicate, Save.
  • Layout: From Value (McKesson Invoice Item) → To Source Invoice Item Field.
Recommended Line Mappings
McKesson Field Maps To Notes
Buyer’s Item Number (IN) SKU Primary line identifier; align with catalog SKU.
Quantity Quantity Quantity invoiced.
Cost Per Unit Cost Unit price for the line item.
(Constant) Invoice Item Type Set to Product (Option) for standard goods.
(Optional) Title Not required; may be left unmapped.
(—) All Custom Fields Leave unmapped unless you need custom data.

  • Reads 810 EDI files from the inbound directory.
  • Matches invoice lines to items using your mapping (typically Buyer’s Item Number (IN) → SKU).
  • Creates invoice records against eligible FRs within the configured lookback window.
  • On success, uploads a 997 functional acknowledgment to the outbound directory.

Capability Status Notes
Inbound Format EDI 810 Invoice files from McKesson.
Outbound Ack EDI 997 Uploaded after successful import.
Line Matching SKU Usually Buyer’s Item Number (IN) → SKU.
Lookback Configurable Default 1 month (~30 days).

  • 1 Add Integration: Source ➜ McKesson (EDI) ➜ Get Invoices.
  • 2 Create Connection: Enter FTP host, port, user, password ➜ Test ➜ Save.
  • 3 Configure: Set folders, account number, ISA IDs/qualifiers, and the FR lookback period.
  • 4 Mapping Template: Map IN → SKU, Quantity → Quantity, Cost → Per Unit Cost, set Invoice Item Type = Product.
  • 5 Run/Schedule: Save and Complete, then run or schedule.

  • No invoices created: Confirm inbound path and that 810 files are present; verify the FR lookback covers the FR create date.
  • Line mismatch: Ensure the correct identifier is mapped (Buyer’s Item Number (IN) → SKU).
  • Costs missing: Verify Cost is mapped to Per Unit Cost and is present in the 810 file.
  • 997 not sent: Check outbound folder permissions and connectivity.

Conclusion
The McKesson (EDI) Get Invoices integration automates 810 intake, line mapping, and acknowledgment—so your billing stays accurate and in sync with McKesson.
 

Related Articles

FragranceNet as Source

FragranceNet Specializes in fragrances, skincare, and beauty products. Flxpoint i...

Essential Pet Products as Source

Essential Pet Products is a distributor of pet supplies, including toys, food, an...

Entrenue as Source

Entrenue is a wholesale distributor specializing in adult products, boutique plea...