3.3 Specific Rules for naming a business data term or group

Submitted by GS1.IT.team on Sat, 12/12/2020 - 07:51

The following specific rules for naming a business data term or group apply to business data terms or group used for GS1 identification keys, coded values, monetary amounts, references and dates or date periods.

3.3.1 Business data terms or groups, which are constituted by a GS1 acronym such as GLN, GTIN, SSCC, GDTI and other GS1 identification keys.

R14. The business data terms or groups must be written in full name.

R15. The acronym of the GS1 identification key must be included in the business data term name separated by a “,”.

Not so good naming

Reason

Better naming

GTIN

Not British English (R 3).

Not business oriented (R 5).

No clear use (R 8).

The name must be written in full name and be complete by “,” and the acronym (R 13, R 14).

Global trade item number, GTIN

GLN

Not British English (R 3).

Not business oriented (R 5).

No clear use (R 8).

The name must be written in full name and be complete by “,” and the acronym (R 13, R 14).

Global location number, GLN

3.3.2 Business data terms or groups which are constituted by an abbreviation

R16. The business data terms or groups must be written in full name.

R17. The abbreviation must be included in the business data term name separated by a “,”.

Not so good naming

Reason

Better naming

SEPA

The name must be written in full name and be complete by “,” and the acronym (R 16, R 17).

Single euro payments area information, SEPA

3.3.3 Business data terms or groups which contains dates

R18. The word “date” must be included in the name.

R19. The name must be designed in a way that it is clear what is meant by the indication of the date.

Not so good naming

Reason

Better naming

Date

No clear use (R 8).

Multiple purposes (R 9).

Lacks meaning for the date (R 19).

Document creation date

Estimated date for the delivery

Too long (R 6).

Estimated delivery date


3.3.4 Business data terms or group which contain a date and time

R20. The words “date” and “time” must be included in the name.

R21. The words “date” and “time” must be included in the business data term group if the group contains the business data terms “date” and “time”, and the business data term group mainly expresses date and time information.

R22. The business data term name must be designed in a way that it is clear what is meant by the indication of the date time.

Not so good naming

Reason

Better naming

Requested delivery time

No clear meaning (R 22).

The word “date” must be included (R 20).

Requested delivery date time

Requested date and time for the delivery

Too long (R 6).

Bad naming (R 21).

Requested delivery date time

Referenced customer document date and time information

(R21) the business data term does not mainly express a date. It contains date and time and other information.

Referenced customer document information

3.3.5 Rules only for business data terms which contain a time period or date period

R23. When the SDD include a time or date period, the business data term must been split in two business data terms.

R24. The business data term name must be designed in a way that it is clear what is meant by the indication of the begin or end period.

Not so good naming

Reason

Better naming

time period

split in 2 business data terms (R 23).

Begin time period || End time period

Date period

split in 2 business data terms (R 23).

Begin date period || End date period

3.3.6 Business data terms or groups which contain a coded value

R25. The word “code” must be included in the name.

R26. The word “code” must be in the end of the name.

R27. The name must be designed in a way that it is clear what is meant by the coded information.

Not so good naming

Reason

Better naming

Currency code for invoice

Name is too specific (R 10).

The word “code” not at the end (R 26).

Currency code

currency ccording to ISO-4217

Name is too specific (R 10).

Name includes reference to standard (R 11).

The word “code” not at the end (R 26).

(R54, R55, R56) For Code list reference

Currency code

(Reference to ISO-4217 to be included in a separate field: “used code list”, in the semantic model of the business document in which the business data term is used.)

3.3.7 Business data terms or groups which contain a reference to a document

R28. The name must begin with the word “Referenced” when referring to a document.

R29. The Business data term group name must end with “information” when the reference is to a set of information.

R30. The name referring to a document must be designed in a way that it is clear which document is referenced.

Not so good naming

Reason

Better naming

Despatch advice

Name begins incorrect (R 28).

Not clear as a reference (R 30).

Referenced despatch advice information

3.3.8 Business data terms or groups which contain a reference to a line in a document

R31. When referring to a document line, the generic business data term must be used.

R32. Where the business data term is used the exact meaning must be specified in the document model.

Not so good naming

Reason

Better naming

Line in despatch advice

Name begins incorrect (R 31).

Not clear as a reference (R 32).

Document line number

3.3.9 Business data terms or groups which contain a monetary amount

R33. When the name constitutes a monetary amount, it must include the word “monetary amount”.

Not so good naming

Reason

Better naming

Total tax amount

The word “monetary” is not included (R 33).

Total tax monetary amount

3.3.10 Business data terms derived from a Boolean data type

R34. No business data terms … Boolean data type should appear in the semantic data dictionary.

R35. A GDD Boolean attribute should be created as a business data term.

R36. The name of the business data term must include the word “indicator” in the end.

Not so good naming

Reason

Better naming

Is signature required

The word “indicator” is not included (R 36).

Signature requirement indicator

Which of the following best describes the primary purpose of your visit?

Success

Thank you for your feedback!

Were you able to find the information you were looking for on our website?

Success

Thank you for your feedback!