Questionnaire 1. You change a purchase requisition. Why does the system not generate a new version?
2. You change a purchasing document (request for quotation, purchase order, contract scheduling agreement). Why does the system no
. You release a document (purchase requisition or purchasing document). You change the document and the system generates a new v ". You change the te#ts in a purchase requisition or a purchasing document. Why does the system not generate a new version?
$. You change the te#ts in a purchase requisition or a purchasing document. Why is a time stamp which has a date earlier than that of the &. What conditions need to %e met to set a version to !'n process!? ((utton )*et version in process)) +. You do not ,now what the -.-/0(1234 field is used for or how it is filled.
5. 't is possi%le to post a goods receipt for a purchase order if the current version of the purchase order has not %een completed yet. 6ow 7. You included the version num%er in the message form for purchase orders. Why is the num%er not displayed in the print preview?
18. 'f you attach a new document to a purchase order item or change an attached document, the system creates a new version and a cha found. 4he traffic light (in the message screen) displays status 2 (red). 4he message was processed unsuccessfully. 'n addition, you cann 00000000000000000000000000 1. Question: You change a purchase requisition. Why does the system not generate a new version? Answer:
4he system always creates a new version when the purchase requisition reaches a final processing state. 4hese are the following proces 3ctive, if no release is used .elease completed, if the release is used
;nly the following changes to a purchase requisition lead to a new version:
3ll version0relevant changes (defined in purchasing <ustomi=ing under 0> /ersion 9anagement 0> /ersion0.elevant ? <hanges to the document assignment
00000000000000000000000000 1. Question:
You change a purchasing document (request for quotation, purchase order, contract scheduling agreement). Why does the system not g Answer:
4he system always creates a new version when the purchasing document reaches a final processing state. 4hese are the following proce 3ctive if no release is used .elease completed if the release is used.
;nly the following changes to a purchasing document lead to a new version:
3ll print0relevant changes (defined in purchasing <ustomi=ing under 0> 9essages 0> ?ields .elevant to @rintouts of <h <hanges to the document assignment <hanges to time0dependent conditions
4o ensure that a new version is created for a purchasing document, all messages must %e transferred (see also Cote +&5$28). Co new versions are generated for purchase orders on hold. 00000000000000000000000000 1. Question:
You release a document (purchase requisition or purchasing document). You change the document and the system generates a new ver Answer: 4he system undoes the release when the version is !completed!. 00000000000000000000000000 1. Question: You change the te#ts in a purchase requisition or a purchasing document. Why does the system not generate a new version? Answer: 4his is not a change to print0relevant te#ts. 00000000000000000000000000 1. Question:
You change the te#ts in a purchase requisition or a purchasing document. Why is a time stamp which has a date earlier than that of the o Answer:
'f you change te#t in the current version, the system generates a te#t edition for this te#t which was already saved on the data%ase and th 00000000000000000000000000 1. Question: What conditions need to %e met to set a version to !'n process!? ((utton )*et version in process)) Answer:
'f the version is !completed! and if the documentDthe document item is not su%Eect to a release strategy, you can set the version to !in proc 'f the version is !completed! and if the documentDthe document item is su%Eect to a release strategy, you can set the version to !in process 00000000000000000000000000 1. Question: You do not ,now what the -.-/0(1234 field is used for or how it is filled. Answer:
4he -.-/0(1234 field (posting date of the version) was implemented on request of ?unds 9anagement. You can use this field to define 'f the field is a required entry field according to field selection, the system fills it with the current date. *ee 'nclude F9-2<99?81, method '?G.-/'*';CG93C3H-.G2<9I<.-34-G'4-9.
00000000000000000000000000 1. Question:
't is possi%le to post a goods receipt for a purchase order if the current version of the purchase order has not %een completed yet. 6ow ca Answer: *et the 9-2<9 81" or 9-2<9 817 messages as error messages in <ustomi=ing. 2ue to design reasons, the system cannot issue these messages as warning messages. 00000000000000000000000000 1. Question: You included the version num%er in the message form for purchase orders. Why is the num%er not displayed in the print preview? Answer
When the system issues the message, it also issues the version num%er. 4he print preview in transaction 9-7? also issues the version n 00000000000000000000000000 1. Question:
'f you attach a new document to a purchase order item or change an attached document, the system creates a new version and a change found. 4he traffic light (in the message screen displays status 2 (red). 4he message was thus processed unsuccessfully. You cannot disp Answer
4he system response corresponds to the system design. 'f you change a purchasing document, the system always carries out a messag transferred yet, the system does not create a new version even though you have changed a field that is relevant for printing. 4he !traffic li 00000000000000000000000000 1. Question: ... Answer ... 00000000000000000000000000 Other terms
Affected R Software Component *3@G3@@F "+8 Release "+8 From
Related N 74 4!" 9-$2C(: 'con for )3ttachments) is visi%le
Related N #4$%!# #"& '' #"$4 $ #"'!!! #$% &% #'##44 #'$$"4 #%&$#" #%"444 2<9 setting version in process, generating new version 2<9 9-21C 6olding purchase order, no version created 2<9 <hanging net order value, reset release strategy 9-$2C: 4e#t changes do not generate new version 2<9: <hange of doc. typeDpurchasing org. causes short dump 2<9 release determination if version in process 2<9: <ustomi=ing for change displays not ta,en into account 2<9: 3ctivation of the )(uyer approval) function 2<9: @.eq via 9-G.-J1'*'4';CG-K4, no release strategy
0 *ee more at: http:DDwww.stechno.netDsap0notes.html?viewLsapnoteMidL&&"725Nsthash.oaJ6m4n2.dpuf