Hierarchy
EA-FIN (Software Component) EA-FIN⤷
RE-FX-MI (Application Component) Migration⤷
RE_MI_CL (Package) RE: Migration RE Classic => RE-FX
IMG Activity
| ID | REFXV_TIVMISETCNTYPE | Contract: Define Different Contract Types for Third-Party and Own Usage |
| Transaction Code | S_XEN_65000027 | (empty) |
| Created on | 20050718 | |
| Customizing Attributes | REFXV_TIVMISETCNTYPE | Contract: Define Different Contract Types for Third-Party and Own Usage |
| Customizing Activity | REFXV_TIVMISETCNTYPE | Contract: Define Different Contract Types for Third-Party and Own Usage |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | REFXV_TIVMISETCNTYPE |
Use
Here you can specify the contract type in RE-FX that an existing contract type in Classic RE is converted to. The system proposes that you use the same contract types for RE-FX as in Classic RE. The system converts contract types using this logic if there is no entry for them here.
Note the following if you had contracts both for your own usage and for third-party usage in Classic RE:
- In Classic RE, the same contract type is used for both own usage and for third-party usage.
- In RE-FX, there is an indicator in the contract type that determines if the contract type is for internal or external use (own usage or third-party usage).
Therefore, if a contract type in Classic RE was used for both own usage and third-party usage, you are required to define at least one new key for the contract type. In the Propose Conversion Decisions for Customizing step, the system already determined which contract types in your system were used for both own usage and third-party usage contracts, and the system already generated two entries for each of these contract types.
For the third-party usage contracts, the system proposes keeping the existing contract type.
For contracts for own usage, the New Contract Type field is blank. In this blank field, enter the key that this contract type for own usage should now have. This contract type does not have to exist already. In the Convert Customizing step, the system automatically copies the setting for the "old" contract type; for the new one, it changes the usage to Own Use.
Aside from this, you also have the option of defining new keys in RE-FX in this table for all contract types of Classic RE.
Activities
Enter the key for the new contract type, at least for those contract types with contracts for both own use and third-party use.
For any contract types from Classic RE, for which there is no entry here, the system uses the same key in RE-FX that was used in Classic RE.
If, based on this logic, there is a contract for third-party usage that has the same contract type as a contract for own usage, then the system issues an error message.
Example
Business Attributes
| ASAP Roadmap ID | 252 | Prepare Data Transfer Fields |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 1 | 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 | REFXV_TIVMISETCNTYPE | 0 | ALN0000041 | Migration |
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 |
| V_TIVMISETCNTYPE | V - View | SM30 |
History
| Last changed by/on | SAP | 20050810 |
| SAP Release Created in | 600 |
