Version mgmt in PR

I am using 3 level rel strategy for PR;
I want to develop a report for the release dates along with its codes.
Does version management stores the rel dates for a PR.
VS

Hi
Yes Version mangemnt stores the relase dates of the PR, Please check the Table EREV - Version in Purchasing
Thanks & Regards
Kishore

Similar Messages

Version mgmt

I wnat to have the release codes & release dates for PR in version mgmt.
How can I do so.
regards
VS

hai,
Go for
Spro->MM->Version management->set up vrsion management for purchase requisition->Version ok
Version o ok check box both
then give the version relelavance changes .
there u give the corresponding fileld name for which u need the versions to be updated.
Regards,
Senthil

PO Version Mgmt Control by Text Type

Hi -
We currently have Version Management active for Purchase Order for when 'Item Text' is changed/updated on the purchase order, yet Version Management does not invoke for other purchase order item/header texts changes.
Does anyone know where in configuration this control is set for purchase order text types?
Thanks,
Karen

Hello,
Please check the following configuration
Purchasing-> Messages -> Fields Relevant to Printouts of Changes
System takes fields of tables EKKO, EKPO, EKET and ADRC into account.
Please check note 664928 : FAQ Version Management
Hope this solves.
Ashutosh

Planning Version Mgmt

Hello Gurus -
I have a few questions in planning version management. Appreciate if you can help me out.
Scenario: I have some planning data in the active version 000 and I have used "/SAPAPO/VERCOP - Copy Planning Version" to create a new version 001. Now I have the same data in both 000 and 001.
Then I went on to change some planning data in 001 to do my what if analysis and I arrived at a final plan which I want to see in 000.
Question: How do I do this? Since we cannot just copy it back to 000. Do we have to replan it in 000? Or do I have to delete the existing 000 and then copy/create 001>000? How is this normally done?
Appreciate your help!
Varun

Thanks Harish -
I am copying order series data, so I would be using the merge functionality. However the help document says :
SNP orders are not permitted to be published directly into the SAP R/3 system. Communication with the SAP R/3 system is only permitted to take place using the Production Planning and Detailed Scheduling (PP/DS) component. The system performs a technical check of the corresponding Customizing for this.
It is not permitted for any releases to be made into or out of SNP until all the planning versions that came from an active version have been copied back into this active version.
AND when I tried to copy my simulation version results back into the active version, system does not let me do it and gives a message " Function not possible because of transfer to OLTP systems" and says I should try avoiding transfer to OLTP system.
But I do need to transfer the Preqs(both SNP and Deoplyment and POs from TLB) to R/3 and my SPRO settings for " Configure Transfer to OLTP System" is setup in such a way that I transfer all output of SNP/DEP/TLB to R/3.
Any idea what could be done here?
Thanks a lot..
Varun

BW Conversion Rountine Version Mgmt

Hi,
We have just upgraded BW release 3.0B to SP level 28.
After the upgrade, we realized that the customized infosource transfer/conversion routine seems to have been overwritten and we could not find or retrieve the last transfer/conversion routine codes before the upgrade.
1. Is there anyway to retrieve the last version of customized conversion routine and re-import into the system?
2. Is there any version management for BW transfer & update rules/routines/infopackages setup?
Regards,
Taly

Hi Dinesh,
Thanks for the reply.
This is actually our first BW upgrade and right now our development, test & production system have all been upgraded. In all the systems, the customized routine can't be found.
We managed to identify an old transport performed in 2002 (prior to upgrade) which seems to contain the customized routine. We had tried re-importing into the test system but it ended in errors as the datasource, source system and infopackages in the old transport does not exist anymore.
Seems like the customized conversion routine has been deleted or somehow overwritten after upgrade.
We are trying to find other means to recover the customized routine prior to upgrade. Is there any other ways of retrieving?
Regards,
Taly

Sun Java Version Mgmt, Which Version, Deployment Methods

All,
We are preparing to deploy the Enterprise Portal NW04s (7.0). We've realized that we have many different versions of Sun/Microsoft Java deployed around the organization. I'm looking for advice around a few questions.
1. Which version of Sun Java should we standardize on? We're assuming the latest which is 1.6.0_03.
2. How have other organizations deployed this? Batch scripts, logon scripts?? We do NOT have SMS or other deployment tools.
3. Is there a way to auto detect when launching the portal if someone has the right java JRE and if not to prompt them for an upgrade?
Thanks very much, any assistance is appreciated.
Ethan Hill
Greene Tweed & Co.

JVM of end users should not create trouble. Any JVM should do good in most cases. For portal users, browser version matters the most.
The best place to find the information you need is the platform availability matrix.
https://websmp202.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000651812&
Regards,
Prasanna Krishnamurthy

Version not triggerd in PO

Dear Experts,
Even though version management is maintained for Po document type, when creating PO 0 version is not triggered. in version tab blank is there. please let me know the reason for this. version mgmt settings are OK.
Thanks in advance.

Hi
Please recheck your Configuration with reference to the PO Created
The Document Category - F for Purchase order
The Document type
Purch. Org.
Version Active &
Version 0 OK Checked
Check in the PO if the same document type & Purchase organization has been used.
Thanks & Regards
Kishore

Version Change

Dear Experts,
I want to activate version for Tax Code what setting I required and what table and fields I mention and where.
RCR

Hi
Activate the Version Management: SPRO > MM > Purchasing > Version Mgmt > Set Up Version Management for External Purchasing Documents
After activating the same use the path: SPRO > MM > Purchasing > Messages > Fields Relevant to Printouts of Changes > Give the Table: EKPO & Ref. Field name: MWSKZ.
So that when ever you change the tax code after the PO Process (PO, PO Release, Output) is completed, version will active.
Check the flow
Regards
Prasanna

Version managt-MM

Dear friends,
Iam implimenting Version management for purchase orders.I have got doubts like;
1)---In IMG side ,under setup change displays node, we need to enter all the field names of purchase order document type wise, ..i.e.
we have got three doc.types of POs,NB,ZCP,ZCO,then Header and item details fields of PO shall be entered against each doc.type in this node.
like -NB-EKPO---field
NB-EKKO-field
We need to enter tables as EKKO and EKPO and
all the fileds are to be entered for all the doc.types.
2)----For header fields,if i change the data,version is not creating,
3)--At item details ,after release of the PO,if i change the data,if i save the document,it is saving without automatically closing the version.We need to manually close the version.
I have given error category E for application MEDCM for 14,19,22,eventhough system is not giving error.
Atleast provision should be there to give error if user doesnot close the version manually.
please suggest.
Regards,
Magana

Hi,
Senthil is correct. Version mgmt will be active only after the PO is printed / sent to vendor via EDI /email.
Please take print of it and then change the PO. Version will be created.
Thanks,
Anand.

Version management for PO

Hi,
If I create a PO & save, then i will add a freight condition in PO, will it be activated in version managment.
Also can we configure the fields which we want for triggering the Vesrion management.
Pleae suggest.
Thanks
SHP

Hi,
[Version Management| http://help.sap.com/saphelp_erp60_sp/helpdata/en/8a/60b43bb7492147e10000000a114084/content.htm]
In the case of procurement transactions extending over a longer period of time (for example, in the procurement of capital goods), you may need to differentiate between various versions of the purchasing document. You may also need to refer to one particular version when corresponding with the vendor.
The Version Management facility enables you to generate and manage versions of purchase requisitions and external purchasing documents such as POs. A version groups together the change documents generated in the course of subsequent processing of the relevant document. A version thus indicates the revision level of a document (version 0 = original document, versions 1 + = revisions) and provides the user with an overview of the various changes that may have been made in the course of time.
Version Management thus represents an extension to the hitherto existing change documentation functionality for internal and external purchasing documents.
Version Management can be used in connection with purchase requisitions (ME51N, ME52N and ME53N only), RFQs, purchase orders, contracts, and scheduling agreements.
The following prerequisites must be satisfied before a version of a purchasing document can be deleted:
The changes made in the version must have been reversed (cancelled, revoked)
All open messages must have been deleted
CONFIGURATION:
1) Go to SPRO-MM-Purchasing-Version Mgmt-Setup Version Mgmt for External Documents
Activate Version Mgmt against your Doc type and Double click on that Doc type NB then in next screen in Control data tab mark all the fields and in Field Selection set all the Fields as Required entry Except Posting Date and save.
2) go to SPRO-MM-Purchasing-Version Mgmt-Define Reasons for change
Create one New Reason Called Xyz something and give text and save.
3) Go to SPRO-MM-Purchasing-Version Mgmt-Set up change Displays
Here Select Doc type say NB and Give Table name say EKPO for PO and EBAN for PR, Give Field name say MENGE for qty and save.

Version Management - Automatic creation on vew version

hi experts,
I have activated in customizing a version management for Purchase Order, but I have the following problem:
the system doesn't generate a new version of PO when I change the address. I have already defined this field like a print-relevant in Customizing for Purchasing under Messages ® Fields Relevant to Printouts of Changes.
At the moment a can only see this change in a version display in the current version.
tkanks a lot
Mario

Hi Mario,
1) Go to SPRO-MM-Purchasing-Version Mgmt-Setup Version Mgmt for External Documents
Activate Version Mgmt against your Doc type and Double click on that Doc type NB then in next screen in Control data tab mark all the fields and in Field Selection set all the Fields as Required entry Except Posting Date and save.
2) go to SPRO-MM-Purchasing-Version Mgmt-Define Reasons for change
Create one New Reason Called Xyz something and give text and save.
3) Go to SPRO-MM-Purchasing-Version Mgmt-Set up change Displays
Here Select Doc type say NB and Give Table name say EKPO for PO and EBAN for PR, Give Field name say MENGE for qty and save.
Now try once.
http://help.sap.com/saphelp_erp60_sp/helpdata/en/8a/60b43bb7492147e10000000a114084/content.htm
Reg,
Ashok

Version comparison in purchase order

Hi
In a Purchase order, how do we compare that the current version is different from last completed version.
can some one give me information on what tables and fields i need to check to see these details.
Thanks
Vamsi

hi
Set Up Version Management for External Purchasing Documents
In this step, you set up the version management facility for external
purchasing documents.
For a combination of purchasing organization, document category, and
document type, you can:
o Activate version management
If version management is active, changes to a purchasing document
are managed in versions.
o Define field selection for versions
You can specify the attributes certain fields of the version are to
have: mandatory entry, optional entry, display only, field
suppressed.
process
spro>mm>purchase>version mang
set up version management for purchasing doc create ur new entry and tick version man active
save come one step behind
below it define reason for change
do it ur version management will be active
CONFIGURATION:
1) Go to SPRO-MM-Purchasing-Version Mgmt-Setup Version Mgmt for External Documents
Activate Version Mgmt against your Doc type and Double click on that Doc type NB then in next screen in Control data tab mark all the fields and in Field Selection set all the Fields as Required entry Except Posting Date and save.
2) go to SPRO-MM-Purchasing-Version Mgmt-Define Reasons for change
Create one New Reason Called Xyz something and give text and save.
3) Go to SPRO-MM-Purchasing-Version Mgmt-Set up change Displays
Here Select Doc type say NB and Give Table name say EKPO for PO and EBAN for PR, Give Field name say MENGE for qty and save.
Hope it helps...
Regards
Priyanka.P
AWARD IF HELPFULL

Version management in SAP

Hi
Can I have more details on the Version management for PO in SAP please.
please provide me some reference document if any

Hi,
Goto SPRO>MM->Purchasing-->version management->Set up version mgmt for external purchasing document
& maintain your entries.
1)Doc cat-F,PO Doc type,Pur org,Activate,
2) Goto its details>select version active,version '0' ok,
Reason-->+Required entry
Short text---> Optional entry
2)Define reason for change say price change, qty change
Hope this will be sufficient for you.
Reward points if helful.
Regards,
Piyush
Edited by: Piyush Mishra on Mar 7, 2008 7:55 AM

Version management- the 'I' type (version created by import)

Hi,
We are in the midst of upgrade. I noticed that after the system copy, some program screens are missing in the new system. A check on the program version in the old system shows this:
Version Cat Fla SAP Rel. Arch Request    Project
Version(s) in the development database:
activ          X 700
Version(s) in the version database:
00002 I          700       UPGRADE700
00001 S          40B       D01K905538
We are thinking to do a transport to the new system to resolve the missing screens problem. However, there is no way I can navigate to the transport request created with UPGRADE700. Does anyone know how is this being created? It has version type 'I' which means is a version created by import?
Thanks in advance!

Hi,
Yes, you need to import the screen once again separately. Regarding the version Mgmt Transport indicators:
'I' --> Imported Version
'S' --> System Request (Before an import)
'U' --> User Request
Thanks,
Shiv

Version management in release procudeure

can anyone help me throwing some lights on version management in release procedure of PR/PO??
regards
Prakash

Hi,
When you activate version mgmt it will ask only when the value changes for the PO and not when the PO is released.
Ex:
If I want to change the PO price or Qty now new version would get trigger. You need to check and save the PO. Until and otherwise if you are not tick on the 'new version completed' you can't release the PO, It would be in Open state.
regards,
Dhanush.

Version mgmt in PR

Similar Messages

Maybe you are looking for