| Home • Tips • Tutorials • Sample Specs • Certification Q's • Interview Q's • Jobs • Testimonials • Contact Us | ||
Document Categories:
Email a FriendWhat's New?
Contribute?What's Hot? |
Determination of Release Code of PO and PRBy Argadip Kar, IBM India Workflow related to Change Purchase order: The Workflow is triggered by the Event ‘CHANGE’ of
Business Object BUS2012. The Change Event does not pass the ‘Release Code’
with it. We have to determine the Release Code Virtually by adding an Attribute
or putting the Code in the Method. There is no Standard Workflow for Changing of Purchase Order.
This is very useful when there is a requirement that approval is required for
non-significant changes in Purchase Order.
Each Purchase Order can have at the most 8 Release codes. The
Release Code is stored in table T16FS and is determined using the field FRGGR
(Release group) and FRGSX(Release Strategy). These two fields are obtained from
table EKKO (Purchase Order Header table). In this table we have to provide the
Purchase order number and we will get the field FRGGR (Release group) and
FRGSX(Release Strategy). Now how to determine which Release Code needs to be released.
The Release Code will be released sequentially in table T16FS. In table T16FS, 8
Release codes can be stored for a particular combination of Release group and
Release Strategy. The field FRGZU (Release status) determines which Release
Codes needs to be released. If the Release Status field value is ’X’ and
there are 3 Release Codes in Table T16FS corresponding to the Release group and
Release Strategy then the Release Code that needs to be released is the value
that is assigned to field FRGC2 in table T16FS. After the Release has been done
for Release code assigned to field FRGC2, we have to again pick the value of
field FRGC3 and Release it. Lets take an example of Purchase Order 4500017173. The
Release group for this Purchase Order is ‘ZR’ and Release Strategy is
‘GM’. Initially the Release status is blank, as none of the Release Code has
been released.
Continued in the following screenshot:
Lets find out how many Release codes are there for the
combination of Release group ‘ZR’ and Release Strategy ‘GM’. There are
three Release Codes for this combination. They are ‘PA’,’PM’ and
‘GM’ respectively.
Lets now try to release for Release Code ‘PA’.
After we have released the Purchase Order for Release Code
‘PA’ the Release Status should be ‘X’ in table EKKO for this Purchase
Order number. Let us check.
We should now try to Release the purchase order for Release
Code ‘PM’ by going to Transaction Code ME29N.
After we have released the Purchase Order for Release Code
‘PM’ the Release Status should be ‘XX’ in table EKKO for this Purchase
Order number. Let us check.
|
|
|
Please send us your feedback/suggestions at webmaster@SAPTechnical.COM Home • Contribute • About Us • Privacy • Terms Of Use • Disclaimer • Safe • Companies: Advertise on SAPTechnical.COM | Post Job • Contact Us ©2006-2007 SAPTechnical.COM. All rights reserved. All
product names are trademarks of their respective companies. SAPTechnical.COM,
Inc. is in no way affiliated with SAP AG. Graphic Design by Round the Bend Wizards |
||