ION Factory OS
  • Welcome to ION
  • Features
    • Procedures
      • Steps
        • Content
        • Datagrid
        • Fields
        • Attributes
      • Dependencies
      • Part-Procedure Relationship
      • Attributes
      • Standard Steps
      • Installation Requirements (Beta)
      • Nested Steps and Nested Standard Steps
      • Procedure Best Practices
    • Runs
      • Run Execution Overview
      • Runs And Step States
      • Batching Runs
        • Batching 2.0 Changes
      • Workcenter execution
      • Split Inventory on a Run
      • Redlines
      • Export run data
      • Scheduling runs
      • Time Tracking
      • Attributes
      • Outside Processing
      • Runs Best Practices
    • Parts Library
      • As-built Bill of Materials (aBOM)
        • Editing aBOM build requirements
        • aBOM Beta Changes
          • aBOM actions for developers
      • Inventory
        • Inventory status
        • Inventory splitting
        • Inventory merging
        • Inventory scrapping
        • Kitting
        • Inventory Movement Automations
      • Manufacturing bill of materials (mBOM)
        • mBOM versions
        • Made on Assembly (MOA)
        • Part Substitutes
        • Reference designators
      • Part Attributes
      • Part revision interchangeability
      • Supplier Part Numbers & Purchase Unit Conversions
    • Kitting and Inventory Fulfilment
      • Kit Statuses and Workflows
      • Inventory requests
      • Kitting and runs
      • Fulfilling Multiple Kits
      • Kanban Kitting
    • Purchasing
      • Purchase Orders
        • Types of Purchases
        • Purchase Order Approvals
        • Purchase Order FAQs
        • Supplier Part Numbers & Unit Conversions
        • PO Requirements, Terms, and Quality Clauses
      • Receiving/Inspection
      • Outside Processing
      • Consigned Parts
    • Barcode Labels
      • Templating
        • ION barcode minimum sizes
        • Sample templates
      • Printing
        • Configuring Zebra Browser Print
        • Server Based Barcode Printing (PrintNode)
      • Scanning
        • Scan barcodes from other systems
    • Quality
      • Issues
      • Further Actions - CAPA
      • Issues States, Dispositions, and Resolutions
      • Quality Best Practices
    • Tools
    • Locations
    • Attributes
    • Labels
      • Deleting labels
    • Notifications
    • Search
    • Settings
      • Role based access control
        • Full Glossary of ION Permissions
    • ION Actions
      • ION Actions examples for Quality
      • ION Actions examples for Runs and Procedures
      • ION ACTIONS examples for Supply Chain
  • Analytics
    • Inventory valuation
    • Part impact analysis
    • Users, Roles, Teams
    • Analytics FAQ
    • Data Connector
    • Data Products
  • Plans and Autoplan
    • Autoplan
    • Autoplan glossary
    • Preparing to use Autoplan
    • Clear to build reporting
    • Running Autoplan on a schedule
    • Firm and blocked plan items
    • Location constraints
    • Autoplan suggested suppliers and procedures
    • Reorder point
    • Plan input serial numbers
    • Applying a calendar
    • Plan Reservations
    • Independent schedules
    • Drive demand from kits
    • Drive demand below buy parts configuration
    • Group plan items with the same date
    • Manualy Changing Autoplan Status
  • API
    • How to create an App with ION
    • Access Tokens
    • About GraphQL
    • Interactive API explorer
    • API Keys
    • Examples
      • Notifications
      • Runs
      • Automatically updating fields in runs
      • Parts and Part Revisioning
      • mBOMs
      • Part Inventory and Kitting
      • aBOM (As-built Bill of Materials)
      • Edit time-tracking session data
    • Changelog
    • Webhooks
    • Pagination
  • Automations
    • Auto-checkout of Run Steps
    • Auto-Consumption of Lineside Inventory
    • Automatically Send Purchases to Suppliers
    • Set Close by Run Step on Issue Creation
    • Intent Management / Grade / Tier / Pedigree
      • Data Imprinting
      • ION Actions for Intent
    • Auto-Update mBOM Revision on Part Revision Update
    • Auto-approve part-procedure relationships
    • Purchase Order PDF and Versions
    • Auto Populate PO Line Attributes
    • Imprint Attributes from One Object to Another on a Desired Event
  • Integrations
    • Deploying Integrations and Automations
    • Arena
    • Cofactr
    • Datum
    • Duro
    • NetSuite
      • Purchasing in NetSuite, Receiving in ION
      • Work Order/Assembly Builds
    • Procurable
    • PDF Generator
    • Quickbooks
    • Ramp
    • Silkline Integration
    • Slack
    • Smartsheet
    • SOLIDWORKS
    • Teamcenter
  • Training
    • Standard Operating Procedures
      • Cycle Counting
      • Tool Utilization
    • Guided Flows
    • ION Sandbox
    • Chat Support for ION
  • Troubleshooting
    • Resetting your password
    • Resetting your Multi-Factor Authentication
    • You have no roles... error
  • Changelog
  • Adminstration
    • Security
      • Backups and Security FAQ
      • Single Sign-On (SSO)
        • Okta SAML connection setup
      • Export Control
      • Report Generator Disclaimer
    • Browser and Device Compatibility
    • Authentication
      • My company is new to ION, logging in for the first time.
      • I'm told I'm not authorized to access the application
      • My account has been deactivated
    • Login Page
  • Tickets Portal
Powered by GitBook
On this page
  • Overview
  • Key Capabilities
  • How It Works
  • Best Practices for Using This Feature

Was this helpful?

  1. Automations

Auto Populate PO Line Attributes

Overview

The Purchase Order (PO) Attribute Propagation automation available in the ION marketplace streamlines the management of attributes between the PO level and the PO line level. This automation significantly enhances procurement efficiency by reducing repetitive data entry, maintaining attribute consistency, and allowing flexibility where needed.

Key Capabilities

  • Automated Propagation: Automatically copies values from PO header attributes to PO line attributes who's keys are an exact match.

  • Line-Level Customization: Allows users to override propagated values on individual PO lines.

  • Accommodate to New PO Line Items: Applies updates dynamically when new PO line items are created so they reflect the setup of header attributes.

How It Works

Triggers & Conditions

The automation activates under the following conditions:

  1. On PO Line Item Creation:

    • Copies Need Date and ETA from a specified PO header attribute to new PO line native fields "Need Date" and "Parts ETA Date ".

    • Copies custom attributes if matching keys exist between the PO header and PO line.

  2. On PO Attribute Updates (Need Date, ETA, or Custom Attributes):

    • Updates all PO line items with the new values.

    • If the updated PO attribute does not exist at the PO line level, the automation does not execute.

Flow

Setup

This automation allows you to map date-time attributes at the PO level to the native PO Line fields "Need Date" and "Parts ETA Date." During configuration, you can specify which PO attribute keys to map.

If you do not want to automate the population of "Need Date" and "Parts ETA Date" on the PO line, retain the default options during configuration and select "Finish."

Error Handling

  • If an attribute exists at the PO header but not at the PO line level, the automation does not attempt a copy-down. As such your attributes within IONs organizational settings must be an exact match for the copy to work.

Best Practices for Using This Feature

  • Be aware that any updates to attributes at the PO header level will be applied to all PO line items. Ensure team members understand the automated propagation mechanics to avoid unintended data changes.

PreviousPurchase Order PDF and VersionsNextImprint Attributes from One Object to Another on a Desired Event

Last updated 3 months ago

Was this helpful?

The being referenced for this automation can be found on ION's Organization Settings page under the Purchase Orders tab. Scroll within this tab to view both Purchase Order and Purchase Order Line attributes.

In order to setup this automation refer to the documentation for generic instructions.

attributes
Deploying Automations and Integrations
Automation Specific Setup With Default Values