License Management provides extensible master data that helps you adapt the functionality to your unique needs.
The creation, modification, and deletion of master data is logged.
Master data | Explanation |
---|---|
End-uses | End-uses to be considered in licenses or check transactions. Military end-use is predefined here, for example. You can add further required end-uses. |
Company groups | Here you can consolidate a company’s various sites and define the group of companies as a single business partner in a license or agreement. |
Classifications of goods ELAN-K2 | In the semi-annual ELAN-K2 usage reports on your licenses that require notification, BAFA requires a special export control number format with sub-numbers for more precise specification. These BAFA goods list numbers cannot always be determined automatically from the export control number. If there are several possible BAFA goods list numbers for an export control number, you can maintain a meaningful assignment to the goods attributes you use (e.g. a specific EU export control number plus a specific material number) in this master data. If the assignment in the table is unambiguous, License Management automatically populates the BAFA goods list numbers in your approvals. |
Goods lists | Lists of goods to which specific common regulations apply. You can use these, for example, in licenses or approvals. |
Goods attributes | Goods attributes, such as export control numbers, commodity codes, or material numbers, which you can use to specify licenses and approvals or to map a new jurisdiction. The EU export control number is predefined here, for example. You can add further required goods attributes. |
Organizational units | Organizational units of your company. You can optionally select organizational units in a license. |
Partner roles | Roles of partners to be taken into account for check transactions or licenses. Predefined roles include the consignor and recipient. You can add further required partner roles. |
Jurisdictions | Areas (countries, etc.) where a license is valid. Jurisdictions in combination with manual restrictions let you customize the rules that are applied during checks. |
Transaction types | Transaction types are particularly important if you run checks for the US ITAR jurisdiction. You determine the type of movement within an approval (company > customer, etc.) and whether identities of the goods should be created and checked. |
Value lists | Here you can specify the values that appear in the drop-down lists of specific fields. For example, you can define goods attribute lists for various product attributes. |
Comments
Please sign in to leave a comment.