Ansicht
Dokumentation
VCH_HL_LOVC2AVC_COPY - AVC-Transition: Copy Dependencies
RFUMSV00 - Advance Return for Tax on Sales/Purchases Fill RESBD Structure from EBP Component StructureThis documentation is copyright by SAP AG.
Purpose
Transition of classic variant configuration models to advanced variant configuration.
Prerequisites
The source of the copy must be a configurable product with a classic configuration profile that is valid on the given key date. The status of the profile is not taken into consideration in this process. To determine the key date, either a valid-from date or a change number must be specified. When a change number is given, the report will take over the valid-from date from it.
The target configuration profile must be an already existing AVC profile of the source product that is valid on the given valid-from date. The target profile must have the same class type and must be created before executing the tool. Its status must not be Locked. If a change number is also entered, the target configuration profile must also be assigned to a change number considering the valid-from date.
A suffix must be specified also, for the name of the copied global object dependencies.
The copy process for one source product can be executed with the transition tool only once.
Features
After specifying the parameters of the copy, the object dependencies of the configuration model shall be loaded via pressing the Load data button. The application will collect and list the global and local dependencies from the source variant configuration model and will also provide a target name proposal for those items that have not been copied by the tool with a different source before.
The following dependencies are collected:
- Global and local dependencies and constraint nets (including constraints) of the source profile
- Global and local dependencies of characteristics and characteristic values allocated to all classes of the specified class type that is assigned to the source product
Copy status
When the global dependencies are assigned to multiple variant configuration models it is possible that there is already an AVC version of them. In this case, the status will be 'Copied'. If a global dependency was not processed yet, the status will be set to 'Ready for Copy'. Other possible statuses:
- Copied with errors: A previous copy attempt was not successful. No further processing of this dependency is possible. In such cases the dependencies should be copied manually with the dedicated applications.
- Cannot be copied: The model was already copied. No further processing of this dependency is possible.
- Already exists: The dependency was not copied before, but there is an already existing dependency with the proposed name. No further processing of this dependency is possible.
- Copied with other change number: The dependency has already been copied, but with a different validity date. The user can decide to adjust the validity with the specified change number and use the dependency for assignments.
- Unique name cannot be generated: There are multiple dependencies in the same model for which the same target name has been proposed. No further processing of this dependency is possible.
Assignment status
Whether the dependency can be assigned to the relevant master data object or not is visible in the Assignment status column. The assignment is only possible when the value is 'Ready for assignment’. Other possible statuses:
- Assigned: The assignment has been successfully done
- Assigned with errors: The assignment attempt was not successful
- Cannot be assigned: The target dependency name cannot be determined, therefore the assignment cannot be done
- No longer possible: The assignment has already been done via a previous run
In case of local dependencies, it is not possible to determine which were already copied and assigned due to their changing identifiers. Therefore, when they are selected, an AVC version of them will be generated and assigned to the relevant master data objects.
Activities
Depending on the user’s decision and their copy and assignment statuses, the selected dependencies can be automatically copied and/or assigned to the relevant master data objects.
After the user has decided which dependencies should be copied and assigned via checking the box in the Select column, the outcome of the AVC-Transition can be simulated via pressing the Simulate Copy button. No changes will happen in the system, but the steps and their simulated outcome will be displayed in the log screen.
When a constraint is selected without the corresponding constraint net, the system will automatically add the constraint net to the selection.
If a dependency is assigned to multiple master data objects, it will be copied only once, but the assignment will be done based on the user’s selection. Copying a dependency without assignments is not supported. When a change number was specified in the input screen, it will be used for both copying the dependencies and for the assignments.
The transition of the model can be done permanently via pressing the Execute Copy button. If the user selects 'Yes' in the confirmation pop-up, the model will be copied and marked as not processible by this application anymore. The results are written into the application log (Object/Subobject: VCH_HL/LOVC2AVC_COPY) for further reference.
PERFORM Short Reference Vendor Master (General Section)
This documentation is copyright by SAP AG.
Length: 6086 Date: 20240601 Time: 103203 sap01-206 ( 116 ms )
