Hierarchy

⤷

⤷

IMG Activity
ID | CMX21 | Settings for Standard XStep Repository |
Transaction Code | S_EAE_99000004 | (empty) |
Created on | 20070410 | |
Customizing Attributes | CMX21 | Settings for Standard XStep Repository |
Customizing Activity | CMX21 | Settings for Standard XStep Repository |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | CMX21 |
Use
In this IMG activity, you make various settings for the standard XStep repository:
- Specifications re system behavior in the check sum check
You can export standard XStep objects and import them into a different XStep repository (see documentation in SAP Library under Logistics -> Production Planning -> Production Planning Process Industry -> Execution Steps -> Export and Import of standard XStep objects)
For this purpose, the data is transformed into XML files. The XML file can be processed and changed in the XML edito. With the check sum check, you can control whether XML files whose content was changed following the XML export are allowed to be imported into your target system. The check sum check must be activated both in the source system and in the target system prior to the export or import of the XML files.
You have the following options:
- No message
- Changed files are imported into your target system. The check sum check is not active in your SXS repository.
- Information/warning
- The check sum check is active. The system generates an information or warning message if changed XML files exist. The import into the target system is then continued.
- Error
- The check sum check is active. The system terminates the XML import if the files have been changed.
- SXS versions: Calculation of valid-to date
At any point in time, there must be only one version of a standard XStep having the status Released oder Released for Test. You can use the indicator to specify that the valid-to date of a version is calculated by the system. No valid-to date can be specified for the version in the repository.
If a valid version already exists for the standard XStep, this version ends one day before the valid-to date of the new version. The valid-to date of the previous version is entered by the system
(See documentation in SAP Library under Logistics -> Production Planning -> Production Planning Process Industry -> Execution Steps -> Versioning
- SXS Version: Automatic consecutive numbering
The versions of a standard XStep are numbered consecutively starting with the number 1.
The numbering cannot be changed manually.
- SXS version: Approval procedure active
If you set the indicator, an approval procedure with status management and digital signature strategy for certain status changes is active for the status assignment of the SXS version.
- For the assignment of the status Released and Approved and Discarded, you can specify a signature strategy. If you make no specification, the single signature is used.
The settings for the signature strategies are specified in advance in Customizing under Cross-Application Components -> General Application Functions -> Digital Signature.
Requirements
Standard settings
Activities
Example
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | CMX21 | 0 | HLA0006253 | Process Management |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
CMX_XSR_VM_SETS | V - View | CMX21 |
History
Last changed by/on | SAP | 20070725 |
SAP Release Created in |