Ansicht
Dokumentation
Process: Version Change Protection (VCP) Changes ( RELNGG_31H_VCPCHGS )
General Material Data BAL_S_LOG - Application Log: Log header dataThis documentation is copyright by SAP AG.
Short text
Process: Version Change Protection (VCP) Changes
Description
The order release process has changed as of IS-SW Release 1.3A. In previous releases, the notification order was deleted when a new released order was created. Therefore, there were two separate orders, one for notification (with the notification line items) and another for the released order (with the deliverable line items).
In Release 1.3A, the notification order is no longer deleted; rather, the deliverable line item is added to the notification order. Consequently, there is only one order for both the notification and release processes. After the notification process, the order contains only the notification items (one for the old product and another for the new product that is to be delivered). After the release process, the deliverable line item (for the new product) is added to the order. Now the order has three line items: two notification lines and one deliverable line item.
Selection run
The selection run is the start of a single VCP cycle. You can start the selection based on a profile with a collection of variants or a single variant. If you start the selection run with a profile that contains multiple variants, the variants are processed sequentially.
The result of the selection run depends on whether the push or pull method is used. If either the software or service material is defined as a push material, then IS-SW uses the push method and creates released orders. Otherwise, IS-SW uses the pull method and generates notification orders. (Note: In the push scenario, no notification line items are created, so the released order only contains the deliverable line item).
After the selection run has finished its processing, IS-SW displays an error log that shows which orders were unsuccessfully processed and the reasons for the errors.
In addition to being able to specify at the software or service material level if an item is a push material, you can overwrite the automatic process type determination at the time of the selection run. You can do this in either a selection profile or a selection variant. You can overwrite the automatic process type determination for both pull and push materials.
To overwrite the automatic process type determination for pull materials, in the OK31 selection process screen, choose:
Selection -> Notify
To overwrite the automatic type determination for push materials, in the OK31 selection process screen, choose:
Selection -> Generate
Notification
The notification line item created by the pull method for the old product contains all the relevant information and links back to the IBASE and/or contracts. Standard functionality for output determination is used to communicate with the customers.
The notification orders created by this selection run are blocked with a header delivery block 'G1' ('notified and blocked'). When you release the notification order, IS-SW creates a deliverable line item which can then be delivered. Notification line items, which refer to an IBASE record in scenarios one (IBASE) and two (Contract with IBASE), are recorded in the SW license's IBASE history.
Customer response processing
Customer responses are processed with the order due list functionality. The order due list can be called with reference to a selection profile or variant and gives you an overview of all orders and their respective statuses. Additional select options include country, ship-to party, delivery block and order creation date.
Each of the following functions can be executed from the order due list:
- Suspend
Notification orders can be suspended (delivery block 'G2'). One possible use for this function is bundle together multiple customer responses that you have received for release at a later point in time.
- Decline
Notification orders and suspended orders can be declined (delivery block 'G3'). After being declined, they are still contained in the list and can be re-activated at a suspended status. However, they cannot be released.
- Delete
All the orders in the list can be deleted from the order database.
- Change
All the orders in the list can be changed by double clicking on the order line. The change order transaction will be executed, and after saving the order, you will return back to the list.
Order Release
The order release process contains the steps necessary to create the deliverable line item from the notification line item. Deliverable line items will be immediately created if you start the selection run for a SW product using the push method.
When the order is released, for scenarios one (IBASE) and two (Contract with IBASE), the latest information from the IBASE is used to create a configured order item. This order item contains all SW license information. In addition, the IBASE history of the SW license is updated with the fact that a VCP order has been created. With this feature, you can track VCP activities by SW license.
ROGBILLS - Synchronize billing plans RFUMSV00 - Advance Return for Tax on Sales/Purchases
This documentation is copyright by SAP AG.
Length: 5549 Date: 20240520 Time: 212751 sap01-206 ( 122 ms )
