WF start condition : PO type field in BUS2012

Hi all !
I am creating a Workflow process whenever a PO ( Order type NB ) is changed.
For this I am using the standard business object BUS2012 ( Purchase Order )
For my objective, I need to use the start Condition of PO type eq 'NB'. I go to Basic data and putting the start condition but I am not getting the PO type field in the Workflow Container. I have placed BUS2012 inside my workflow container. I am using the 'Changed' event.
What I have to do to get the PO type field or do I have to write a check FM ?
Could you please guide me how to put the start condition for the workflow ?
Thanks a lot,
~ The abaper

Hi,
Check in the BO BUS2012 if you have an attribute which stores the PO type field. If yes, you can directly use this attribute and chek its value in the start condition.
If not, then you can create a subtype of the BO BUS2012 and delegate the standard BO to this new Z BO.
Add a new attribute in the Z BO to store the value of PO type.
Now in the workflow start condition you need to check the value of the newly added attribute.
Hope this helps!
Regards,
Saumya

Similar Messages

Workflow start condition : PO type field in BUS2012

Hi all !
I am creating a Workflow process whenever a PO ( Order type NB ) is changed.
For this I am using the standard business object BUS2012 ( Purchase Order )
For my objective, I need to use the start Condition of PO type eq 'NB'. I go to Basic data and putting the start condition but I am not getting the PO type field in the Workflow Container. I have placed BUS2012 inside my workflow container. I am using the 'Changed' event.
What I have to do to get the PO type field or do I have to write a check FM ?
Could you please guide me how to put the start condition for the workflow ?
Thanks a lot,
~ The abaper
( Note : I have posted the same in Workflow forum as well, but no responses yet, I am trying here for a faster response, thnx )

>
The Abaper wrote:
> Hi all !
> I am creating a Workflow process whenever a PO ( Order type NB ) is changed.
>
> For this I am using the standard business object BUS2012 ( Purchase Order )
>
> For my objective, I need to use the start Condition of PO type eq 'NB'. I go to Basic data and putting the start condition but I am not getting the PO type field in the Workflow Container. I have placed BUS2012 inside my workflow container. I am using the 'Changed' event.
>
> What I have to do to get the PO type field or do I have to write a check FM ?
>
> Could you please guide me how to put the start condition for the workflow ?
>
> Thanks a lot,
> ~ The abaper
>
> ( Note : I have posted the same in Workflow forum as well, but no responses yet, I am trying here for a faster response, thnx )
There is no PO type in attributes of BUS2012. You have to extend it to add PO type and write program to that attribute.
That way you can have PO type in where condition of workflow basic data.
Let me know if you need any further help on this
Adding attribute is explained in one of the demos.... Go to Blobs and blog by category - ABAP - extending business object ... You will find a video demo for this...

Configure Start conditions based on ibase\ and Customer Fields ??

Dear friends,
We have enchanced transaction types(document types) using Easy enchancement workbench (EEWB). Therefore we have a new tab(customer screen) in all the transaction types we use !!.
This tab has customer fields in it...
Now the requirement we have here is that we have to send Emails based on these customer fields and ibase and component.
How can i create start conditions based on the customer fields and ibase which are not present in object type BUS2000116(default) which is currently reffered while i create start conditions.
I know that i can create new object type(using swo1) and let it be have inherited supertype as BUS2000116 and then inside the new object type i can have my attributes( ibase and those customer fields) inside the new created object.
Is there any way of incalculating the customer fields and ibase \component in BUS2000116 ( by default it does not have these) ???
Assuming that i created new object type, how do i make use of this type while i am configuring conditions.
Any help would certainly be rewarded.

hi again,
Can anybody take some time out and guide me plz...

How to restrict the job start conditions (only "Immediate" type) ?

Hi,
We allow our users to schedule and execute in background mode transactions (example IP19, IW38). We gave them for that authorizations (object S_BTCH_JOB with LIST, PROT, RELE and SHOW - objetct S_PROGRAM with BTCSUBMIT).
We would like that users can schedule and execute their jobs only with the u201CImmediateu201D job start condition (in the Start Time screen for the type of start condition : Immediate, Date/Time, After job, After event, or At operation mode).
Another solution: prohibit the scheduling and the execution background job in a certain time interval ...
How can restrict the job start conditions ?
Thank you.
Patrice.

Hi Jan,
Yes, sa38 makes it possible indeed to execute in background into immediate mode a job but
the user have to know the name of the program to be carried out ...
The user knows only the name of these transactions trade. For example, IW38.
In the menu of this transaction, SAP gives the possibility to execute in background :
Program --> Execute in Background --> display of Start Time screen for the type of start condition :
Immediate, Date/Time, After job, After event, or At operation mode).
It is at this time there that we want that the user can only choose the "immediate" mode.
We must thus prohibit the other choices (Date/Time, After job, After event, or At operation mode) ... and
and we don't know how to restrict these other options in this screen "Start Time screen for the type of start condition".
Thank you.
By.

Z field in the start conditions of a workflow

Hi all,
Is it possible to add a z field in the start conditions of a workflow?
My requirement is to use a z field created in the shopping cart, in the start conditions for the workflow WS14000044.
Thanks and regards
Kishan

Yes you can undo the delegation at any point of time not to worry. It is just atable entry.
Go to swo1->Settings->Delegates
If you want to use a Custom Business object that is a delegate of a Standard Business Bo you can use it. You create a Virtual attribute in your custom Business Object. If you delegate the Custom bo with Standard BO. Whenever you refer to standard Business Object you will have this Custom attribute in your kitty. This will help in start Condition.
<b>Reward points if useful</b>

Workflow not triggered for BP when start condition's field is set by BADI

Hi guys,
I have created a workflow and given the start Event "Changed" of object BUS1006. In this I have given a start condition which triggers this event when a particular field on transaction BP is populated.
Now the problem is that when I myself explicitly populate the field and press save the workflow is triggered fine, but when I populate that field automatically in a Save BADI (BUPA_GENERAL_UPDATE), the workflow is not triggered. Tcode swel just returns the msg that Start condition returns 'FALSE' for object.
Can someone please help me in this or let me know where I can find its cause in system.
Any help would be really appreciated.
Regards,
Shaili

If this is just one field, create your own custom event and code launching it when saving BP with your field changed.
Maybe event Changed is executed only for changes in GUI.
If you program your own one you will have 100% control of it.
Regards
Radek

Condition type field when Define Pricing Procedure Determination

Hello Gurus,
there is a condition type field when Define Pricing Procedure Determination. what does it mean ?
Many thanks,
Frank Zhang

Here is are the details of various fields while configuring pricing procedure.
A. STEP
This indicates the number of step-in the procedure.
B. COUNTER
This is used to show a second ministep
C. CONDITION TYPE
This is the most important component in the pricing procedure. The rates are picked up from this element, on the basis of the properties described.
D. DESCRIPTION
This forms the description of the condition type.
E. FROM
This is used to define the progression of the calculation and range of subtotals
F. TO
This is used to define the progression of the calculation and range of subtotals
G. MANUAL
This function enables to allow the condition type to be entered manually also apart from automatic pickup.
H. MANDATORY
This function identifies the conditions that are mandatory in the pricing procedure. The sales price is a mandatory condition type.
I. STATISTICS
This can be used to represent the cost price of the material sold, generally used for study statistical impacts of price
J. PRINT
The activation of this function will enable the printing of the values and conditions to the document.
K. SUBTOTAL
A key is assigned from the drop down menu; this can be used by the system in other area like Sis for reporting purpose also
L. REQUIRMENT KEY
This function is used to assign a requirement to the condition type. This requirement can be used to exclude the system from accessing the condition type and trying to determine the value. This can be used to specify that the condition type should only be accessed if the customer has a low risk credit.
M. ALTERNATE CALCULATION TYPE
This function allows you use a formula as an alternative in finding the value of the condition type, instead of standard condition technique. this can be used to calculate complex tax structures.
N. ALTERNATE CONDITION BASE VALUE.
The alternative condition base value is a formula assigned to a condition type in order to promote an alternative base value for the calculation of a value.
O. ACCOUNTS KEY
The account keys form part of account determination. These keys are used here to define the posting of the revenue generated to respective account heads& to subsequent assignment to GL accounts.
PR00- ERL
K007/KA00- ERS.
KF00- ERFu2026u2026u2026u2026.& so On.
P. ACCRUAL KEY.
The accrual keys form part of account determination. These keys are used here to define the posting of the revenue generated to respective account heads& to subsequent assignment to GL accounts and payment to respective parties.
Kalpesh

Custom field in start conditions for workflow WS14000044

Hi all,
We have a requirement where a value of a field is coming from the catalog to the shopping cart via the customer fields (provided by SAP). we want to use it as a start condition for the workflow.
The issue we are facing is that the customer fields are not visible as start conditions for the workflow WS14000044.
Is there a way we can make them visible?
We are using SRM 5.0
Thanks in advance
Kishan

Hi ,
start conditions are specified based on reqhead , i am not very sure wether the customer fields are available there.
since they are not available there , you can not see them in the start conditions.
please check wether you can find any notes which deal with implemenation of customer fields in the start conditions.

Conditionally Hide/Display fields in a region

How can I conditionally hide/display fields in a region. Based on a user selection whether they want to 'Enter' or 'Select', I want to dispaly the appropriate field .i.e. if the user selects 'Enter' then I want to display a Text field and if they opt for 'Select', then I want to display a Select list.
Thanks in Advance.
Regards,
Hilal

Hi Halil,
I've been trying to reproduce what the linked site does.
Here's my solution:
1 - Add all items to the page whether or not they are going to be displayed
2 - Ensure that all items that could be shown/hidden are on lines on their own (ie, set New Line to Yes)
3 - In the region's Region Footer (or in a new HTML region in the Before Footer position), add in this bit of javascript:
<script type="text/javascript">
html_HideItemRow('NameOfFieldToHide');
-- repeat for each item to be hidden when the page first loads
</script>
4 - On the radio button's definition, add the following in the HTML Form Element Attributes setting:
onclick="html_ToggleItemRow('NameOfDisplayedItem');html_ToggleItemRow('NameOfHiddenItem');"
Now when the page is loaded, one field is automatically hidden then clicking any of the radio button options will toggle the hidden/displayed fields and their labels.
As stated before, if you do a View Source on the linked application's page, you will see either more methods that are used to show/hide items/regions, but the above should be a starting point for you.
Regards
Andy

SAP Workflow not triggering due to "Start Condition return FALSE" message in SWEL

Hi,
I have SES approval workflow which is not triggering in few cases because of check function ends with exception even it has valid start condition and correct data. For example lets say we have PO no. 100 for which 3 SES (SES1,SES2 & SES3) are created. Out of which workflow for SES3 is not triggering even if all the three contain valid start condition(Bases on internal order at PO line item).when triggering workflow manually using SWUE for SES3 it work fine.Please find SWEL screenshot below and let me know if you have come across this type of issue.
Thanks in Advance.
Ishant.

kindly use SAP_WAPI_CREATE_EVENT and not SWE_EVENT_CREATE it's always better to use APIs.
Why use 2 sub-objects? you already have a z-object and you can modify it. even if there is a reason for the double sub object , the workflow should still run on the standard one - BUS2091.
see for example :
Extending Object Types: Inheritance and Delegation - SAP Business Workflow - SAP Library
As for your question,
if you are using a function module to raise the event, way not check in it if the service entry sheet has been created properly before creating the event. you can even check if the PO contains an internal order in your RFC function module and raise a specific event. then you will have no need for the starting condition.

Action with start condition always triggers

Functionality required: "when its 4 days from the actual date an
Audit is to take place an e-mail should be triggered to the
audit attendees"
I have created a new date rule (4 days before - reminder) and
added this date rule to the date profile 000000000003. I am
using this date profile in my actions and have set a new start
condition to trigger an e-mail alert when "todays date" = my new
date rule. I have set up scheduled conditions which are met.
when i create transactions which meet both the scheduled and
start conditions (from my perspective) the action is getting
triggered to send the e-mail reminder. My new date rule is as
follows:
<?xml version="1.0"?>
<TimeRule>
   <TimeRuleSource>
      <ruleline>
         <AssignTimeExp displaytype="AssignTime">
            <VarTimeExp displayType="VarTime"
                               name="RESULT"
                           position='B'>
              <VarObjectExp displaytype="VarObject"
                                name="SYSTEM"/>
            </VarTimeExp>
            <MoveTimeExp displaytype="MoveTime" direction="-">
               <VarTimeExp displayType="VarTime"
                                  name="ORDERACTUAL"
                                  position="B">
                 <VarObjectExp displaytype="VarObject"
                                name="SYSTEM"/>
               </VarTimeExp>
               <ConstDuraExp displaytype="ConstDura"
                                duration="4" timeunit="DAY">
                  <VarObjectExp displaytype="VarObject"
                                name="SYSTEM"/>
               </ConstDuraExp>
            </MoveTimeExp>
         </AssignTimeExp>
      </ruleline>
   </TimeRuleSource>
When i test it using various dates it seems to work as expected, it returms false when it should fail and true when it should suceed When tested from within the date rule for the FROM and TO date for todays dates i get the following:
Deadlines
Appointment Type RESULT
From SA 10.02.2007 14:27:52 GMTUK
From
Appointment Type ORDERACTUAL
From WE 14.02.2007 14:27:52
To WE 14.02.2007 14:27:52
Duration
Reference Objects
SYSTEM GMTUK CL_TIMECALENDAR_SIMPLE
In my start condition i am testing for my date rule (4 days
before - reminder) = todays date.
Can anyone explain why my start condition is always being triggered
Thanks in advance
Ed

Hello Easwar Ram,
Thanks for your reply.
No, I didn't create an Action Profile. I use standard profile: /SCWM/TU (Shipping & Receiving - Transportation Unit).
I only have created a new Action Definition, Schedule and Start Conditions for this Definition. All work correctly with the exception of the button 'Start Condition Parameter'.
I don't know why the button appears because I didn't define a Condition Parameter for the Start Condition. And when I click on this button I get an error in standard SAP code:
1) li_bor_object ?= l_context->appl.
2) ls_bor_handle = li_bor_object->get_bor_object( ip_objtype = l_objtype ).
L_context->appl has value '' in the debugger. After line 1 the value of the li_bor_object is '' therefore line 2 terminates the transaction with error.
Maybe this occurs because the Action Profile uses a Persistent Class for Object Type instead of a Business Object Repository?

Unicode - "DMBTR" must be a character-type field (data type C,N,D or T)

Greetings Experts!
I am trying to convert legacy code to Unicode for a current ERP6.0 reinstallation and have encountered the syntax error "DMBTR" must be a character-type field (data type C,N,D or T)
The field is part of a structure and the fields attributes are as follows:
COMPONENT = DMBTR
COMPONENT TYPE = DMBTR
DATA TYPE = CURR
LENGTH = 13
DECIMALS = 2
DESCRIPTION = Amount in Local Currency
The code in question is as follows:-
macro Move_Zoned.
Converts a numeric variable to zoned format and moves it to a
target variable.
DEFINE move_zoned.
     &1 - source variable
     &2 - Number of Decimal Places
     &3 - 'To'
     &4 - Target Variable.
write &1 to w_zoned no-grouping decimals &2.
condense w_zoned.
     Remove the Decimal Points.
search w_zoned for '...'.
while sy-subrc = 0.
    move sy-fdpos to w_to_point.
    if w_to_point = 0.
      w_to_point = 1.
    endif.
    compute w_from_point = sy-fdpos + 1.
    concatenate w_zoned+0(w_to_point)
                w_zoned+w_from_point
           into w_zoned.
    search w_zoned for '...'.
endwhile.
shift w_zoned right deleting trailing space.
translate w_zoned using ' 0'.
call function 'Z_TRANSLATE_ZONED_DECIMALS'
    exporting
      i_input              = w_zoned
    importing
      i_output             = w_zoned
    exceptions
      x_invalid_zoned_char = c_invalid_zoned_char
      x_numeric_info_lost = c_numeric_info_lost
      others               = c_other_zoned_error.
     Get the length of the recipient field so we don't truncate the
     numbers....
describe field &4      length w_flength in character mode.
describe field &4      type   w_type.
describe field w_zoned length w_zoned_len in character mode.
if w_zoned_len <= w_flength.
    move w_zoned to &4.
    shift &4 right deleting trailing space.
    translate &4 using ' 0'.
else.
        Get the start position....
        If it's a packed field allow for values up to 6 figures
    compute w_zoned_len = w_zoned_len - w_flength.
    if w_type = 'P'.
      subtract 2 from w_zoned_len.
      clear w_type.
    endif.
    move w_zoned+w_zoned_len &3 &4.
endif.
END-OF-DEFINITION. "Move_zoned
LOOP AT t_single_kunnr.
    move_zoned t_single_kunnr-postamt 2
            to t_single_kunnr-dmbtr.
    DIVIDE t_single_kunnr-dmbtr BY 100.
    MODIFY t_single_kunnr.
ENDLOOP.
Is there a solution to get past this syntax error as I would rather not change the datatype of the field in the structure.
Much Obliged
Elphick.

Type X is not allowed in Unicode. When a field is declared as Type X with Value u201809u2019 or any other value, it can be resolved by using classes.
Before Unicode
                  CONSTANTS: c_hex TYPE x VALUE '09'.
Resolution:
Itu2019s work for any value of x.
First a temporary field of Type c should declare. Following class will convert Type x variable into type c.
Example:
CONSTANTS: c_hex TYPE x VALUE '09'.
DATA: LV_TEMP TYPE STRING.
DATA: LV_TMP TYPE C.
TRY.
CALL METHOD CL_ABAP_CONV_IN_CE=>UCCP
EXPORTING
UCCP   = c_hex
RECEIVING
CHAR   = LV_TMP   .
CATCH CX_SY_CONVERSION_CODEPAGE.
CATCH CX_PARAMETER_INVALID_TYPE.
CATCH CX_SY_CODEPAGE_CONVERTER_INIT.
ENDTRY.
CONCATENATE I_OUTPUT-BKTXT I_OUTPUT-BVORG
I_OUTPUT-BUDAT I_OUTPUT-MESSAGE INTO
SEPARATED BY LV_TMP.
I_BUFFER = LV_TEMP.
CLEAR LV_TEMP.
CLEAR LV_TMP.
OR
Note: It works only for type x value 09.
CLASS cl_abap_char_utilities DEFINITION LOAD.
CONSTANTS: c_hex TYPE c VALUE
                         abap_char_utilities=>HORIZONTAL_TAB.

How to Add Values in INVOICE SUB-TYPE field at the Invoice Header Forms

Hello,
Does any body knows how could I add/modify values in the INVOICE SUB-TYPE field at the Invoice Header Forms?. This values are related to the Globalization, in this case for the Chilean Localizations.
Thanks,
Alejandro R.

It gives any error or just does nothing?
Have you tried making another simple form with just one block and one or two items?
You can do this type of testing in these conditions.
Which version of forms are you using?

Error using a method call in the starting conditions of a Workflow

Hi,
In SRM 4, I have a doubt about a start condition with WFWS14000109 I need to trigger the WF depending on organizational unit of the requester (not purchase group or purchase organization).
I have seen in the editor, in SWB_COND in the part of requisitionerUser the Method ReadOrgUnit.
I change to traditional mode of the editor and when I select the method I get in Express1. field
&_EVT_OBJECT.REQUISITIONERUSER.READORGUNIT(_RESULT='OBEG';ACTORGUNIT= )&
If I use = and the organizational unit in express2 field I get error
Partial expression expected (expression '&_EVT_OBJECT_REQUISITIONERUSER.READORGUNIT(_RESULT',position 76)
Can anybody say me where is the error? how I should express the condition.
Thanks
Best Regards

I don't think you can use a BOR method in a condition. At least not as far as I know. I think it would be better to create a virtual attribute in your delegated subtype of BUS2121 and use that in the condition.
Regards,
Martin

How to create the sub type field in hr abap infotype

hi ,
how to create the sub type field in hr abap infotype.
regards,
venkat.

Try like this also
creating of infotype please follow these steps ...
Step 1: Create Infotypes
i. Goto Transaction PM01 To create Infotypes:
ii. Enter the Infotype Number and say create all.
iii. The following message would display:
i. PSnnnn Does not exist. How do you want to proceed?
iv. Click
v. A maintain Structure screen appears.
Fill in the short text description and the PS structure of the Infotype.
Since the fields Personnel No, Employee Begin Date, End Date, Sequential Number,Date of Last Change, Name of user who changed the object are available in the PAKEY and PSHD1 structure, define the PSnnnn structure with only the fields you required.
vi. Once the PS Structure is created, save and activate the structure.
vii. In the initial screen of PM01, now click on .
Create a new entry for the infotype.
Fill in the values as mentioned below and save.
Infotype Characteristics:
Infotype Name of the infotype_ Short Text: __Short Description________
*General Attributes :
Time constraint = 1
Check Subtype Obligatory
Display and Selection:
Select w/ start = 3 Valid record for entered data
Select w/ end = 5 Records with valid dates within the period entered
Select w/o date = 6 Read all records
Screen header = 02 Header ID
Create w/o end = 1 Default value is 31.12.9999
Technical Data:
Single screen = 2000
List screen = 3000; List Entry Checked.
viii. In the initial screen of PM01, now click on .
Choose the infotype entry in the list.
Fill in the values as mentioned below and save.
Technical Attributes:
In tab section,
The following attribute values are given:
Applicant DB Tab = PAnnnn Infotype Name
Subtype field = SUBTY
Subtype table = T591A
Subty.text tab. = T591S
Time cnstr.tab. = T591A
Prim. /Sec. = I Infotype
Period/key date = I Interval
and .
ix. Infotype Screen Modification:
Edit Screen 2000 from PM01 for the Infotype.
ABAP Editor for the Infotype Program MPnnnn00 will be displayed.
Click . Flow Logic will be displayed. There string coding of your own logic.
Regards
Pavan

WF start condition : PO type field in BUS2012

Similar Messages

Maybe you are looking for