Hierarchy

⤷

⤷

IMG Activity
ID | /SAPHT/SW_VERS_CHG | Assign upgrade path procedure to sales document type |
Transaction Code | /SAPHT/12000551 | (empty) |
Created on | 20000526 | |
Customizing Attributes | /SAPHT/SW_VERS_CHG | Assign upgrade path procedure to sales document type |
Customizing Activity | /SAPHT/SW_VERS_CHG | Assign upgrade path procedure to sales document type |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_CMMENUOLSDFV |
In this menu option, you define the rules according to which upgrade path or paths you use for version change processing. As part of completing a version change, you must indicate which existing license is being replaced by the new one. The licenses eligible for the version change are specified in the upgrade path table.
The upgrade path is controlled using the condition technique. This technique is described in detail in the examples for pricing and output determination. Further information on the condition technique can also be found in the "SD Pricing and Conditions" manual.
The following elements of the condition technique work together to control product listing:
- The condition table defines the field combinations required in an upgrade path master record.
- The access sequence is a search strategy that the system uses to search for valid condition records. You must define a search strategy for each condition type. The access sequence refers to the fields for the upgrade path or paths in the condition table.
- The type defines how upgrade path determination is carried out.
- The procedure which defines the condition types to be used in an upgrade path search. You use this procedure to check the master records for condition types via the upgrade path. Once you do this, you can assign the procedures to the sales document types.
The above elements are the same as those used in the material listing and exclusion process in the standard SAP system. However, you have to assign the upgrade path determination procedure to the sales document types via a different customizing transaction.
Example
Suppose someone creates the procedure VERS00 and assigns it to sales document type GOR. VERS00 contains one condition type VERS. You establish a master record for condition type VERS that specifies an upgrade path from GG_OS2 to GG_C++. If you do this, then it is possible to do a version change from GG_OS2 to GG_C++ for this document type (GOR).
Actions
First check whether you can use the listing and exclusion elements that are defined in the standard SAP system. If you need to make modifications, carry out the following steps:
- Define the condition table or copy the existing table and make the changes you require.
- If there are not enough fields available, you can extend the list of permitted fields with the field catalog.
- Define the access sequence and assign the condition table to it.
- Define the type of upgrade path and assign the access sequence to it.
- Define the procedures and assign appropriate types to them.
- Assign the upgrade path procedures to the sales document types.
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 |
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_TVAK_VW | V - View | OVCH |
History
Last changed by/on | SAP | 20001014 |
SAP Release Created in | 46C1 |