Validation messages

If resources are rejected during the validation process, a summary of rejection is reported after the completion of the import process. For example:

APACS102=Rejected {0} resources for class "{1}".

Where {0} =Number of resources rejected during the import process.

{1} = Class name of import for which the resources are rejected.

A final message is logged to indicate the number of resources that are successfully imported. The duration of the process is also logged. For example:

APACS101=Imported {0} resources for class "{1}" (duration {2}).

Where {0} = Number of resources successfully imported.

{1} = Class name for which resources are imported.

{2} = Duration of import, in H:mm:ss format, for example ‘0:01:23’ for 1 minute, 23 seconds.

Example – Parent relations

Example 1

In this example, Routes Out and Routes In, both have a parent relation to Locations. Therefore:

  • Locations must be imported before Routes Out
  • Locations must be imported before Routes In

Routes has a parent relation to Routes Out and Routes In. Therefore:

  • Routes Out must be imported before Routes
  • Routes In must be imported before Routes

Scenario: Import resources for Routes Out with parent Locations relation

This table describes the mapping required to import resources for Routes Out with parent relation for Locations, and the data that is imported:

Mapped field Description Import Value (for example)
Routes Out.name Name of the Routes Out resource Route Out A
Locations.name Reference to parent Location resource Location X
Routes Out.description Description of the Routes Out resource Route Out A Description

The ‘Location X’ Locations resource must exist (The resources for references must exist on import).

The import process creates ‘Route Out A’ as Routes Out resource with description ‘Route Out A Description’ and creates a relation between Routes Out resource “Route Out A” and parent Locations ‘Location X’.

Example – Import Allocation resources

This diagram describes the relationship between the resources.

Example 2

Scenario 1: Import resources for regular (non-Allocation) Products class

This table describes the mapping required to import resources for Products and the examples of the data that is imported:

Mapped field Description Import Value (for example)
Products.name Name of Products resource being imported Product A
Products.description Description of Products resource Product description
Products.Item Class Item Class attribute value for Products resource CLS1
Products.units per transport unit (*) Value of default property “units per transport unit (*)” for Products resource 1.2

The import process creates Products resource with name ‘Product A’, description ‘Product description’, Item class ‘CLS1’ and default property units for each transport unit (*) value 1.2.

Scenario 2: Import resources for ‘Products At Locations’ allocation class

This table describes the mapping required to import resources for Product At Locations and the examples of the data that is imported:

Mapped field Description Import Value (for example)
Products.name Reference to Products resource Product A
Locations.name Reference to Locations resource Location X
Products At Locations.description Description of Products At Locations resource Product Location description
Products At Locations.Item Class Item Class attribute value for Products At Locations resource CLS1
Products At Locations.std cost (*) Value of default property “std cost (*)” for Products At Locations resource 1.2
Note: Resource references must be provided for Products and Locations, instead of Products At Locations.

The referenced resources must exist before importing. For Example:

  • ‘Product A’ Product resource
  • ‘Location X’ Location resource

After the completion of the import process:

  • The Products At Locations resource ‘Product A@Location X’ is created, which contains Products ‘Product A’ and Location ‘Location X’ component references.
  • The description is updated as ‘Product Location description’ for ‘Product A@Location X’.
  • The default property std cost value of 1.2 is updated for ‘Product A@Location X’.

Scenario 3: Import resources for ‘Customer Allocations’ allocation class

This table describes the mapping required to import resources for Customer Allocations and examples of data that is imported.

Mapped field Description Import Value (for example)
Products.name Reference to Products resource Product A
Locations.name Reference to Locations resource Location X
Customer.name Reference to Customers resource Customer 1
Customer Allocations.description Description of Customer Allocation resource Customer Allocation description
Customer Allocations.price (*) Value of default property ‘price (*)’ for Customer Allocation resource 12.5
Note: In addition to a reference for Customers component, references must be provided for Products and Locations to identify the ‘Products At Locations’ component. This is required as the ‘Products At Locations’ component class is an Allocation class.

The model definition determines that the import process considers ‘Customer Allocations’ class based on the resource references specified for Products, Locations, and Customer.

These resources must exist for references, before importing:

  • Products - ‘Product A’
  • Locations - ‘Location X’
  • Customers – ‘Customer 1’
  • Products At Locations Allocation resource – ‘Product A@Location X’

After the completion of the import process:

  • The Customer Allocations resource ‘Product A@Location X@Customer 1’ is created which contains Products At Locations ‘Product A@Location X’ and Customers ‘Customer 1’.
  • The description is updated as ‘Customer Allocation description’ for ‘Product A@Location X@Customer 1’.
  • The default property price value of 12.5 is updated for ‘Product A@Location X@Customer 1’.