Version managment in purchase order's

Hi,
I am working on version management. I have configured it in the system but i have problem which is as below:-
Suppose i create a PO the system gives it version 0.Now i do various other changes and say create 2 more versions say ver 1 and ver 2.Now if i want to take the print of the original PO i.e ver 0 it still gives the print as in ver 2 which has all the changes instead of the original PO.Can u please explain why this is happening and the solutions.
regards,
Akshay

HI GUYS,
here's the scene in detail.
I make a PO with 1 item and qty 10,now when i save this version 0 is created.
Now i make changes in the PO say change the qty from 10 to 20, now version 1 is created. Now if i have to to the print of version 0, the print contains the changes which were made in version 1 i.e qty 20 instead of actual 10.
Does this mean that once a version is created the print of older version can't be taken without the changes that were made in the new version??

Similar Messages

Version management for Purchase order

Dear Friends,
I am implimenting version management for Purchase orders.
Under version management(IMG) ,set up change dispalys node--
following fields are available.
Ex:
Doc type-- ZCO,NB
For item view fields:
Field nameEMATN(material),TableMEPO1211--material field in Item over view
Field nameMENGE(Quantity),TableMEPO1211
For Header level fields:
Field nameZTERM(payment terms field),,TableMEPO1226
Category--A or B for selection of change documents
No out put--if i tick it concern field will not included in change doc
Version--what is the purpose
Please suggest me
1) we need enter the all the field names in the item over view and item details and Header level fields as given above ,is it correct.
2) And with regard to Table, do i enter for Header level fields-EKKO or MEPO1226 which is available in F1 under techinical information,
for item level fields,shall i enter table name-EKPO or MEPO1211as dispalyed in the F1 under techinical information.
3) I need to enter all the fields existing in the purchase order
4) All these fields and data is to be entered for every document type NB and ZCO.
5) After changes are made in Purchase order,first time on saving the PO,version is creating automatically,
second time,if we do changes, version is not creating on saving the purchase order,what configuration needs to be done.
Please suggest.
Regards,
Magana

Also tell me the use of *Display of change documents in PO*.
It will display changes made both in item & header.It will help you to audit all changes made in p.o after it is raised.
In version management not all changes can be ameneded as seperate versions
only critical changes like price revision,quantity revision.

Version management of Purchase orders

Hi,
In the version Management for the perchase order can anyone tell me what is the use of following:
Materials Management - > Purchasing-> Version Management-> Set Up Change Displays

Hi,
In this work step, you can specify whether and in which change displays.
(E.g. for version via @II@) a certain field is to be displayed.
In ME22N or ME23N, under Version tab, once you click on "Display Changes" button then system will display you the changes of the those fields only which have been defined in this step.

Activate Version Management in Purchase Order

Dear All Expert,
Current Condition, Version Management will be activated once the PO has been full released (using t-code ME29N) and then printed (using t-code ME9F).
Problem:
Condition in our client that they only need particular document that will be printed, so not all PO will be printed.
Based on this condition our client tends to activate Version Management once PO is approved/released (using t-code ME29N) without need to be printed.
Hope anyone could help me to solve this problem.
Thanks,
Franz.

Is there anyone who can help my problem, about Version Management

Version Management in Purchase Order

Hi All,
I need to display items in PO form according to version.
Can anyone tell me how can I track changes in PO item and display only the changed or newly added item??
Urgent
Regards
Vijai

HI,
The print output is not affected by the version control.
The document printed will always reflect the changes made since the last print.
You cannot even select an older version and print that.
So please don't expect the output functions to have been affected by the new version control functionality, it does not change the way that prints (outputs) are managed, you always get the current printout.
Steve B

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

Business Content for Funds Management and Purchase Orders

Dear all
Our controlling department asks me to have SAP Funds Management and Purchase Order reporting in BW and thus BO. SAP standard report FMRP_RFFMAV01X shows pretty much what they would like to see: Distributable Budget by Funds Center and how it got spent by the Purchase Orders.
I tried to find what SAP BI content can offer. I found for example DSO 0BBP_PO in the "Enterprise Buyer" BI content, but this only shows purchase orders. On the other hand, cube 0PU_C02 shows funds line items, but nowhere a reference to the Purchase orders.
Could anyone advise if there is something in the BI content combining FM and PO?
thanks a million for your help
Josef

Hi Josef,
The Functional cosultants in the Team should be able to answer this as to how the integration has been done and the respective tables.
In case there is no STD datasources then you can build a view of Generic Datasource based on the Tables Recommended by the FC Team.
Also check how Fundcentre is mapped in MM module,like it may be same as Profit centre or Plant.
In that case get both the data in BW and build a MP/IS and report for both the KPIs...Amount Alloted and Amount Spent ,if drill down is require then show the POs.
rgds
SVU

Kits management in purchase order

Dear all,
I have to manage the following case.
We have material A and material B; the vendor has to produce the two materials together and so he has to sell them together.
But in my production model the consumption of A and B are not the same, and so sometimes it happens that the RdA are created by MRP only for one material (es. A).
I would like that during creation of purchase order the system insert an item for material B (A and B is like a kit), too.
Do you have some ideas?
regards
Flavia Borselli

Hi,
Create BOM using T.code CS01- A as BOM, and A, & B as components.
Stock type-L, Procurement type-F, Sp prcmt-30 for subcontracting.
Based on the qty requirement of B, create Alternative BOMS using the same BOM usage.
You may try this and confirm the result.
Thanks..

Possible version conflict, sending purchase order to SUS in MM-SUS scenario

We are currently trying to get the MM-SUS scenario working. In this
scenario, we create a purchase order in the ERP/MM system. The
purchase order is then transferred into SUS via XI/PI.
After creating a purchase order in the MM system, the purchase order
reaches the SUS system, but then errors-out in the SUS system upon
posting. The specific error is paraphrased as follows:
No interface action for sender or receiver found (from Trace)
PARSE_APPLICATION_DATA
CX_ST_MATCH_ELEMENT
System expected the element http://sap.com/xi/SAPGlobal20/Global;
PurchaseOrderRequest
We suspect a version conflict. The SUS version is 7.01. The XI/PI
system is version 7.11.
Can you confirm or rule-out a version conflict?
The Integration Builder scenario we are using is Plan
Driven Procurement with Supplier Enablement.
We have tryed many variations in Integration Builder, but all
produce errors in SUS. The test tool in Integration Builder also shows errors
for certain message types. The message type ORDERS.ORDERS02
needed to be added manually, and did not come along with the scenario.
Edited by: Bill Guderian on Mar 19, 2010 4:53 PM

Any clue from here.
Note 936003 - ERS Invoice causes conversion error within SRM
When the SRM system attempts to process an ERS Invoice sent from the MM backend, a PARSE_APPLICATION_DATA CX_ST_DESERIALIZATION_ERROR fault is thrown.
Other terms
CX_ST_DESERIALIZATION_ERROR PARSE_APPLICATION_DATA SUS SRM EBP ERS Invoice XI Exchange Infrastructure Mapping
Reason and Prerequisites
This error will occur when the IDOC does not have a VPREI value; it is the result of an error within the divide logic of the XI mapping operation. This operation is performed within the XI system. A calculation of NETWR/MENGE is performed; however, the result is not properly formatted. As such, 72.30/10 produces a result of 7.2300002. This value is too long for the inbound SRM proxy and hence the error is thrown.
Solution
The solution to this problem is to add a FORMATNUM function within the XI mapping operation. This restricts the result to 2 decimal places, which adheres to the definition of the inbound proxy.
Step by step directions on how one implements the FORMATNUM function are as follows:
1. Log into the XI system with SAPGUI
2. Start the Integration Builder:Design tool (for steps on how to do this, review the steps below):
    a. Run transaction sxmb_ifr
    b. This will cause a browser to come up. Select the Integration Repository link
3. In the left pane, select the Objects tab
4. Navigate to the SAP SRM SERVER ' SAP SRM SERVER 5.0 ' http://sap.com/xi/SRM/SupplierEnablement/Global --> Mapping Objects --> Message Mappings folder
5. Double-click on MM2SUSInvoice
6. The right pane will display the mapping object
7. Select Edit mode
8. In the box that contains the output (Message Type: InvoiceRequest), navigate to InvoiceRequest ' Invoice ' Item ' Price ' NetUnitPrice
9. Double-click on the Amount element and you should see the mapping, represented graphically in the bottom pane
10. In the status line of the graphical editor, select Arithmetic from the list box:
11. To the right of the listbox, scroll until you see the FormatNum function
12. Click on FormatNum, which will cause the function to be added to the graphical editor. You may drag the box as desired
13. Select the connection that binds the if/then/else to the Amount box by grabbing the arrow within the input of the Amount
14. Release the drag of the connection while over the input to the FormatNum box. This will reassign the output of the if/then/else to the input of FormatNum
15. Create a connection between the output of the FormatNum box and the input of the Amount box. You accomplish this by clicking within the output and releasing within the input (respectively).
16. Save the modified mapping object
17. Activate the changes
    a. In the left pane, select the Change Lists tab
    b. Navigate to the Standard Change List entry
    c. Right-click the Standard Change List entry and select Activate
    d. Select only MM2SUSInvoice if more than one item is available, and press the Activate button
18. This will complete the required modification.

Cash management - MM purchase order

Dear Gurus,
Presently I am working on Cash Management, I have an issue to configure the PO to cash Managemnet. Please provide me config steps. Please forward the same to my email id: [email protected]
Thanks & Regards,
Chandrasekhar

Thanks for your response. I have read 9859 note. Here is the explanation how integration of MM/SD and CM is realized.
But the question is:
PO data is updated in the CM. Data of PO positions appear in CM. If in PO position VAT deductible is selected amount without VAT appears in the CM. But the outflow cash planning we should do with Amount + VAT.
The note 9861 says how this problem can be solved. But it is not good solution (much manual work). It should be updated correctly during PO saving. I do not know, my be somewhere in the Functional models (mentioned in 9859 note). But it is not possible without crushing standard system.

Problem in Purchase order version management

Dear Guru,
My Friend i have some problem in version management in Purchase order, when my user changed PO new version created, then user fill the data like reason, text, requested by but he forget about the tick mark on completed field so that PO not require new release.
can u suggest how i can mandetory this completed field
Regards
Kashyap Kumar

Hello,
In version management..the tick is mandatory.... and remaining fields are not manadatory.......
Mahesh

Version Management

Dear Sirs,
We have activated version management for purchase orders.
Purchase Orders are made in the system and printout of the same are being taken from the print preview screen before the release of the PO.
If some changes are made in the PO after the release of the PO, the sytem does not activate the version management. Reason: no messages were issued after the release of PO.
Is it possible that when a print out is taken, the system automatically processes the output message, whether the PO is released or not.
Viral Bhinde

Hi Viral,
I got ur problem.
As you said when you make changes to PO system set new release strategy as well as new version. It is expected that whenever there are changes in PO it should be communicatted to Vendor thru PO print.
In your case ur PO created new version as well as new release strategy. And you tried to take print before PO release. Please first release the PO and take print thru ME9F. That message will disappear.
Plz let us know if there is further problem.
Thanks
Nilesh

Block Purchase Order to be changed once Service Entry Sheet is created

Hi All,
I need help, i want to know how can i block the PO not to be changed once the service entry sheet is created. For example : Once the user create a service entry sheet with a released PO it must not allow her / him to change the PO.
Thanks,
Rosina

Set the Release Indicator for Purchase Order Release Strategy such that it will not allow to change once Released.
Else Configure Version Management for Purchase Order.

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

Internal Data Transfer to Funds Management - Version Management Error

Hi All,
We are trying to convert the open PO's in our system that were created before FM was implemented, and that are to be converted now before the MIGO stage.
We are using the following steps:
1) Select the document
2) Convert the worklist.
We had done the first step, and faced no issues. During the conversion of the worklist, we face the following error
Message ID - MEPO;Message Number - 813; Version Management of purchase order still faulty.
Message ID - MEDCM; Message Number - 4; Enter short text for version
Message ID - MEDCM; Message Number - 3; Enter reason for change for version
In the Control Data for each of the Document Type, the control data, Version Active and Version 0 OK are activated.
Can someone kindly suggest what could have possibly gone wrong here ?
Regards,
Wy

Hi All,
Just to clarify, I went through note 800784 and found that in our system
1. None of the fields - 'Reason,' 'Description,' 'Req By,' 'Req By Ext' or 'Post Date' - is a required entry in the version management field selection
2. None of the fields - EKPO-ELIKZ or EKPO-EREKZ or EBAKZ - are set as Version-Relevant Fields of Purchase Requisitions.
Cant figure out why I am not able to assign the fund centre and commitment item here, although I am able to perform MIGO and MIRO on that.
Regards,
Wy

Version managment in purchase order's

Similar Messages

Maybe you are looking for