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

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.

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.

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.

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??

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

SRM 7.0 Output for changed purchase order documents

Hi all,
if we change purchase orders we like to send a PO output document for changed purchase orders only if we change certain PO fields in header or items.
What is the functionality in PO - Header - Output - Order and Send Immediatelly ? We thought that this function is the solution!
But independent we press the button <Order and Send Immediatelly > or button <Order> the system creates allways an output document in any cases of PO field changes which will be sent to a supplier (fax, email). How we can control that a PO document only will be created in cases we define ?
Kind Regards
Edited by: Hermann-Josef Wessels on Mar 28, 2011 6:53 PM

Hi Jay,
we like to control the output because PO changes for G/L account, cost centre or change from account assigment order to cost centre are not interesting for the supplier and in this cases a PO document should not be sent to the supplier. This was the main reason why we like to use function <Order and Send Immediatelly>.
So I would like to clarify the requirement:
1. Automatic created output document if a new PO will be created
2. Automatic created output document if a PO will be changed but no output if the following fields will be changed:
e.g. for G/L account, cost centre or change from account assigment order to cost centre
So we come back in our discussion to table: BBPV_COMP_FIELDS. There are entries for POO = PO Output and POR = Version comparison for Purchase Order.
Question: Can I use structure name: BBP_PDS_ACC for our requirement. If yes which field-names I have to maintain in detail in this table. If possible I need the entries in detail.
Kind Regards
Edited by: Hermann-Josef Wessels on Mar 30, 2011 9:20 AM

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

ESYU: Importing Standard Purchase Orders에서 문제 발생시 진단 방법

Purpose
Oracle Purchasing - Version: 11.5.10.2 to 12.0.6
Information in this document applies to any platform.
ConcurrentProgram:POXPOPDOI - Import Standard Purchase Orders
이 문서는 reader게 Importing Standard Purchase Orders 실행 중 갑자기 발생하는 issue에 대해 어떻게
대응하는지에 대한 자세한 정보를 제공한다.
Instroduction
Purchase Document Open Interface는 다량의 Standard Purchase Order는 Oracle Purchasing으로 빨리
import 할 수 있게 한다. Import process는 import 되어야 하는 document information을 PO interface tables에
넣어주는 작업을 필요로하며, data를 validate 하고 application에 PO를 생성하거나 error message를 return 하는
Import Standard Purchase Orders concurrent program을 실행한다.
이 문서의 목적은 Importing Standard Purchase Orders에 관련된 process를 이해하거나 갑자기 발생한 문제의
원인을 찾는데 도움을 주기 위함이다. PO import 문제는 일반적으로 interface tables에 입력된 불일치하는 data가
원인이며, 일단 문제가 확인되면 Metalink는 비슷한 문제를 찾아주거나 Oracle Support에 Service Request를 log
할 수 있다.
Test case Information
1. 아래 insert 문장을 이용하여 PO interface tables에 data를 입력:
INSERT INTO po.po_headers_interface
(interface_header_id,
action,
org_id,
document_type_code,
currency_code,
agent_id,
vendor_name,
vendor_site_code,
ship_to_location,
bill_to_location,
reference_num)
VALUES
(apps.po_headers_interface_s.NEXTVAL,
'ORIGINAL',
207, -- Seattle
'STANDARD',
'USD', -- Your currency code
24, -- Your buyer id stock
'Advanced Network Devices',
'FRESNO',
'V1- New York City', -- Your ship to
'V1- New York City', -- Your bill to
'Currency test') -- Any reference num
INSERT INTO po.po_lines_interface
(interface_line_id,
interface_header_id,
line_num,
shipment_num,
line_type,
item,
uom_code,
quantity,
--unit_price,
promised_date,
ship_to_organization_code,
ship_to_location)
VALUES
(po_lines_interface_s.nextval,
po_headers_interface_s.currval,
1,
1,
'Outside processing',
'Flooring OSP',
'Ea',
1,
--17.50,
'10-APR-2009',
'V1',
'V1- New York City' )
INSERT INTO po.po_distributions_interface
(interface_header_id,
interface_line_id,
interface_distribution_id,
distribution_num,
quantity_ordered,
charge_account_id)
VALUES
(po_headers_interface_s.currval,
po.po_lines_interface_s.CURRVAL,
po.po_distributions_interface_s.NEXTVAL,
1,
1,
12975) -- Your Charge Account Id
2. Interface tables에 data가 insert 되었다면 import progra을 실행전 정보를 확인하기 위해 아래 query 문을 이용한다.
a - Select * from PO_HEADERS_INTERFACE where INTERFACE_HEADER_ID=&headerid
b - Select * from PO_LINES_INTERFACE where INTERFACE_HEADER_ID=&headerid
c - Select * from PO_DISTRIBUTIONS_INTERFACE where INTERFACE_HEADER_ID=&headerid
3. Data를 review 했으면 Import Standard Purchase Orders program을 실행한다.
Parameter >>
Default Buyer: Null
Create or Update Items: No
Approval Status: INCOMPLETE
Batch Id: Null
4. 만일 program에 문제가 있어 error가 발생한다면 error의 원인을 제공하기 위해 Purchasing Interface Error Report를
실행할 수 있다.
Parameter >>
Source Program: PO_DOCS_OPEN_INTERFACE
Purge Data: No
만일 PO가 import 되지 않았다면 Puchasing Interface Errors Report와 동일한 정보를 보기 위해 Interface Errors table을
아래 SQL을 이용하여 조회할 수 있다.
SELECT * FROM PO_INTERFACE_ERRORS WHERE INTERFACE_TRANSACTION_ID ='&recordsinterfacetransid';
Diagnostics
Import Standard Purchase ORder process의 troubleshoot 도움을 위해 아래 Diagnostics과 Reports를 이용한다.
1. Diagnostics Tool : Oracle Purchasing Purchasing Documents Open Interface Data Collection Test
(please refer to Note 224887.1 for assistance)
이 Diagnostics는 import program에 의해 import 되는 data를 validate 할 것이며 missing 되거나 맞지않는 정보를 highlight 한다.
이 Tool은 interface tables에 있는 맞지 않거나 불완전한 data의 자세한 정보를 제공할 수 있다.
Error는 PO를 import 할 때 발생한 문제 분석을 시도하는데 매우 유익하므로 SR을 log시 이 Diagnostic output을 upload 하는
것을 권장한다.
2. Purchasing Interface Errors Report
이 report는 Oracle Purchasing에서 사용가능하며 Import Standard Purchase Orders program을 실행시 발생하는
error를 강조한다.
Tracing
11.5.10 이상의 version에서 Import Standard Purchase Orders program의 trace를 생성:
1. Navigate to System Administrator responsibility
2. Navigate to Profiles->System
3. Query the Profile Option Concurrent: Allow Debugging and set it to Yes at User level
4. Navigate to Purchasing responsibility
5. From the Requests form, choose the Import Standard Purchase Orders program and set the required Parameters
6. Click the Debug button
7. Check the SQL Trace checkbox and specify Trace with Binds and Waits
8. Submit the Concurrent program
9. Retrieve the trace file created.
Logging
Import Standard Purchase Orders program의 FND Deug Log 생성:
1. Log_seq를 아래 SQL을 이용하여 확인.
select max(log_sequence) from fnd_log_messages;
2. Set the following profiles at the user level:
FND: Debug Log Enabled = YES
FND: Debug Log Filename = NULL
FND: Debug Log Level = STATEMENT
FND: Debug Log Module = %
3. Run Import Standard Purchase Orders program
4. Using a SQL client run the following query :
Select * from fnd_log_messages
where log_sequence > &log_seq_noted_above
order by log_sequence;
이 query의 output은 Import Standard Purchase Orders program이 실행 중 발생한 error를 표시한다.
Reference
Note 781351.1

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.

Attachments to Purchase order via e-mail

Hi,
Im working on SRM5.5, Extended classic scenario,
I have a requirement where :
Right now , users can send Purchase Orders by mail to vendors but apart from the PDF version of the Purchase Order no other document can be attached to the email.
I have to attach an other document to this purchase order in PDF format and send it via email.
Could anyone tell me if there is any BADI for this ?
Any technical solution would be of great help.
Thanks and Regards,
Aravind Nair.

Hi Yann.
At this moment I have the a similar problem... In my case I'm woeking with MySAP Enterprise 4.7 and I want to send the PO and their attachament vía e-mail, currently only the PO is being sent to the Vendor and the attachment only appears like texts into the "body" of PO. Is there some way to send PO and attachments at the same time??
Thanks in advanced for your answer and help!!
Regards,
Blanca Reyes

Purchase order change blocking

hello all ,
I need to block the PO changes every week end (by Saturday) so that next week no body has to change PO Price since we we are following new price every week. Also we have release strategy for PO with workflow set up .
regards
Mike

Some Possible Solution for your Issue are :
Set Up Version Management for Purchase Orders so than no user can Change Relevant Fields.
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
Else Communicate with Basis Team and Remove Authorization for ME22N for all Users except Power Users.
Reg,
Ashok

How can I select alternative BOM when creating subcontract purchase order?

In our business, a finish good material always has different production versions at the same time. Each of production versions has its own alternative BOM. When I create a planned order, I can select wanted BOM through specifying production version.
But, when I creating subcontract purchase order, there is no field for me to specify the production version or which alternative BOM I prefer. In this case, I need to create a planned order at first. And then, convert the planned order to purchase. Only through this way, I can create a subcontract purchase order with my wanted BOM.
So, I wonder if there is any way to select alternative BOM directly when creating subcontract purchase order.
Thanks a lot!
Regards
Robbie

Dear Mr. MM
can you give me additional information about your solution?
BUT I would not expect the sytem to offer you during the Purchasing cycle the different Production Versions as it is not meant to be. I remember having the same requirement some time ago and we solved it the way I described above, additionally we created a Pop up window with a user exit during the PO creation which offered the different production versions and if the one linked with the quota arrangement, the standard PV, is used in the PO.
We also have the same problem, we activated businessfunction SCM_GEN_02 so that it is possible to have several production versions for one supplier, but unfortunatly it is not possible to change the production version in the purchase order. (business function does not seem to be very integrated)
So i would be very interested in your solution because acually it seems that i have to modify the sap standard.
Thank you and best regards
Lisa

Purchase Order - Version

Hi SRM Gurus,
After Ordering a Purchase Order, if we come out of the Process PO screen and after some time if again go and display the PO, System is showing second version. Due to which, in the Print out it is being displayed as Version 2, even though it is of version1.
Thanks & Regards,
Ramkumar

Dear Ramkumar,
SPRO > Material Management > Purchasing -> Version Management .
After activating version management you can see the Version tab in ME53N near to source of supply tab in PR.
http://help.sap.com/saphelp_47x200/helpdata/en/8a/60b43bb7492147e10000000a114084/frameset.htm
http://help.sap.com/saphelp_srm30/helpdata/en/46/882fdd8bfc1743bd5ef8b532f94402/content.htm
SAP Enterprise Buyer provides you with version management for purchasing documents. As a first step, you can display versions of purchase orders and contracts.
The system creates a version in the background if you, as a purchaser, carry out one of the following actions:
· You change a posted purchase order
· You order a posted purchase order again
· You change a contract that has already been released
· You release an already released contract again
In contrast to the change documents that retain a change history, a version displays the status of a document at a specific point in time.
Version management provides a check for you as a purchaser, for example, if you wish to display a purchase order in the form in which you transferred it to the vendor on day X. A version provides clarity, for example, in negotiations on a contract.
Features
You can use versions as follows:
· Display
· Compare and list differences in tabular form. The comparison result has separate areas that can be displayed:
Header data (including organizational data, tax and payment data; partner data and documents)
Item data (including taxes and limits if they exist; partner data, documents; account assignment and conditions)
· Archive, if it relates to transaction data (you can archive versions of purchase orders, but not contract versions)
You cannot change or output versions. This is only possible for the active document.
Also, visit the following thread:
Hope this will help.
Regards,
Naveen.

Version comparison in purchase order

Similar Messages

Maybe you are looking for