Business Engine
Resource | Category | Description |
---|---|---|
Ad Hoc Report Group | Configuration |
Ad hoc report groups are maintained in 'Ad Hoc Report Group. Open'(AHS100). To create an ad hoc report group, use one of the two design tool options: 0-Ad hoc report designer or 1-Configurable XML. For 0-Ad hoc report designer, these programs are included in the export: =
For 1-Configurable XML, these programs are included in the export: =
|
AP Accounting options | Configuration | Accounting options are defined in 'AP Accounting Option. Open' (APS020) and must be defined and maintained at the division level. |
AR Accounting options | Configuration | Accounting options are defined in 'AR Accounting Option. Open' (ARS020) and must be defined and maintained at the division level. |
Authorization by Roles |
Configuration | Authorization by Roles is maintained in 'Function. Connect
Authorization by Roles' (SES400) and must be defined either on a
company or division level. The Authorization by Roles is dependent on these
programs:
|
BOD initial load | Configuration | BOD initial loads are maintained in 'Initial Load. Open' (EVS006). BOD initial loads are not connected to an organization (company or division) and are configured on a tenant level. |
Custom list | Configuration |
Custom lists are maintained in 'Information Browser Category. Open' (CMS010) and is defined on a company level. The export contains these programs:
Custom list are dependent on ‘Sorting option’. |
Custom list MI | Configuration | Custom list MIs are maintained in 'Custom List MI. Open' (CMS015) and is defined on a company level. Custom list MI is dependent on (CMS010). |
Customer-defined fields | Configuration | Customer-defined fields are maintained in 'Customer-Defined Fields. Open' (CMS080) and is defined on a company level. |
Dataset | Configuration |
Datasets are maintained in 'Dataset. Open' (OSS401). These related programs are also included as part of the export:
|
Delivery methods | Configuration | Delivery methods are maintained in 'Delivery Method. Open' (CRS070). Delivery methods are connected to an organization on a company level, and are dependent on (CRS010). |
Dispatch policy | Configuration |
Dispatch policies are maintained in 'Dispatch Policy. Open' (MWS010). Dispatch policies are connected to an organization on a company level. Only records without warehouse key are included in the export. Dispatch policies are dependent on 'Item Numbering Rule. Open' (MWS050), 'Attribute. Open' (ATS010), and 'Transaction Reason. Open' (CRS103). |
Event Based Alert | Configuration | Event Based Alerts are maintained in 'Event Based Alerts. Open' (CMS047). Event Based Alerts are not connected to an organization (company/division) and are configured on a tenant level. |
Event Based API Calls | Configuration | Event Based API Calls are maintained in 'Event Based API Calls. Open' (CMS041). Event Based API Calls are not connected to an organization (company/division) and are configured on a tenant level. |
Event Log Fields | Configuration | Event Log Fields are maintained in 'Event Log Fields. Open' (CMS048). Event Log Fields are not connected to an organization (company/division) and are configured on a tenant level. |
Event Subscription | Configuration | Event Subscription is maintained in 'Event Subscription. Open' (CMS045). Event Subscription is not connected to an organization (company/division) and is configured on a tenant level. |
Feature toggle | Configuration |
Feature toggles are maintained in 'Feature List. Open' (CMS975). Only features with Feature type = 3-'Feature toggle’ and 4-'Feature toggle, process change' that have not elapsed the Update schedule period are available for export. Feature toggles are dependent on these programs:
|
Financial report specification | Configuration |
Financial report specifications are defined in 'Financial Report. Specify' (RGS900) and must be defined and maintained at the division level. All sections defined in 'Financial Report. Specify Section' (RGS901) connected to the report are also included as part of the export. |
Financial report group specification | Configuration | Financial report groups are defined in 'Financial Report Group.
Specify' (RGS905) and must be defined and maintained at the
division level. The financial reports included in the financial report group in
'Financial Report Group. Specify Details’ (RGS906) are
also included as part of the export. When importing the file, records are also automatically created in 'Financial Report Group. Open' (RGS305) and 'Financial Report Group. Open Details' (RGS306). Financial report groups are dependent on 'Financial Report. Specify' (RGS900). |
Fixed asset type | Configuration |
Fixed asset type is maintained in 'FA Type. Open' (FAS075) and must be defined and maintained at the division level. Aside from (FAS075), these related programs are included in the export:
These fields must be defined first before they can be used by the FAS programs listed above:
Note that the fixed asset type can affect accounting transactions. If fields from (FAS075) and (FAS076) are used in the accounting rule exemption, these fields must be defined correctly in the related programs. |
Goods receiving method | Configuration | Goods receiving methods are maintained in 'Goods Receiving Method'
(PPS345). Goods receiving methods are connected to an organization
on a company level. The related program 'Goods Receiving Method. Connect Document' (PPS346) is also included in the export. Goods receiving methods are dependent on these programs:
|
Item type | Configuration | Item types are maintained in 'Item Type. Open' (CRS040). Item types are connected to an organization on a company level. Only data stored in (CRS040) is included in the export. Data in 'Item Type. Select Fields' (MWS041), 'Item Type. Connect Warehouses' (MWS042), 'Item Type. Connect Alias' (MWS043), and 'Item type. Select Fields Equipment' (MWS046) is excluded. Item types are dependent on template items in 'Item. Open' (MMS001) and 'Item Numbering Rule. Open' (MWS050). |
Key Group | Configuration |
Key groups are maintained in 'XML Text Key Group. Open' (CMS034). They are defined on a company level. Key groups are used in the Custom text functionality. These programs are included in the export:
Note: (CMS036) and (CMS038) programs are only included
when they are connected to each other.
This export configuration uses the Configuration Management functionality. |
Language | Configuration | Languages are maintained in 'Language. Open' (CRS010). Languages are connected to an organization on a company level. |
Manufacturing Order Type | Manufacturing Order Type |
Manufacturing order types are maintained in 'Manufacturing Order Type. Open' (PMS120). Manufacturing order types are connected to an organization on a company level. Manufacturing Order types are dependent on these programs:
|
MDBREADMI transaction | Configuration | MDBREADMI transactions are maintained in 'MDBREADMI Transaction. Open' (MRS010). MDBREADMI transactions are not connected to an organization (company or division) and are configured on tenant level. MDBREADMI transactions are dependent on (CRS021). MDBREADMI transactions can only be deployed by replacing existing records. |
Payment term | Configuration |
Payment terms are maintained in 'Payment Term. Open' (CRS075). Payment terms are connected to an organization on a company level. Payment terms are dependent on (CRS010) and 'Start Day Interval. Open' (CMS071). |
Printer programs | Configuration |
Printer programs are maintained also in 'List and Printer programs. Open' (CMS005). It is defined on a company level. Printer programs are used in the Output Management functionality. These programs are included in the export:
Note: (CMS034) and (CMS033) programs are only included
when they are connected to each other.
|
Purchase order type | Configuration |
Purchase order types are maintained in 'Purchase Order Type. Open' (PPS095). Purchase order types are connected to an organization on a company level. Aside from (PPS095), the related program 'PO Type. Connect text' (PPS096) is included in the export. Purchase order types are dependent on these programs:
The related program 'PO Type. Connect number series' (PPS097) is not included in the export because it is connected to an organization on facility level. |
Purchase order type - Number series | Configuration |
P.O. Type - Number series are maintained in 'PO Type. Connect Number Series' (PPS097). P.O. Type - Number series are connected to an organization on a division level. Purchase order types are dependent on these programs:
|
QI plan | Configuration | Quality Inspection (QI) plans are maintained in 'Quality Inspection Plan. Open' (PPS340). QI plans are connected to an organization on a company level. |
Rental reason | Configuration | Rental reasons are maintained in 'Rental Reason. Open' (STS060), and are connected to an organization on a company level. |
Requisition/Distribution Order Types | Configuration |
Requisition/Distribution order types are maintained in 'Requisition/Distribution Order type. Open' (CRS200). Req/Distr order types are connected to an organization on a company level. Req/Distr order types are dependent on these programs:
|
Settings - Deliveries | Configuration |
Deliveries settings are maintained in 'Settings - Deliveries' (CRS721) and are defined on a company level. Settings - Deliveries are dependent on 'Stock Msg Partner. Open' (MMS865). |
Settings - TPL Standard Values | Configuration |
TPL standard values settings are maintained in 'Settings - TPL Standard Values' (CRS728), and the values are defined on a company level. Settings - TPL Standard values are dependent on 'Dispatch Policy. Open' (MWS010) and 'Delivery Method. Open' (CRS070). |
Sorting order | Configuration |
'Sorting Order. Open' (CRS022) is only available for programs that do not use a configurable list. Supported programs can be listed using EXPORTMI query 'C7PGNM from CSYVIG where SOUS < 2'. If a sorting order is invalid and cannot be deployed, it is not listed. To find excluded sorting orders, turn on the concept log for 'mvx.msf.crs.configuration.export'. Sorting orders are connected to an organization on a company level. Sorting orders are dependent on (CRS021). |
Sorting option | Configuration | 'M3 file. Create sorting options' (CRS021) is activated through an async job during deployment. If other configuration items are dependent on sorting options, these might not be active if deployed directly after. Sorting options are not connected to an organization (company or division) and are configured on tenant level. |
System languages | Configuration | System languages are maintained in 'System language. Open'
(MNS105).You can create custom languages in this program. These
are languages with Custom language indicator (CULN) set
to 1. In 'Custom Language Constants. Open'
(MNS130), you can add custom language constants. This holds the
custom translations for existing constant IDs. You can only export custom languages. The custom language details from (MNS105) are exported with the custom language constants from (MNS130). |
VAT report template | Configuration |
VAT report templates are maintained in 'VAT Report Template. Open' (TXS005). These related programs are also included as part of the export:
|
View | Configuration |
'View . Open' (CRS020) configuration is only available for programs that do not use a configurable list. To list the supported programs, use EXPORTMI query 'C7PGNM from CSYVIG where SOUS < 2'. Views are connected to an organization on a company level. Views are dependent on 'Sorting Order. Open' (CRS022). |
XML Structure | Configuration |
XML structure or variants are maintained in 'XML Structure. Open' (CMS006). This export configuration only selects a certain structure or variant to export. These programs are included in the export:
Note: (CMS034) and (CMS033) programs are only included
when they are connected to each other.
|