PO version management - view history version

Hi expert,
I'm using PO version management together with change PO output.
1. Is there a way to pre-view or re-print a certain history version of the PO output? currently only the last version can be previewed and I got error message when I try to reprint hisotory version (no printed relevant changes).
2. When I change the PO, a new version is not created until I save the PO. I have to come to the change mode again to mark it "complete". Is there a way to have the new version available before save, so I can make my changes and mark it completed right way.
3. Is there a standard SAP report shows incompleted PO versions? I need to run it to remind me of the PO's that I still need to work on or to mark completed.
Thanks a lot for your kind help!
Regards,
Jully

Hi Jully,
You can try the following link :
http://www.sap-img.com/mm001.htm
It is an ABAP program contributed by one of the SAP members, which reports all the changes made in PO and list out the details per document.
Take the help of your ABAP consultant to run for you.
See if it helps.
Best regards
Amit Bakshi

Similar Messages

Upgrade to ECC - Can we keep our Version Management & Transport History?

Hi
We definitely do not want to loose our Version Management and/or Transport History during our upgrade from 4.7 to ECC 6.0
Is it possible to keep the Version Management and Transport History? Can this be imported and applied to ECC 6.0 client after/during upgrade?
Please advise.
Thank you and best regards,
Adrian

Hi Adrian,
The modification adjustment of the ABAP Dictionary objects is performed before downtime. This
is possible since the complete version management is available in the shadow system.
Even the upgrade guide details this.
Also, for your information, please check the SAP Note
130906 How can versions be transported
Hope this helps.
Regards,
Sriram

Version management external no version

Hi All,
While I maintain version management it is asking for a external no for version message MEDCM006 ,but I dont know where I have to maintain .In fact I want internal version management no ,such that the system should automatically generate new version no .
Regards
Abhijit

Hi,
1. Goto SPRO>MM>Purchasing>Version Mgmt>Setup Ver mgmt for ext Purch Docs
2. Select your Pur.Org & Double Click
3.In Field Selection Tab, there will be fields for Reason, Short Text, Requester, External No & Posting Date
4.In External Number field change the entry from Required entry to Optional entry
Save the settings.Now you woudn't get that error
Regards,
Baskar.

Actual and Plan Versions annual view - Multiple versions per company code

Good Day,
Iu2019m creating an FI-CO query with an annual view of both Actuals and Plan Values, which uses period and version as input values. The dilemma is around the plan versions which are hardcoded per company codes (eg. 1 Company Code = versions 501 u2013 512)
Can anyone suggest a possible solutions as normally there is only one version used for planning but in this instance there are multiple versions per Company Code.
Currently the report is hardcoded for one Company Code and going forward it should cater for more than one(Company Company* 12 Version)
Kind Regards

Remove restriction on comp code. There could be 2 models.
1. Include comp code, value type and version in the rows. This way you get multiple records for a comp code. One record for actual data and one record each for plan versions. To have this model at the query, the data model in the cube also should be in this way (what we call as the account model), multiple records differentiated into actual/plan by valuetype and different versions by version.
2. Include comp code in rows. Create selections, one for actuals (restrict with key fig and value type 10, actuals), one for each plan versions (restrict key fig with value type 20, version 501. Create one selection for each version this way). This way we have one record per comp code with diff key fig for actual and plan versions. We call this as key fig model. To have this model at the query, the data model in the cube could be account model or key fig model. If it is key fig model then no need of selections. The key fig could be taken directly from the cube.

Trial / Test Version cannot view WebMarketing Version

I can publish and view a WebBasic site, but not a WebMarketing Site. I have created a New site on Business Catalyst and chosen WebMarketing, then I go to Muse and publish to that site. When I try to preview it does not work. I have not tried to add any modules or anything fancy. Just trying to view it with the WebMarketing choice. Same site, same publishing techniques - I can view the WebBasic, I cannot view the WebMarketing. Any ideas why?

Thanks for asking, I got this resolved. I had to change the "home" page to "index." The first time I had uploaded that issue did not occur. With the second publishing and a change in the site name, when previewing I got the big construction sign. Editing the site "home" page (as it uploads from Muse) to "index", did the trick. Thanks for asking!

Version management for POs

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---MATNR
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.
we need to enter all the fields including header fields and item fields ,
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 for my doubts.
Regards,
Magana

Hi
For a combination of purchasing organization, document category, and document type, you can:
<b>Activate version management</b>
If version management is active, changes to a purchasing document are managed in versions.
<b>Define field selection for versions</b>
You can specify the attributes certain fields of the version are to have: mandatory entry, optional entry, display only, field suppressed.
Set the message ststus as follows
MEDCM     014     Purchasing document &, version & in process     W
MEDCM     019     Purchasing document &, version 0, still in process     E
MEDCM     021     Not all version-relevant changes were cancelled (&1)     W
MEDCM     023     No unprocessed message exists                         W
System will allow to manually close the version .Version 0 will be set automatically .After that system will allow to manually close the version.
I dont think you will face probelm.
Regards
Sunny

Purchase order item text version management is not creating.

Dear sap professionals,
I have an issue in item text as per customer need I created item text type as drawing number, the problem is when ever an user change drawing number review in text area system should create new version number, but in present case instead of creating new version number the data is updating in existed version number.
Same time I am not able to trace field name and table used for this specific drawing number type, do I need to do any new configuration for that or I missed any thing in this process.
Did any one experienced same issue?
With Regards,
Ranganath

ranganath.kakarla wrote:
Dear sap professionals,
>
> I have an issue in item text as per customer need I created item text type as drawing number, the problem is when ever an user change drawing number review in text area system should create new version number, but in present case instead of creating new version number the data is updating in existed version number.
> Same time I am not able to trace field name and table used for this specific drawing number type, do I need to do any new configuration for that or I missed any thing in this process.
> Did any one experienced same issue?
>
> With Regards,
> Ranganath
Hi,
path:mm-purchasing-version management-Set Up Version Management for External Purchasing Documents
Doc.cat will be F means po, Doc type will be NB & p.org of ur client
in control data active both version acrive & version 0 ok.
in field selection reason, shorttext& requestor is required option & save
give the reason for ur inputs
in Set Up Change Displays category willbe f for all doc types
Regards
Raj.

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 error

Dear Gurus,
Am havng a problem in version Management. After creating a P.O and saving it I need to make changes in it. I am changing the quantity and before saving the P.O i want to enter the reason for change. The red flag on top of status tab is not coming and it is not allowing me to enter the reason for change. Kindly guide me how to fix this prblm...Thankyou...

Hello,
New version will only be triggered, once you completely release the PO, output the PO and then do any changes with print relevant fields.
For maintaining reason for change in version, you can follow Customizing --> Purchasing --> Version Management --> Set Up Version Management for External Purchasing Documents, and make the field mandatory.
Hope this helps.
Thanks & Regards,
Mihir Popat

Steps for configuration of version management

Dear Experts,
Kindly tell me what is meant by version management and under which situation this will be used and how its impact in MM after configuring this. Kindly let me know the configuration steps for version management.
Regards,
Prasath

You make the settings here for activating the version management:
SPRO --> MM --> Purchasing --> Version management --> Set up version management for PR -->here make the settings and tick on the activate indicator...
Now define the relevent fields which shd go under version change:
SPRO --> MM --> Purchasing --> Version management --> Version relevent fields of PR's
If you wanna set up change displays and its output, then make settings here:
SPRO --> MM --> Purchasing --> Version management --> Set up change displays...
NOTE: You can only release this PR fully if you tick the version completed indicator in the PR document...
Similrly you can activate for Purchase order
spro-mm-purchasing-version management-purchase order

Fields triggering Version management in POs

I see in the following path in SPRO
MM-> Purchasing ->Version Management -> Set up version management for external purchasing document:
Version Management is active for doc cat 'F ' , doc type EC , and Purchasing Org FR01. But still when I changed the price of a PO (type EC and pur org FR01 ) and set the delivery indicator in the PO , the version management was not triggered.
What is the reason for this? Is it that VM will be triggered only for a specific fields in the PO?Where are these fields set?
I have seen in the same path there is an option "Version-relevant Fields of Purchase Requisitions" , but there is nothing for PO

hi,
Check your settings properly...
You can't set the fields for the PO as you do for PR...
The whole document will be taken in to consideration for version change and if setttings done properly
then the version compleated indicator must be set before releasing the PO and then check...
Regards
Priyanka.P

Version Management Table values

Dear Friends,
Following are the requirements of client to make the Purchase Order Version active.
Price Change
Qty Change
Change in Material Code
Change in Material Description
Header Text Change
Pl let me know whether all the 5 requirements are possible for PO and also help me to find out the table and field names of the 5 above requirements.
Regards,
ASK

hello,
did you activated the version management in the system. if not activate it through the following menu path,
spro>material management>purchasing>version management> Set Up Version Management for External Purchasing Documents
check the box against your P.org.
once you activate it., create a po with that p.org and try changing that po through me22n. a version tab will appear in header details. make any required changes in po and save it. now go to the versions tab, select the version line and click on the "display changes" button. you'l get a detailed changes list that you have made in the po.
hope this helps,
regards,
vamshi

Version management(Purchasing)

Hi All,
         please clarify the Use of version management,what&why and when it is required?
         please explain briefly process....like
         set up version management for
        1. PR's and Externanal Purchase documents
        2. define reasons for change,what are the reasons
        3. set up change displays
        4. version relevent fields of PR's, why not for Purchase orders
   thanks in advance
Thanks&regards
Venkate

Hi,
SPRO > MM > Purchasing > Version Management
- Set Up Version Management for Purchase Requisitions
In this step, you set up the Version Management facility for purchase requisitions.
For a combination of document category and document type, you can:
Activate Version Management: - If Version Management is active, the changes made to a purchasing document are managed in versions.
Set up field selection for versions: - For certain fields of the version, you can specify which properties they are to to have: mandatory entry, optional entry, display only, suppressed.
Note: - When a purchase requisition is created externally (e.g. via a BAPI), the system does not check whether these fields have been designated as mandatory-entry fields.
- 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:
Activate version management: - If version management is active, changes to a purchasing document are managed in versions.
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.
- Define Reasons for Change
In this step, you can define the reasons for changes to requisitions and external purchasing documents (e.g. increase in material requirement).
- Set Up Change Displays
In this workstep, you can specify whether and in which change displays (e.g. for version via @II@) a certain field is to be displayed.
- Version-Relevant Fields of Purchase Requisitions
In this step you can specify whether changes to a field are version-relevant. ("Version-relevant" means that a change to a field causes a new version to be created.)

Can someone help me bring up ALL previous versions of an Adobe Story Script? (Tried View History already).

Hi, I am working on a script. Somewhere along the way, I lost a scene I know I previously wrote. I tried looking at the View > History menu option, but it only shows 3 different saves (it's been saved multiple times since July). Is there any way to bring up all previous versions of the file from the cloud?

christine major wrote:
The only thing that I can think of, was to possibly erase and reinstall again
that might not be a bad idea. and, yes, you should use the +firewire method+ to migrate @ least some of the data using setup assistant (which launches automatically once you have reinstalled OS X). you should be able to safely migrate everything but applications. i would re-install 3rd party applications manually and, since you migrated the user data earlier, you will find that you won't have to re-enter any license numbers or settings.
Pondini has a brilliant [walkthrough|http://web.me.com/pondini/AppleTips/Setup.html] for you. just deselect the applications @ the prompt.
when the migration process is done, i would immediately +repair permissions+, then restart. next, i would run software update from the  menu and install any updates offered. repair permissions again and restart.
@ this stage, you might want to try to upgrade to SL again.
as for the iTunes library, the simplest way would again be to connect the two Macs with a firewire cable, boot the source Mac in _*Target Disk Mode*_ (TDM), and copy the entire iTunes folder (not just the iTunes music folder) from <MacintoshHD>/users/<yourname>/music on the source (Mini) to <MacintoshHD>/users/<yourname>/music on the target (overwriting the iTunes folder in place there). since you updated all software components earlier, you shouldn't see that error message again.
the iPhoto library can be copied manually, too. again, using TDM, just drag and drop from source to target. see this user tip for locations: _*where important data is stored*_ (one correction to this link: iCal data is stored in ~/library/calendars).
JGG

Why does the fire fox page change, sometimes it is just an orange fire fox button and othr times it says file, edit, view History, bookmarks, tools, help? I barely learn how to run one version of the page and then it changes

Why does the fire fox page change, sometimes it is just an orange fire fox button on the top left that opens a panel with all the things listed in it and then it sometimes has a bar across the top that says File, Edit, View, History, bookmarks, tools, Help? I barely get used to using one type of set up and then it changes to the other without me doing anything??

[[Menu bar is missing]] and [[Preferences are not saved]] may help to you

PO version management - view history version

Similar Messages

Maybe you are looking for