Documente Academic
Documente Profesional
Documente Cultură
COPYCODESAP
A SAP system based approval which notifies business users to login to SAP and approve a particular
document or a part of it.
https://copycodesap.wordpress.com/2016/06/27/purchase-requisition-workflow/ 1/23
3/8/2019 Purchase Requisition Workflow – copycodesap
Remove the unwanted activity and keep which ever you want.
https://copycodesap.wordpress.com/2016/06/27/purchase-requisition-workflow/ 2/23
3/8/2019 Purchase Requisition Workflow – copycodesap
When you click the binding you find the below screen.
https://copycodesap.wordpress.com/2016/06/27/purchase-requisition-workflow/ 3/23
3/8/2019 Purchase Requisition Workflow – copycodesap
Now if you double click the task it goes to the screen “Basic data” and you give the Object type and
the method.
Lets see how to find the object type and create linkage first then shall comeback to the activity.
https://copycodesap.wordpress.com/2016/06/27/purchase-requisition-workflow/ 4/23
3/8/2019 Purchase Requisition Workflow – copycodesap
Go to Tcode BAPI
https://copycodesap.wordpress.com/2016/06/27/purchase-requisition-workflow/ 5/23
3/8/2019 Purchase Requisition Workflow – copycodesap
The third option would be to run SWELS/SWEL TCode. Execute the purchase order Tcode and find
in the SWEL about which Object type is triggered.
Since we have got the object type through the above mentioned approach now we are now going to
create the linkage by replacing the standard linkage. Go to TCode SWE2 and find the Object type
BUS2012.
Copy the standard BUS2012 and place the newly created workflow (WS99400002) in the receiver type
and mark the linkage. Now the linkage is created.
https://copycodesap.wordpress.com/2016/06/27/purchase-requisition-workflow/ 6/23
3/8/2019 Purchase Requisition Workflow – copycodesap
Now delegate the Object Type so that you can change/add methods in the standard Object type.
https://copycodesap.wordpress.com/2016/06/27/purchase-requisition-workflow/ 7/23
3/8/2019 Purchase Requisition Workflow – copycodesap
After delegation, you can create/add a new method for your requirement in the object type
ZBUS2012.
https://copycodesap.wordpress.com/2016/06/27/purchase-requisition-workflow/ 8/23
3/8/2019 Purchase Requisition Workflow – copycodesap
https://copycodesap.wordpress.com/2016/06/27/purchase-requisition-workflow/ 9/23
3/8/2019 Purchase Requisition Workflow – copycodesap
https://copycodesap.wordpress.com/2016/06/27/purchase-requisition-workflow/ 10/23
3/8/2019 Purchase Requisition Workflow – copycodesap
https://copycodesap.wordpress.com/2016/06/27/purchase-requisition-workflow/ 11/23
3/8/2019 Purchase Requisition Workflow – copycodesap
https://copycodesap.wordpress.com/2016/06/27/purchase-requisition-workflow/ 12/23
3/8/2019 Purchase Requisition Workflow – copycodesap
Go back to the previous page and click program. Below is the program.
SELECT SINGLE smtp_addr FROM adr6 INTO lv_email WHERE addrnumber = lv_adrnr AND pers
number = lv_prnum.
client = sy-mandt
id = ‘ZTXT’
language = ‘E’
name = ‘ZGO_PO_SUBJ’
object = ‘TEXT’
* ARCHIVE_HANDLE =0
* LOCAL_CAT =‘‘
* IMPORTING
* HEADER =
* OLD_LINE_COUNTER =
TABLES
lines = it_text.
REFRESH :it_text[].
CLEAR : lv_ebeln, lv_frggr, lv_objid, lv_prnum, lv_adrnr, lv_email.
end_method.
https://copycodesap.wordpress.com/2016/06/27/purchase-requisition-workflow/ 15/23
3/8/2019 Purchase Requisition Workflow – copycodesap
https://copycodesap.wordpress.com/2016/06/27/purchase-requisition-workflow/ 16/23
3/8/2019 Purchase Requisition Workflow – copycodesap
Activity for fetching agent ID is done now lets go to the send activity on sending mail for approval.
https://copycodesap.wordpress.com/2016/06/27/purchase-requisition-workflow/ 18/23
3/8/2019 Purchase Requisition Workflow – copycodesap
Advertisements
REPORT THIS AD
REPORT THIS AD
JUNE 27, 2016JUNE 27, 2016
(HTTPS://COPYCODESAP.WORDPRESS.COM/2016/06/27/PURCHASE-REQUISITION-
WORKFLOW/) BY PRAVEEN ATHIKKAL
(HTTPS://COPYCODESAP.WORDPRESS.COM/AUTHOR/PRAVEENATHICKAL/) 2 COMMENTS
(HTTPS://COPYCODESAP.WORDPRESS.COM/2016/06/27/PURCHASE-REQUISITION-
WORKFLOW/#COMMENTS)
Karina says:
Dec 28, 2017 at 7:26 pm
Really useful guide, thank you!
I’m doing something similar to this, for release of contract (BUS2014), everything works fine for 1
level release but for releases with more than 1 level the WF is only triggered for the first level, I
executed a trace and I can see that the event RELEASESTEPCREATED is trigger just once, is there
any customization or something I can check that could be causing the problem? any suggestion?
REPLY
Praveen Athikkal says:
Jan 19, 2018 at 1:42 pm
https://copycodesap.wordpress.com/2016/06/27/purchase-requisition-workflow/ 19/23
3/8/2019 Purchase Requisition Workflow – copycodesap
Hi Karina,
Sorry, Been a long time since i checked my blog.
Not sure if you have fixed the issue or not. If not then would you mind to elaborate the issue
for my understanding.
REPLY
REPORT THIS AD
https://copycodesap.wordpress.com/2016/06/27/purchase-requisition-workflow/ 20/23
3/8/2019 Purchase Requisition Workflow – copycodesap
https://copycodesap.wordpress.com/2016/06/27/purchase-requisition-workflow/ 21/23
3/8/2019 Purchase Requisition Workflow – copycodesap
https://copycodesap.wordpress.com/2016/06/27/purchase-requisition-workflow/ 22/23
3/8/2019 Purchase Requisition Workflow – copycodesap
https://copycodesap.wordpress.com/2016/06/27/purchase-requisition-workflow/ 23/23