Basic setup

Dawid Kaczmarek Updated by Dawid Kaczmarek

Attributes and attribute types (PIM\Setup\attributes)

Product attributes represent the details that you want to maintain for some or all your products. With the CEPHEO data sheet functionality you can add them directly on the released products. When you define attributes, you must first define the attribute type. The attribute type identifies the type of data that can be entered for a specific attribute. The attribute type also defines a list or range of valid values, that can be used for the attribute. The first step is to create the types of attributes that is needed to define a product using the standard D365FO product attribute framework and afterwards create the specific attributes. As an example, the type could be 'Temperature' and the attributes could be 'Minimum storage temperature', 'Maximum storage temperature', 'Boiling point', 'Melting point' or similar. It is also possible to create a fixed list of values or a range applicable for the attribute.

It is important to note that translations are done using the translation buttons and creating the various texts in the wanted/needed languages.

NOTE: The attribute framework is a global setup, with the same data available cross all legal entities.

Figure 3: Product attributes and attribute types

Data sheet number sequence (Organization administration/ Number sequences/ Number sequences)

The number sequence used for the Data sheet ID is a shared number sequence and it is setup and its reference is defined directly on the number sequence

Figure 4: Create shared number sequences for DS ID

– Create a shared number sequence and under References select the option 'Product data sheet'/data sheet version:

Figure 5: Referece of number sequence is Product data sheet

Data sheet setup (parameters) (PIM/Setup/Data sheets/Data sheet setup)

Besides the number sequence you need to setup a few parameters regarding the behavior of Notes on data sheet groups and validation criteria, some of these can be defined on a more detailed level as well:

Embedded Image Embedded Image

Figure 6: Data sheet parameters

Datasheet document types (PIM/Setup/Data sheet)

Data sheet document types are defined per SSRS report located in the AOT and deployed to the reporting server, meaning that there can be one individual setup for the product data sheet, for batch certificate of conformity and for batch certificate of analysis, but only one for each. Here it is decided on a company level, whether the setup of content is specific for all sheets or for customers/items combinations. It also controls which languages will be available for groups, customer(s) or item-specific setups. In addition to defining the content, it is possible to define whether a validation of datasheet content should be performed or whether it can be overridden and the types of content that shall be validated.

Please be aware that when a data sheet is created, all settings on datasheet document types are taken from the setup at that moment. All future changes to data sheet document types will not affect the data sheets already created. For example if a language code is added or removed on a data sheet document type and a data sheet is already created referencing to that data sheet document type, the newly added or removed language WILL NOT affect the already created data sheet.

Here german has been added to the BCoA

Here german has been added to the BCoA

But for the already created data sheet 000002 it did not take effect:

But for the already created data sheet 000002 it did not take effect:

To get the changes added, you need to do it manually on the data sheets or create new data sheets.

To get the changes added, you need to do it manually on the data sheets or create new data sheets.

Setup items:

  • Datasheet header When this is validated, the systems checks whether all information in the sections name and notes is translated to the correct languages to avoid empty fields.
  • Datasheet group When this is validated, the systems checks whether all information in the sections name and notes is translated to the correct languages to avoid empty fields.
  • Datasheet attributes Here it is possible to activate validation of the presence of units and values for the relevant attributes, which are defined on the datasheet groups. Finally, a language validation can be performed for the description and friendly name of the attributes as well as for text values of the attribute's values.
  • Data sheet definition type

This field holds 2 values: Data sheet group (default) and Customer/item. When setting up a data sheet on a product, this can be setup as a general one i.e. product specific only, regardless of customer and country code, or it can be setup as combinations of the 3 elements. The data sheet groups that have been setup on the data sheet will all be part of the data sheet when printed.

When creating a certificate: BCOA or BCOC, all data sheet groups will also be included in the certificate IF the value of the field 'Definition type' = Data sheet group, if however the value of the field is 'Customer/Item', the system will search the setup in the form 'Certificate data sheet group setup' to determine which data sheet groups are included for the customer + item combination (see 4.1.6 )

Figure 7: Datasheet document types and elements

Data sheet groups (PIM\Setup\Data sheets)

Datasheet groups can be considered as sections of grouped data that can be present on the reports (like paragraph headers). They are the link between attributes and reports and could for example be a collection of temperature information. Within the food industry, it could also be nutritional values, where protein, carbohydrates and fat would be attributes within the group.

Please be aware that – as with data sheet document types explained above - when a data sheet is created, all settings on data sheet groups types are taken from the setup at that moment. All future changes to data sheet document types will not affect the data sheets already created. For example if attributes are added or removed on a data sheet group and a data sheet is already created referencing to that data sheet group, the newly added or removed attributes WILL NOT affect the already created data sheet.

This also goes with the “hide attribute value”.

The form consists of several parts:

The action pane – Here you can select "Translations" and set up the group name in the relevant languages. The name of the data sheet group will be used as a paragraph header in the reports. Using the "Datasheet documents button", it is possible to select on which documents the group can be printed. Finally, new groups can be created faster by copying from existing ones.

List - where you create and name new groups.

General area – This area contains general settings for the group, as well as identification. It is possible to define a general note, that can also contain an attribute value using the placeholder function. Additionally, it can be decided on a group level, whether attributes and attribute values will be printed on the document. Finally, it can be defined if notes on document should be validated in terms of the correct language.

Attributes – For the various attributes it can be selected, if the attribute values should be printed or it may be relevant to hide some of them. If the attribute type is a string (Text), you can also insert your own text, which is specific for this group and will be translated as well.

Note: If the attribute is a type 'Text' you can either define a fixed list of possible options or choose to setup data sheet specific text options. If the attribute type is marked for 'Fixed list' the language translations of the options must be maintained on the attribute type, whereas the 'non-fixed' option can be translated on the individual data sheet group (Button 'Translate' will be available).

Figure 8: Datasheet groups and document types

NOTE: Data sheet groups is a global setup, with the same data available cross all legal entities.

Data sheet item groups (PIM\Setup\Data sheet)

Here it is possible to group similar items for data sheet setup, similarly to how it is done for individual items. It is also possible to define on which documents the groups can be used and to create translations.

Figure 9: Datasheet item groups

Certificate type setup (PIM\Setup\Data sheet)

Here you can define, which type of certificate a specific Customer/Item combination will use/trigger. It is not possible to define two different certificates for the same combination. The difference between these two types of certificates is that a conformity certificate is a generic document displaying the standard product attributes for a batch product (similarly to what the product data sheet specifies for a product), whereas the certificate of analysis can display test results, that have been transferred to the batch attributes after test completion.

Figure 10: Certificate type setup

Certificate data sheet group setup (PIM\Setup\Data sheet)

![This form basically functions as the final content control before actual data is printed out on the certificate. The data sheet, that forms the basis of the data to be possible included in the applicable certificate for the customer/item combination.

You can in the form setup a which of the data sheet groups also should be part of the certificate (BCOA or BCOC) when printed for a specific product or all products in combination with a single customer (table), a customer group (group) or all customers.

The setup in this form is only searched IF the certificate type holds the value 'Customer/item' in field 'Definition type' (see 4.1.7).

In the screenshot the selected setup is defining, which of the groups are applicable for which certificate in relation to a combination of item(s) and customer(s).](../images/placeholder_image.png)

*This form basically functions as the final content control before actual data is printed out on the certificate. The data sheet, that forms the basis of the data to be possible included in the applicable certificate for the customer/item combination.

You can in the form setup a which of the data sheet groups also should be part of the certificate (BCOA or BCOC) when printed for a specific product or all products in combination with a single customer (table), a customer group (group) or all customers.

The setup in this form is only searched IF the certificate type holds the value 'Customer/item' in field 'Definition type' (see 4.1.7).

In the screenshot the selected setup is defining, which of the groups are applicable for which certificate in relation to a combination of item(s) and customer(s).*

Figure 11: Certificate data sheet group setup

How did we do?

Data sheets (PIM\Common\Data sheet)

Printing certificates for a batch

Contact