Running More Than One Function Module Using SE37

When we are testing BAPI, we need to run the BAPI Transaction Commit as well.
We can do that simultaneously using SE37. This is how we do it.

For example, we are going to run BAPI_GOODSMVT_CREATE (Create Goods Movement) and BAPI_TRANSACTION_COMMIT (Commit Transaction)

Step 1: Select Function Module > Execute > Test Sequences

Step 2: Fill in all the Function Modules

Step 3: Execute

 The result:

Internal Table Definition in Smartforms

This is a sample of how to declare an Internal Table in Smartforms.

Step 1:
Global Settings > Global Definitions > Tab: Types
Declare:
TYPES:
  BEGIN OF ty_fixed_text,
    num   TYPE zcmtsd_text_inv-num,
    text   TYPE zcmtsd_text_inv-text,
  END OF ty_fixed_text.

Step 2:
Global Settings > Global Definitions > Tab: Global Data
Variable Name: T_FIXED_TEXTS
Type Assignments: TYPE TABLE OF
Associated Types: TY_FIXED_TEXT

PO Release Strategy Step-by-Step

By Gowri Shankar, HCL Technologies

This document describes step-by-step procedure for triggering workflow while creating a PO.

Depends on PO value, it selects the level of approver one or two level. 

Step1:

First we need to set the PO Release strategy.

Go to transaction SPRO. 

 

Step 2: Click SAP Reference IMG. 

 

Step 3:

Choose Material management à Purchasing à Purchase order à

Release Procedure for Purchase order à Define release Procedure for Purchase Order. 

 

Step 4: The following screen appears. 

 

Step 5: First let us set the release group 

 

Press save and come back. 

Step 6: Now the screen looks like this. 

 

Step 7: Now select the Release code. 

 

 

Step 8: After Release Codes, now select Release indicator.

Step 9:  

Next you need to set the release strategy. 

 

On double-clicking the record, the following screen appears. Here you need to set the conditions. 

 

Step 10 :  

Finally you need to set the workflow strategy.

 

Save your entries.  

 

Now the release procedure is configured. 

1) Go to transaction SWDD and open the standard SAP workflow definition WS20000075.

 

2) To tailor the workflow definition as per our requirements, let us take a copy of the standard workflow definition and modify the same. 

 

3) After that give the name for standard workflow. 

 

 

 

4) Now a copy of the standard workflow is available. We can modify this workflow definition as per the client requirements. 

 

 

5) Note the workflow definition id. Go to the transaction PFTC.

 

6) Select the task type as Workflow template.

And task as 99900281(workflow definition id). Next click the change button. 

 

7) Select the tab “Triggering events”. (The alternative method for getting into this screen is by selecting Basic data (Hat symbol on the application toolbar) in the workflow definition) 

 

8) Select the step and select “Call binding editor”. 

 

The Following screen appears. Do the check and activate it. 

 

Step 9 : 

 

 

Step 11 : Go back to the earlier screen and activate the event.

 

The event linkage is now activated. 

 

Hereafter whenever a purchase order is created, the workflow is automatically triggered.