Data entities supported in AWS Supply Chain

Organization

Non-transactional data

company - Entity to store the name and location of your company.

Non-transactional data

geography - Entity stores geographical hierarchy of your company.

Non-transactional data

trading_partner - Contains the partners that have trading relationship with your company, such as vendors, 3PLs, channel partners, or distributors.

Non-transactional data

trading_partner_poc - Contains information that can be identified about the point of contacts at the partners such as vendors, 3PLs, channel partners, or distributors, that have trading relationship with your company.

Product

Non-transactional data

product - Contains the key product attributes, including name, description, brand, codes, category, business group, and price.

Non-transactional data

product_hierarchy - Contains the product categories and sub-categories.

Non-transactional data

product_uom - Contains the product packaging options and conversations between packages.

Non-transactional data

product_alternate - Contains information about alternative products, including type of alternative.

Non-transactional data

un_details - Contains information about hazardous products.

Network

Non-transactional data

site - Stores information for sites holding inventory such as Stores, Distribution Centers ,including ID, name, address, geographical region, and site type.

Non-transactional data

transportation_lane - Contains information about transportation lanes, including from and to sites, transportation mode, and transit time.

Vendor management

Non-transactional data

vendor_product - Contains the product information per vendor, including price, lead-time, and inbound sites.

Non-transactional data

vendor_lead_time - Contains the planned and actual lead times from the vendor.

Non-transactional data

vendor_holiday - Displays information on vendor outages due to holidays and shutdowns.

Planning

Non-transactional data

inv_policy - Contains inventory policies such as minimum and maximum safety stock policy, target inventory quantity, minimum or ma maximum order quantity and so on, for product, product-site, and other possible combinations.

Non-transactional data

segmentation - Used to store segments. Segments are used in conjunction with product, site, and effective dates for uniqueness. For example, HV1 for High Value, HLW for Halloween Products, seasonal, volatile and so on.

Non-transactional data

sourcing_rules - Defines rules at product-site level to specify the sourcing related attributes (for example, rule type, to and from site, transportation lane, minimum and maximum quantity, priority, ratio, and so on).

Non-transactional data

sourcing_schedule - Sourcing schedule determines when to source. For example, source from vendors or transfer between sites.

Non-transactional data

sourcing_schedule_details - Provides sourcing schedule details. For example, the days in a week, a product be sourced from a vendor.

Transactional data

reservation - Provides details about inventory reservation. For example, reservation ID, type, date, quantity, product ID.

Transactional data

product_bom - Displays bill of material for product with type, level, ratios, quantities, and cost attributes.

Operation

Transactional data

process_header - Track execution activities within a plant or site. For example, manufacturing, maintenance or repairs.

Transactional data

process_operation - Defines operation associated with an activity. For example, Stop machine, Oiling, and so on.

Transactional data

process_product - Define the product or material associated with an activity.

Transactional data

production_process - Defines attributes associated with the manufacturing or production process.

Inventory Management

Transactional data

inv_level - A snapshot of the product’s inventory condition in each site. For example, snapshot date, on-hand inventory, condition of the product.

Inbound

Transactional data

inbound_order - Contains information about inbound orders into your companies locations. For example, for example, purchase orders (POs), blanket POs, production orders, or stock transfer orders).

Transactional data

inbound_order_line - Stores line level information for inbound_order, including product_id, and quantity.

Transactional data

inbound_order_line_schedule - Stores schedule-line level data within an inbound_order_line and is relevant only when schedules are used.

Transactional data

shipment - Stores shipment information like origin, carrier code, ship date, product, quantity, ship from site, expected delivery date, and actual delivery date, or inbound orders (PO,TO and so on) including ship date, product, quantity, ship from site, expected delivery date, and actual delivery date.

Transactional data

shipment_stop - Contains list of shipment stops with corresponding date and time. This field is used when there are multiple stops for shipments.

Transactional data

shipment_stop_order - Contains list of orders picked and dropped per shipment stop.

Transactional data

shipment_lot - Contains the shipment details per shipment lot.

Outbound fulfillment

Transactional data

outbound_order_line - Contains orders originating from your company and shipped to locations outside of the your network. Outbound_order_line contains order date, customer location, incoterms, and so on. It also includes product, price, discount, and units.

Transactional data

outbound_shipment - Stores shipment information for outbound orders, including ship date, product, quantity, ship from site, expected delivery date, and actual delivery date.

Cost management

Transactional data

customer_cost - Displays the information about the costs incurred by you during the supply chain operations.

Plan

Transactional data

supply_plan - Displays the supply plan generated by AWS Supply Chain Supply Planning.

Forecast

Transactional data

forecast - Stores forecast over forecast horizon for product, product-site, or other combinations.

Transactional data

supplementary_time_series - Displays additional demand driver time series information such as price, promotions, and out-of-stock indicator to improve forecast quality.

Reference

Non-transactional data

reference_field - Contains mapping of any entity-field-value combination to a corresponding description, such as mapping specific inbound_order status code to status description.

Non-transactional data

calendar - Calendars can be used for many purposes by the application, such as planning, execution, and reporting.

Non-transactional data

uom_conversion - Contains conversions for unit of measure (UOM).

Insights

Transactional data

work_order_plan - Provides the supply chain process plan for a work order along with source type and duration to finish each supply chain process.