Version Management

[Former Member]

Hi ,

Can anyone explain in detail about the version Management , purpose .

Vighnesh.

[Former Member]

hI,

Version Management

Use

This function allows you to:

Create multiple versions of a planned independent requirement

Create planned independent requirement quantities or dates for one material

Label a planned independent requirements as a reference

Create versions of planned independent requirements in simulative mode to see how each version affects the production and procurement plan.

Activities

If you want a planned independent requirement version to be included in the operative planning run, activate it. Inactive planned independent requirements versions are excluded from the operative planning run.

Comparing Versions

Procedure

You can compare versions entered for a material, and you can copy one or all schedule lines from the version you are using for comparison. You can use this function to copy the planned independent requirements or the schedule lines of other materials.

Select the version.

Select Edit ® Compare reqs with ® Reqmts version.

The dialog box Compare With appears.

Enter the material.

Enter the requirements plan number if the version that you want to use for comparison has a requirements plan number.

Enter the requirements type.

Enter the plant in which the version to be used for comparison is created.

Specify the version to be used for comparison:

– To select one version, select Selected version, and enter the required version.

– To select all active versions, select All active versions.

– To select all active and inactive versions, select All active/inactive versions.

Choose Continue.

Result

The Compare Versions screen appears. On the left-hand side of the screen, the material or the version you selected in the dialog box is displayed. On the right-hand side of the screen, the material you selected on the entry screen is displayed.

Setting Periodicity for Versions

Procedure

To compare versions created using different periodicity, you can change the periodicity of both versions to a common periodicity using Change period.

If the same periodicity has been set for both versions, the system highlights the lines that contain different quantities, and displays the percentage of the deviation in a third column.

To set the periodicity for versions, select Edit ? Change period, and select the periodicity in which you want to compare the versions.

Result

The system highlights the periods in which the versions in comparison differ from each other. It also displays the percentage deviation between the quantity on the right and the quantity on the left in the Dev % column.

*Reward points

Regards

[alex_m]

You can track the changes using version management.

[Former Member]

Hi,

Go thru the Following Links,

http://help.sap.com/saphelp_nw04/helpdata/en/87/0a6b3ae886e511e10000000a114084/frameset.htm

http://help.sap.com/saphelp_nw04/helpdata/en/a4/d47e2d49e111d189730000e8322d00/frameset.htm

http://help.sap.com/saphelp_nw04/helpdata/en/22/bd18c8460a11d188fe0000e8323d3a/frameset.htm

Regards,

Padmam.

[Former Member]

Version management is done automatically in ABAP. It as good as software configuration in software engineering.

Once the system is set only for repairs in SAP , all the changes needs to be tracked. These changes would tracked using version management

[sreeramkumar_madisetty]

<b>Hi

The main purpose of the Version Management is to Maintain the Versions of the developed objects and to track the changes from version to the next version.

VSS(Visual Source Save) is the general tool used for Version Management purpose.

Or

Goto Utilities --> Version Management --> It will show u all the versions for an object. Select one and press Retrieve. It will first create temporary version. Goto that version and activate the code.

Hope it helps.</b>

Regards,

Sree

[Former Member]

Hi Vignesh

Version management in the Integration Repository permits versioning as follows:

· The Integration Builder manages multiple versions of a software component in an Integration Repository. In this way, different product versions can communicate with each other. Each design object is created in the context of a software component version that represents a unit of a product that can be shipped.

· Objects can also have new object versions when changes are made within a software component version. You also have the option of releasing changes to multiple objects simultaneously.

Versioning in the Integration Repository ensures that objects are shipped consistently, and as part of a product.

However, there are no software component versions in the Integration Directory, because the configuration content is not shipped. Nevertheless, you can also release changes to the configuration for the entire runtime environment here. When you release the objects, the Integration Server updates the directory runtime cache.

check this link also

http://help.sap.com/saphelp_nw04/helpdata/en/57/38e0fb4eb711d182bf0000e829fbfe/content.htm

Reward all helpfull answers

Regards

Pavan

[Former Member]

hi

good

Version management in the Integration Repository permits versioning as follows:

· The Integration Builder manages multiple versions of a software component in an Integration Repository. In this way, different product versions can communicate with each other. Each design object is created in the context of a software component version that represents a unit of a product that can be shipped.

· Objects can also have new object versions when changes are made within a software component version. You also have the option of releasing changes to multiple objects simultaneously.

Versioning in the Integration Repository ensures that objects are shipped consistently, and as part of a product.

However, there are no software component versions in the Integration Directory, because the configuration content is not shipped. Nevertheless, you can also release changes to the configuration for the entire runtime environment here. When you release the objects, the Integration Server updates the directory runtime cache.

http://help.sap.com/saphelp_nw04/helpdata/en/71/0b99063e1f974d9f25951746d04dc3/content.htm

thanks

mrutyun^

[Former Member]

Hi,

The purpose of retaining versions is to inform the translator of any changes that have been made to existing documents and to create an editing history.

A version is considered to have been finalized when the document in question is saved as active. The active version is released for translation.

When you edit and save an active document again, the version number is incremented. This happens irrespective of whether or not a text change has been made.

Note: When you save an already active document again as active, the version number is incremented only if you declare the change made to be translation-relevant.

For more information check the following link:

http://help.sap.com/saphelp_nw04/helpdata/en/87/0a6b3ae886e511e10000000a114084/frameset.htm

Regards,

Bhaskar