Scribd
Upload
1K views11 pages

Calling Tcode As A Link in Work Item As An Attachment Object

The document provides steps to create a business object that calls a transaction code (Tcode) as a link in a workflow attachment. It involves: 1. Creating a business object with an event and method to call the Tcode 2. Configuring the business object and workflow container 3. Creating a user decision step in the workflow with a container for the business object 4. Executing the workflow which displays the Tcode as a link that can be clicked to navigate to the transaction.

Uploaded by

Balbino Soares
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
1K views11 pages

Calling Tcode As A Link in Work Item As An Attachment Object

The document provides steps to create a business object that calls a transaction code (Tcode) as a link in a workflow attachment. It involves: 1. Creating a business object with an event and method to call the Tcode 2. Configuring the business object and workflow container 3. Creating a user decision step in the workflow with a container for the business object 4. Executing the workflow which displays the Tcode as a link that can be clicked to navigate to the transaction.

Uploaded by

Balbino Soares
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 11

Calling tcode as a link in work item as an attachment

object
created by Aravindan Aravi on Jul 1, 2013 10:41 AM, last modified by Mariana Mihaylova on Aug 22, 2013
12:09 PM

Step 1 : Create a BO as shown below.

Create an event and a method.

Step 2 : Method of Name DISP and its properties are shown below.
Step 3 : Flow logic inside the method , Here we are simply just calling se11 tcode.

Step 4 : Now go to basic data of business objects and change the default method as DISP method as
show below.
Click on f4 and change the default method as DISP:

Step5 :Now activate and generate the BO by making its status as implemented and released.

Step 6: Go to swdd , create a workflow.

Create a workflow container of type above BO.


Go to properties tab and make it as importing , Exporting.

Step 7: Now click on basic data tab.

Give the category as BO and object type as BO name and the event as FIRE.

Step 8: Now go to binding and click on automatic binding.


Step 9:Now come back and check all are in green state , if not activate by clicking on it.

Step 10: No go back and create user decision step.

After creating user decision step , copy the standard user decision step into your custom task.

For coping standard task check this link.

http://****************/Tutorials/Workflow/CustomText/CustomText.htm
Step 11: Put your custom task number in place of standard task number.

Step 12 : Click on the task and go inside .


Step 13:

Go to the container tab and create a container element of type bo : as shown below.

Step 14: Create a element of type BO which we have created.


Step 15: No come back to the work flow and click on binding.

Click on automatic binding.

Step 16: Now click on tick mark and save , activate the workflow.
Now workflow will look like this.

Step 17: Execute the workflow.

Give some value in the instance.


Step 18: Click on execute.

Step 19: Now click on the link which is on the objects and attachments side.

Which will navigate to the tcode : in our case we gave se11.


step 20: Now click on back it will return to the user Decision step .

Hope it helps.

http://scn.sap.com/docs/DOC-43386

You might also like