Item level Workflow Hold..

Hi,
i am working an item-level SC workflow
( WS14500015 ). i would like to know is there any way to hold the last step which in workflow template is using for create follow on document in backend system, until i will recieve some text data from thrid party system and needs to be restarting again the particular step which i hold after i recieved the text data from third party system.
give some hints to fix.
regards,
john.

Hello,
No change is needed in WS14500015.
WS10400051 is the final processing sub-workflow used by all standard workflows in SRM. Navigate through workflow builder, you'll find it is called in the line item app workflow: it's the final proccessing. Depending on the approval status of the SC, it updates its status and follow on document are created.
To work safely, first generate a new version for this workflow (WS10400051) before any change.
Idea is to extend bus2121: create a subobject and activate delegation, define a new event on sub object.
In wf definition, insert a event waiting step linked to the SC number and new event just before the task "set release status".
I guess that receiving the third party text is made in specific. Use the function module swe_event_create to genrate the new event of object bus2121 for the concerned shopping cart.
when this event will be generated, the final processing workflow will continue.
Hope it helps,
Pierre

Similar Messages

SRM Item level Workflow

Hi All Workflow Experts,
I have started developement of Item level Approval WF in SRM.
Can anybody help me what are the steps I need to follow for development.
Currently I am able to get the approval step but Approvers are not coming. some step missing i guess.
In the Item level WF I need to do following things
1) first 3 levels will be the header level approval
2) next 2 steps will be item level approvals
And this workflow should have all the functionality of standard WF of SRM.
I dont know how to achieve this. I am very new in WF.
Any help will be awarded
Thanks
Smita

Hello,
First you can check the sample implementation to get start.
Item level approval works with 3 tables that are sent to worklow instance each time the document (SC or PO) is changed (or created) :
- "object" table that define the object to be approved and their criteria (3 possible)
- "item" table that link item to approval object
- "approval" table that contain that define for each approval level the approver and the object to be approved
Stay close to the sample implementation to generate the 3 tables and it should be fine.
Now, if all items are linked to the same approval object, it is like a header approval (for your first three steps).
In the badi:
An import parameter "approval_index" in the badi indicates you at wich step the workflow stands. Consider that that you only need to send the following steps including the current step (actual index).
In general: check notes and make the system be very up to date concerning workflow correction
Rgds,
Pierre

System is not picking up approvers from BADI in Item level workflow

Hi All,
My problem is that
1. when I creat the shopping cart the system is picking up the correct approver from BADI and showing it in approval preview.
2. My first level approver is a general task so Workitem going to the correct persons.
3. after first level approver I am fillng approver in BADI for 2 nd level.
4. But after first approval the SC is directly getting approved finally as system is not picking up approvers from the BADI.
I dont understand the problem. even We applied SP9 as well, but the problem is not resolved.
Please suggest something.
Thanks
Smita

Hi ,
I am pasting the code of my BADI. Let me know if i need to do some changes.
Regards,
smita
if lv_wf = '4'.
1st approval step executed for indices 1 and 0
      IF actual_approval_index LE 1.
First approval step (General task)
endif.
2. approval step executed for indices 2,1 and 0
      IF actual_approval_index LE 2.
*break-point.
**get the approver for the commodity
         LOOP AT lt_item INTO ls_item WHERE del_ind IS INITIAL.
We consider only items, which are not deleted (del_ind = 'X')
Set the product category
            MOVE ls_item-category_id TO lv_call_value1.
Find the approver of this item based on the customizing table ZCOMMODITY
CALL FUNCTION 'ZWF_COMODITY_ITEM_APPROVAL_GET'
   EXPORTING
     SC_GUID                          = ls_header-guid
     ITEM_GUID                        = ls_item-guid
   APPROVAL_DESCRIPTION             =
    HIDE_ITEMS_NOT_RESPONSIBLE       = 'X'
     CRITERION1                       = 'COMMODITY'
     CATEGORY_ID                      = ls_item-category_id
     ITEM_VALUE                       = ls_item-VALUE
     APPROVAL_INDEX                   = '2'
   CHANGING
     APPROVAL_TABLE                   = approval_table
     ITEM_APPROVAL_TABLE              = item_approval_table
    ITEM_APPROVAL_OBJ                = item_approval_obj
endloop.
*ELSEIF actual_approval_index EQ 2.
don't process 2nd step
         no_further_approval_needed = 'X'.
endif.
endif. " if lv_wf = '4'.
FUNCTION ZWF_COMODITY_ITEM_APPROVAL_GET.
""Local Interface:
*" IMPORTING
*"     VALUE(SC_GUID) TYPE BBP_GUID
*"     VALUE(ITEM_GUID) TYPE BBP_GUID
*"     VALUE(APPROVAL_DESCRIPTION) TYPE BBP_STEP_DESCRIPTION OPTIONAL
*"     VALUE(HIDE_ITEMS_NOT_RESPONSIBLE) TYPE BOOLEAN OPTIONAL
*"     REFERENCE(CRITERION1) TYPE BBP_WFL_APP_CRITERION
*"     VALUE(CATEGORY_ID) TYPE ZBBP_CATEGORY_ID
*"     VALUE(ITEM_VALUE) TYPE BBP_VALUE
*"     VALUE(APPROVAL_INDEX) TYPE SWH_NUMC10
*" CHANGING
*"     REFERENCE(APPROVAL_TABLE) TYPE BBPT_WFL_APPROVAL_TABLE_BADI
*"     REFERENCE(ITEM_APPROVAL_TABLE) TYPE BBPT_WFL_ITEM_APPROVAL_BADI
*"     REFERENCE(ITEM_APPROVAL_OBJ) TYPE BBPT_WFL_ITEM_APPROVAL_OBJ
*"       OPTIONAL
this Function Module is for getting the commodity approvers
for the commodity items, in the Shopping cart
DATA:
    ls_approval_table      TYPE bbp_wfl_approval_table_badi,
    ls_item_approval_table TYPE bbps_wfl_item_approval,
    ls_approval_def        TYPE bbpt_wfl_lia_def,
    ls_item_approval_obj   TYPE BBPS_WFL_ITEM_APPROVAL_OBJ.
DATA:
    lv_app_obj_guid   TYPE bbp_guid_32,
    lv_is_new_approval_object TYPE boolean.
**structure for commodity data
data : ls_commodity type zcommodity.
data : lv_value1 type BBP_WFL_APP_PROPERTY.
CONSTANTS:
      c_agent_is_user TYPE otype VALUE 'US'.
First find the right approval object the item belongs to.
All items of an approval object are approved togheter in
this approval step, and therefore only one workitem is
created for this items. IF possible use this standard function
BBP_WFL_DIN_APP_OBJ_GET for creating the approval object.
lv_value1 = category_id.
CALL FUNCTION 'BBP_WFL_DIN_APP_OBJ_GET'
EXPORTING
    SC_GUID                      = sc_guid
    CRITERION1                   = criterion1
CRITERION2                   = ''
CRITERION3                   = ''
   VALUE1                       = lv_value1
VALUE2                       = ''
VALUE3                       = ''
IMPORTING
   APPROVAL_OBJ_GUID            = lv_app_obj_guid
IS_NEW_APPROVAL_OBJECT       =
TABLES
    ITEM_APP_OBJ                 = item_approval_obj
              CALL FUNCTION 'BBP_WFL_DIN_APP_OBJ_GET'
                EXPORTING
                  SC_GUID                      = sc_guid
                  CRITERION1                   = criterion1
                 CRITERION2                   = ''
                 CRITERION3                   = ''
                 VALUE1                       = lv_value1
                 VALUE2                       = ''
                 VALUE3                       = ''
                 IV_ITEM_VALUE                = ITEM_VALUE
               IMPORTING
                 APPROVAL_OBJ_GUID            = lv_app_obj_guid
                 IS_NEW_APPROVAL_OBJECT       =
                TABLES
                  ITEM_APP_OBJ                 = item_approval_obj.
CALL FUNCTION 'BBP_WFL_DIN_APP_OBJ_GET'
   EXPORTING
     sc_guid                 = sc_guid
     criterion1              = criterion1
CRITERION2              = ''
CRITERION3              = ''
     value1                  = category_id
VALUE2                  = ''
VALUE3                  = ''
IMPORTING
If 2 items of the same shopping cart have the same
values for the criterias, this function returns the
same (!!!) approval object guid
    approval_obj_guid       = lv_app_obj_guid
   TABLES
This table saves the criterias for which the approval object
was created. For example:
|approval object1| "cost center" | 1000   |
|approval object2| "cost center" | 1200   |
|approval object3| "prod categ " | office |
    item_app_obj            = item_approval_obj
Check if this approval object already exists in the approval
table
READ TABLE approval_table INTO ls_approval_table
          WITH KEY approval_object_guid = lv_app_obj_guid
                   approval_index       = approval_index.
IF sy-subrc EQ 4.
    lv_is_new_approval_object = 'X'.
ENDIF.
IF lv_is_new_approval_object = 'X'.
Now read your own approval table based on your criteria's
**now check whether the category id is a commodity material and
*find the responsible person for that and
*check if the amount of item is falling in the approval limit of the comodity manager
select single * from zcommodity into ls_commodity
where CATEGORY_ID = category_id
and ( ZFROMAMT <= item_value and ZTOAMT >= item_value ).
   SELECT * FROM bbpt_wfl_lia_def
            INTO CORRESPONDING FIELDS OF ls_approval_def
            WHERE
                  app_crit_name1 = criterion1 AND
                  app_crit_value1 = value1
   ENDSELECT.
    IF sy-subrc NE 4.
Fill approval table (who is responsible for which approval
object in which approval step)
      ls_approval_table-approval_index       = approval_index.
     CONCATENATE c_agent_is_user ls_approval_def-approval_agent1
                             INTO ls_approval_table-approval_agent.
CONCATENATE c_agent_is_user ls_commodity-person
                              INTO ls_approval_table-approval_agent.
      ls_approval_table-name = ls_commodity-name.
      ls_approval_table-approval_description = approval_description.
      ls_approval_table-approval_object_guid = lv_app_obj_guid.
      ls_approval_table-hide_items_not_responsible =
                              hide_items_not_responsible.
      APPEND ls_approval_table TO approval_table.
     IF ls_approval_def-approval_agent2 IS NOT INITIAL.
Second approver for the same workitem exists
       CONCATENATE c_agent_is_user ls_approval_def-approval_agent2
                           INTO ls_approval_table-approval_agent.
       ls_approval_table-name = ls_approval_def-agent_string2.
       APPEND ls_approval_table TO approval_table.
     ENDIF.
    ENDIF.
ENDIF.
Fill item table (Which items belongs to which approval object)
ls_item_approval_table-approval_object_guid = lv_app_obj_guid.
ls_item_approval_table-approval_item_guid   = item_guid.
APPEND ls_item_approval_table TO item_approval_table.
**Fill Item approval object
ls_item_approval_obj-sc_guid = sc_guid.
ls_item_approval_obj-APP_CRIT_NAME1 = CRITERION1.
ls_item_approval_obj-APP_CRIT_VALUE1 = CATEGORY_ID.
ls_item_approval_obj-APPROVAL_OBJECT_GUID = lv_app_obj_guid.
append ls_item_approval_obj to ITEM_APPROVAL_OBJ.

Issue in N level workflow of shopping cart

Hi all,
SRM5.0 and ECC5, using ECS scenario
We are using the N level workflow ( SC approval workflow and not item level workflow) with the BADI for determining the approvers of the shopping cart.
The following are issues faced during rejection:
1. When the 1st approver rejects some of the line items and approves others, The SC is sent back to the requester or. the requester accepts the changes, the SC instead of going to the next level of approvers gets approved.
I have debugged and found that the actual index is set to 2 and the next level of approvers are determined correctly in the BADI, once it is out of the BADI, something happens and the SC is approved and it doesn't go for approval.
2. When the 1st approver approves all the line items and the 2nd approver does a partial rejection, the SC is sent back to the requester and once the requester accepts the changes, the workflow restarts and the approvers are redetermined again.
For the 2nd issue, if its a standard process, Can onyone provide me with a document or a OSS note which can be used for substantiating it. Does this behavior correspond to the back and forth process of N level workflow?
Thanks and Regards
Kishan

Hi Munna,
The code just determines the approvers for each level, this works fine when I debug but it changes after the control comes out of the N level BADI.
Is there any other check which I need to do?
Regards
Kishan

Workflow not triggering when changing Item-level Permissions in Sharepoint 2013 list

Scenario:
We have a custom list in Sharepoint 2013 that we use for Case Management. We have a workflow that triggers on a created item generated from an email. The user then gets a reply with a link to his own case.
I want the users only to be able to see their own cases and no one elses. When I change this under
Advanced Settings under List Settings and
Item-level Permissions and set them to Read items that were created by the user
and Create items and edit items that were created by the user
the workflow doesn´t trigger.
How can I resolve this? I've tried every possible out-of-the-box permissions but with no result. Help!
Thanks in advance!
// Browncreek

When you're testing , remember you cant trigger declarative workflow from the System Account - you need a general user account for auto-trigger workflows. Good luck!
Chris McNulty MCSE/MCTS/MSA/MVTSP | blog http://www.chrismcnulty.net/blog | twitter @cmcnulty2000 Microsoft Community Contributor Award 2011
Hi, I have the same problem. Except that I am not using an email to create a new item. The item is created by members of a SharePoint group that have Contribute access to the list. When use the same settings i.e.
Read items that were created by the user and Create items and edit items that were created by the user,
the workflow does not trigger. If I set it back to Real all items and Create
and Edit all items, it triggers the workflow.
Please help me resolve as I have rolled this out to pilot users and am having this trouble.
Thanks,
Vishal

Workflow - Header vs. Item level

Hello,
I am looking for some documentation / list of pros and cons of implementing header level workflow vs. item level. I understand that item level is more difficult to implement, but what are the benefits.
We are looking at two types of approval, financial approval and commodity based approval and I would like to understand more before making a decision.
Many thanks,
AR

Hi,
For your requirement,you can go for N step HEader level SC Approval Workflow.I have worked on a similar reqt and the agent determintation can be made flexible based on runtime values thorugh the BADi BBP_WFL_APPROV_BADI.
Advantages of header level WF is that its very flexible.Disadvantage is that some techincal problems require application of OSS notes e.g graphical Preview inconsistent.
I have not worked on Item level WF so cant comment on that.For more info ,pls refer the foll links:
http://help.sap.com/saphelp_srm50/helpdata/en/17/40a86c773d6c41801d78af1a34b90f/content.htm
http://help.sap.com/saphelp_srm50/helpdata/en/a3/a6a34098022a54e10000000a1550b0/content.htm
Useful Workflow links ->
SRM Business Workflow
http://help.sap.com/saphelp_srm50/helpdata/en/8b/4fa9585db211d2b404006094b92d37/frameset.htm
Setting Up SAP Business Workflow
http://help.sap.com/saphelp_srm50/helpdata/en/ee/277e3c281f1817e10000000a114084/frameset.htm
Related links:
Re: SRM workflow doubts....
Triggering SRM workflow from a web-based form (HTML)
Workflow debugging
Re: Triggering an alert
BR,
Disha.
<b>Pls reward points for useful answers.</b>

Workflow for Changing Item Level Permission in SharePoint 2013 (Office365)

I am using OOTB Tasks List in SharePoint 2013 (O365). Now my scenario is like this:
I have two user groups: 1.Sales Managers 2. Sales Executives
Sales Managers can create & assign task to Executive. I want something like Sales Managers Can view all tasks (Which is by default view of tasks list i.e. perfact) but Executives can see only their tasks assigned to them. How can I achive this?
Can I use WorkFlow for this to Change item level permission or to assign permission to assigned to user? or JS
Can anyone have proper solution? thanks

1. make 2 SharePoint group 1>Sales Managers 2>Sales Executives
2. Show 2 WP of same task list in same page.
3. Use Audience Target for Sales Managers Sharepoint group in first Webpart property. (All
Iten view)
4. Show "My Task" view (assign to =[Me]) Bottom WP for same task list and use Audience Target for Sales Executives. Or if you want it to see
Sales Managers as well, the dont use any Audience Target.
Bottom line - SharePoint group use in Audience Target will do the trick. OOTB
Regards Sudip Misra [email protected] +1-412-237-5435 Pittsburgh, PA

PO Approval Workflow on item-level?

I have a requirement to implement an approval workflow when the price or cost center/internal order is changed on the purchase order.
The problem is that as I see it, standard SAP only allows approval on header level for Purchase Orders.
Is there a way to handle approval on item-level if for example the PO has 2 rows, we change the cost center on both these rows to different ones???
Based on this cost center, the approval should then go to the cost center responsible and then his boss and so on based on the org-structure.

Hi,
Consider a example , you have a PO and this PO has three items IT1, IT2, IT3. Based on the cost center, you want to send the respective item for approval to the respcetive KOSTL manager .
Desgin your workflow in this way.
1. Design a background activity step in and a BOR method where it returns you all the items of the PO and store these items in a multiline container element in the workflow container.
2. Now next to the above step include a [BLOCK step|http://help.sap.com/saphelp_nw70/helpdata/en/cc/18a8f409a93749b10e8dd9f9d81797/frameset.htm] in the workflow and choose par for each option and pass the items stored multiline container element. The use of the block step is it dynamically creates a parallel branches based on the number of rows in the multiline container element you mapped to the block step.
3. Now Inside the block step create another bor method and include a bacground activity step. Now in this BOR mehtod what ever the item you import try to determine the manager of the KOSTL(Cost Center.) and who ever is determined pass that user(s) name(s) back to the workflow container.
4. Next to this step include a decision step and choose the recipient type as expression and pass the container element in which the KOSTL managers are stored, in this way you can send based on the item cost center to its respective manager.
Regards
Pavan

Item level SC workflow in SRM 7

Hi all,
I am new to SRM 7.0.We have a reqt to implemnet the n step Item level approval workflow for Shopping cart based on the cost centre data in line items in SC.
Can some one explain me the steps how do I implement the above WF??
Which WF do I need to use in SRM 7.0??How is the BRF workfow implmenetation differenet than BADI workflow in SRM 5???
Where is the logic for approver determination to be defined in SRM 7??
Please advise.
Any helpful links to get started will be appreciated.

Thanks Masa...For the programming part,ABAP consultant can do it...But in case the WF goes into error,how is debugging to be done??
Also technically what are the advantages of workflows in SRM 7.0 compared to those which were used in SRM 5.0?

AD-hoc approver n step item level shopping cart workflow

Hi
We are on latest version of SRM and using n step item level SC approval workflow.
The scenario goes like this:
-     Requester creates shopping cart and workflow goes for two step approval.
-     In the approval preview the requester is able to see both levels of approvers, which is correct.
-     Requester now selects second level approver and replaces him with a ad-hoc approver. WE DO NOT WANT THIS. Requester should NOT be able to replace an approver determined by approval badi. However should be able to extend approval step with ad-hoc approver say third level approver a ad-hoc approver. Also he should be able to change AD-HOC approvers ONLY.
Thanks
Joe

Jo,
You may be able to achieve it in the BADI BBP_WFL_SECUR_BADI .
You can use the Business Add-In (BAdI) BBP_WFL_SECUR_BADI to determine whether
A shopping cart can be changed during the approval process
The approval workflow restarts when changes are made to the document
A reviewer/approver can be added or changedThese are the call scenarios (see import parameter SCENARIO).
Regards,
Suren

Re-starting Item Level Shopping Cart Approval Workflow

Hi All -
We are implementing WS 14500015 - the Item-based n-level approval workflow for shopping carts - for certain scenarios. In other scenarios we are using the overall approval workflow.
I need to re-start the item-level approval workflow for certain scenarios (change in price, change in quantity, etc) - not when any and all changes are made to a line item.
I was hoping to use the badi BBP_WFL_SECUR_BADI - which works great for the overall n-level shopping cart approval workflow. However, I can't seem to hit it appropriately for the item level approval workflow!
Does anyone know if this BADI or any other can be utilized for determining when to re-start the item-level shopping cart n-level approval workflow?
Thanks so much!
Abby

hi,
Have you implemented the badi BBP_WFL_SECUR_BADI ? for restarting the workflow?
Let me know?
Also it is possible to debug and see why the restart does not happen.
Also let me know wether the restart happens in other cases?

N level workflow. item level approval

Hello,
How does item level approval work in N level workflow ?
1) Suppose the shopping cart has 3 items then does the workflow proceed only after all the three approvers approve their items ?
2) Does the approval workitem stay in the approvers inbox will the time all are approved ? and if yes does the approved workitem appears differently ?
3) Does the approver see only his item or all other items too? if he does then are the other items greyed out?
4) What happens if or more of the approvers changes the contents of the item or rejects the item? Does the entire shopping cart again goes to the requestor and what happens to the other approver workitems ?
5) Is it possible to have shopping cart level approval workflows as well for N level workflow ?
Where can I find this information in sap help?
Kindly help its urgent !! thanks !!

Hi Rita,
Please see the links,it will help you.
http://help.sap.com/saphelp_srm30/helpdata/en/8b/4fa9585db211d2b404006094b92d37/content.htm
This will answer most of your questions
http://help.sap.com/saphelp_srm30/helpdata/en/5a/af5eff85d011d2b42d006094b92d37/content.htm
Regards,nishant

PR workflow for item level release (stock and non-stock)

Hello gurus,
I am not getting the agents.!!
I am creating a workflow for pr( item level release)..and using standard wf WS00000038 for this, as the standard wf contains the simple release procedure only but i have to add some custom steps to it, so i have copied this wf as custom wf .
In this wf i have to fetch the agents based on the "stock" and "non-stock items".
so i have maintained strategies and release code like:
i have maintained two strategies W1(non-stock) and W2(stock)..and release code for W1 are P1 and P2..here P1 i have given for my first level of approval and P2 for second level of approval.
The release code for W2 are P3 and P2..first level is P3 and second is P2.
so what i have did in a workflow , started with a condition step where i have given "releasecode = p1".. if yes than than it will go for getting approval from p1 , in this activity i am using standard rule 157.
The main thing is 1). i am not getting how to fetch agents using standard rule. 2)and how and where to define next level of approval for both stock and non-stock.
means by using condition step in the starting i am dividing workflow in two parts stock and non stock but how to proceed next.
i am really confused. should i use rules or write my own methods. please if anybody has gone through the same scenario than please suggest some points. i will really appreciate the help.
Kind Regards.
Himanshu

Hello HIM Joshi !
                   Include the task TS00007986 and all its branches and in a loop and loop around it for two times.When the loop goes for the first time, it should pick the first agent and during its second iteration, it should pick the second agent.
                   To accomplish so, In the same loop, but before the above task , include a background task which should populate the agent ids depending on stock and non-stock details and pass it to the the task TS00007986
                   That's all.
Regards,
S.Suresh

PR workflow (item level)

Hello gurus,
I am not getting the agents.!!
I am creating a workflow for pr( item level release)..and using standard wf WS00000038 for this, as the standard wf contains the simple release procedure only but i have to add some custom steps to it, so i have copied this wf as custom wf .
In this wf i have to fetch the agents based on the "stock" and "non-stock items".
so i have maintained strategies and release code like:
i have maintained two strategies W1(non-stock) and W2(stock)..and release code for W1 are P1 and P2..here P1 i have given for my first level of approval and P2 for second level of approval.
The release code for W2 are P3 and P2..first level is P3 and second is P2.
so what i have did in a workflow , started with a condition step where i have given "releasecode = p1".. if yes than than it will go for getting approval from p1 , in this activity i am using standard rule 157.
The main thing is 1). i am not getting how to fetch agents using standard rule. 2)and how and where to define next level of approval for both stock and non-stock.
means by using condition step in the starting i am dividing workflow in two parts stock and non stock but how to proceed next.
i am really confused. should i use rules or write my own methods. please if anybody has gone through the same scenario than please suggest some points. i will really appreciate the help.
Kind Regards.
Himanshu

solved

PR item level Release WorkFlow

Hi Experts,
I have activated PR item level release WorkFlow WS00000038. My MM consultant has configured release strategy with ME51N. The Work flow works fine On releasing it sends notification work item to initator but on release Refusal it don't send notification work item to initator. Can anyone guide me how to resolve this issue.
TS00007986 SINGLERELEASE
4 Outcomes of release
1) Positive Confirmation
2) Negative Confirmation
3) Confirmation Release Cancelled
4) Purchase requisition item significantly changed
Now 1) posative confirmation is working fine.
but when we reject release then in that case also the workflow log it is going in undefined output that is significantly changed.
can anyone help me to resolve this issue.
Regards,
Hari

Hi Hari,
When you reject a PR, 2 events are getting triggered (Significantly changed and rejection_started). You check this in Transaction SWEL by rejecting PR.
The reason why output is going to Significantly changed branch is in SWEL you can see that 1st Significantly changed event is getting triggered and then Rejection_started.
Solution1: Deactivate the Significantly changed event in termination events tab.
Solution2: Create an attribute(Database object) for your business object. This attribute should be of type EBAN-BANPR. Check if BANPR = 08 and then send the rejection mail.
I hope this clears your doubt.
Please Revert back to me if you have any queries.
Regards,
Gautham Paspala

Item level Workflow Hold..

Similar Messages

Maybe you are looking for