Different scenarios for implementing screen exits

Hi all,
Is there different scenarios for implementing screen exits for different applications such as MM,SD....etc.

Similar Messages

How to Implement Screen Exits for MK01...

Hi All,
I have to implement screen exits for Tcode MK01.
There is a BADI namely VENDOR_ADD_DATA_CS for Mk01.
Please guide me on how to implement a screen exit..
If possible send me the steps to be followed.
Regards,
Vidya.

Hi,
Check this:
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
Have a look at this thread:
your working with BADI Then do as follows....
you follow the SPRO way and do everything they say.
1.you make an own z program with your subscreens
2.by VENDOR_ADD_DATA you put something like this to method CHECK_ADD_ON_ACTIVE:
Aktivierung Zusatzfelder für ZDB
if i_screen_group = 'Z1'.
e_add_on_active = 'X'.
endif.
3.by VENDOR_ADD_DATA_CS you put something like this to get_taxi_screen
CASE i_taxi_fcode.
Premier
WHEN 'Z1_SRCE1'.
e_screen = '0100'.
e_program = 'ZPM_SCREENEXIT_MK02'. " your own program
e_headerscreen_layout = ' '.
Deuxiem
WHEN 'Z1_SRCE2'.
e_screen = '0110'.
e_program = 'ZPM_SCREENEXIT_MK02'.
e_headerscreen_layout = ' '.
ENDCASE.
4. you make sure, that everything is active
Regards
Kiran
Edited by: Kiran Sure(skk) on Apr 11, 2008 3:42 PM

Someone has a tutorial for creating screen exit?

I have a development and I do not know how to create screen exit.
Case Someone has a tutorial for creating screen exit please help me
Thank you
Wagner Duarte
Consultant - SAP ABAP

hI
Screen Exit is nothing but enhancing the screen like creating some more fields, subscreen and so on.
1. Go to the screen>System>Status-->Program (Double
click this program. It will take you to the program.
2. Now, Goto-->Object Directory Entry.
3. Make a note the package name.
4. Now run the transactions SMOD, press F4 and enter the
above noted package, press enter.
5. It will display list of Exits.
6. Now go back to the initial screen SMOD.
7. Specify the exit name here and select the radio button
Components.
8. It will display four group boxes one for FM, second
for Fcodes, thrid for Screen areas and last for
includes.
9. Goto transaction CMOD, create a new project, and
click the button "Enhancement assignments" and
specify your enhancements that you got in SMOD.
10. Now bouble clikc the enhancement, it will take you to editor with some includes starting with Z, double clikc the include you want to edit and proceed.
Have a look at below link It will definately help you to undestand the same.
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
check these links.
http://help.sap.com/saphelp_46c/helpdata/en/c8/1975e643b111d1896f0000e8322d00/frameset.htm
http://www.allsaplinks.com/screen_exit.html
USER EXITS
https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=312792
https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=1320078
https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=2669896
How to implement screen exit for a SAP standard transaction
Introduction
SAP provides standard transactions to enter data into database. But a client may want to maintain some additional information in SAP other than what is provided.
To make provisions for this, additional screens have to be provided and additional fields must be added into appropriate database table.
To pave way for this, SAP has provided the option for screen exits. Usually, SAP provides the following:
An append structure in the database table with the new fields.
A subscreen area into the standard screen where the programmer can attach his subscreen of his own program with the new fields.
A function group under which the new subscreen has to be created with the new fields.
Function exits to synchronize the PBO and PAI of the standard SAP program with the PBO and PAI of the subscreen so that data can flow back and forth between the standard SAP program and the program written by the developer for the subscreen. These function modules also exist in the same function group under which the subscreen will have to be developed.
Finally, a linkage has to be done between the subscreen area of standard SAP screen with the custom subscreen constructed by the developer.
Typically, SAP provides an enhancement in which the developer can create an append structure, use the function exits to synchronize the PBO and PAI of the standard SAP program and the custom subscreen program, and make the necessary linking( as mentioned above in step 4. But, again, this is not a hard and fast rule. Linking in some case, is also done by configurations.) SAP also usually provides the name of the function group under which the subscreen has to be developed.
Necessary guidance about implementing a screen exit development is usually available in the Documentation section of the enhancement ( can be availed by transaction SMOD).
Pre-Requisites
The developer to work on screen exit should have essential knowledge on the following:
DDIC concepts, including the knowledge of append structure.
Concept of SAP Enhancements and implementing them using Projects.
Concept of function exits.
Knowledge on Module Pool including subscreens, Tabstrip controls etc.
Steps
Guidelines
So, a developer can follow the guidelines mentioned below to implement a screen exit to a standard SAP transaction, as and when required:
Find out the Required Enhancements
Go to SMOD. Press F4 in the Enhancement field. In the next popup window, click pushbutton SAP Applications. A list will appear that contains information on all the enhancements, categorized under functional areas. Developer must search for the enhancements relevant to his functional area of interest for e.g., Purchasing, Asset Accounting, etc.
Note down the enhancements. Then, come to the initial screen of SMOD and view the documentation of each enhancement to find out which one is required for your development.
Utilize the Enhancement in a Project
After you have found one, do as directed in the documentation. Generally, the steps are as follows:
Create a project using CMOD including your enhancement.
Create the append structure with new fields.
Go to the desired function group and create a subscreen with the new fields. Write PBO and PAI for the subscreen, if required.
Use the function exits in the enhancement to link the PBO and PAI of the subscreen with that of the main SAP program supporting the SAP transaction.
Maintain necessary linkage between the subscreen area of standard SAP program with the custom subscreen developed along with the custom program name. This can be done in the project (developed by CMOD including the enhancement) or outside as a part of configuration.
Activate the project.
Test to ensure that required functionality are met.
Case Study 1
Add three new custom fields for Asset master and maintain information for them
Requirement
Three fields in the legacy system have to be maintained in Asset master. These fields are:
Original Asset number 20 characters
Location 2 15 Characters.
Model no 20 characters
Location 2 should start with L.
Pre-Analysis
Finding out the Enhancement
As described above, the enhancement is determined. It was found, that enhancement AIST0002 will serve the purpose. It contains the following components (can be viewed by transaction SMOD):
Exit Type Description EXIT_SAPL1022_001 Function Exit Check of User-Defined Fields when Using Create and Change BAPI EXIT_SAPLAIST_002 Function Exit Transfer Data for User Subscreens in PBO. EXIT_SAPLAIST_003 Function Exit Transfer of User-Defined Fields to SAP Master Data Transactions CI_ANLU Customizing Include Include structure to add new fields
Studying the Function Exits
The function module level documentation for the function exits are then viewed from transaction SE37. The documentation clearly laid out for the purpose for their use:
EXIT_SAPLAIST_002
Function module Level Documentation
This function module is called by asset master data maintenance at the start of the dialog. (When changing, it is called after reading of the data from the database; when creating it is called after the transfer of the default values from the asset class and reference asset.) The purpose of the function module is to enable this function group to recognize the master data. For interpreting or controlling master data fields that are important for user fields, it is possible to transfer to global variables at this point, so that they can be recognized when the user subscreens are processed.
Import Parameters
Understanding
This function module is called at the PBO to pass the information retrieved from the database to pass them to the custom subscreen and its underlying program. Import parameter : I_ANLU will be populated with the values for user-defined fields which will be passed to the subscreen program. So, there must be some sort of variable assignment from I_ANLU.
EXIT_SAPLAIST_003
Function module Documentation: This function module is called by SAP asset master data maintenance after the screens are processed, but before saving. The purpose of the function module is to transfer fields entered on user sub-screens of SAP asset data maintenance to the database for updating. The export parameter for this function module is:
Understanding
This function module will be used to transfer the user entered data in the subscreen fields to the main SAP program, which will then be saved into the database.
Studying the Documentation of the Enhancement
The enhancement documentation (as is viewed from the initial screen of SMOD] also supports the idea. Moreover, it informs that we need to develop a subscreen under function group XAIS. This is the function group under which the two function exit modules also exist. So, if the custom subscreen refers to the global data of the function group XAIS, then those values will also be available to these function exits as well.
Going to SE80 and viewing the function group XAIS helps us to inform that there are three DDIC tables declared for it:
Deciding the Final course of Action
After making all the investigations, the final course of action was determined.
SrlNo Step Justification
A project has to be created using transaction CMOD where the enhancement AIST0002 will be included.
Customizing include CI_ANLU has to be created with the custom fields demanded When CI_ANLU will be developed, the custom fields will get appended to the database table ANLU. Also, these fields will be used to create screen fields in the new subscreen.
A custom subscreen, say, 9000 will be developed under function group XAIS. The screen group for the screen will be CUST (or any name). The three custom fields added to table ANLU (by creating CI_ANLU) will be used to create new fields in the screen.
In the PAI of the subscreen, validation for Location to start with L will be added. The subscreen with three new fields has to be developed so that it can be attached to a subscreen area of the asset master screens.
In the custom include of the function exit module EXIT_SAPLAIST_002, the following code will be written:-
ANLU = I_ANLU. I_ANLU is the import parameter of this FM. The value is assigned to the global variable ANLU, referring which the three new subscreen fields are developed. So, data retrieved from database table ANLU will be passed to this FM as I_ANLU by the standard SAP main program. The value will be taken and passed to the global variable of the function group XAIS, so that the three custom fields (referring to ANLU of XAIS) get populated.
In the custom include of the function exit module EXIT_SAPLAIST_003, the following code will be written:-
E_ANLU = ANLU. The changed values in the subscreen fields exist in global variable ANLU for the function group XAIS. This function exit module will pass the data back to the SAP main program as E_ANLU.
Proper linkage/configuration has to be done so that the new subscreens get linked to the appropriate subscreen area of the Asset master screen. This has to be done otherwise, the new custom subscreen will not be displayed in the Asset master screens.
Development
Creating a Project to include the enhancement
Go to transaction CMOD and create a project.
Enter a description for the project. Then, click on the pushbutton Enhancement Assignments in the Application Toolbar.
Enter the name of the enhancement and Save.
Go to Components.
Creating Custom Include for ANLU
The screen shown below will appear, showing all the enhancement components under the assignment AIST0002. Double-click on the name of the Include Structure to create it.
Create the include structure with three new fields, as required. Then, save and activate it.
Develop the subscreen and the program
Go to transaction SE80. For the function group XAIS, create a new subscreen 9000.
Create it as subscreen.
Then, go to the Layout of the screen and create three new fields from Database table ANLU.
Drag the fields in the screen body and place them.
Then, save and activate the screen and come back to screen flow editor.
Create the PAI module to add validation for field Location 2, as required .
Activate the whole function group and come out.
Write code in the Function Exits to synchronize the programs
Now, code has to be written in the function modules EXIT_SAPLAIST_002 and EXIT_SAPLAIST_003 so that data flows to and fro between the main SAP program and custom subscreen program. For that, go back to transaction CMOD and change the function exits.
Write code in the function module EXIT_SAPLAIST_002 called once at the beginning of the transaction:
Write code in EXIT_SAPLAIST_003 to pass the data from the subscreen to SAP main program.
Then, activate everything the whole project and come out.
Complete the configuration to link the subscreen
The development portion is complete. Now, linking of the subscreen has to be done with the subscreen area of the main program. In most of the cases, this linking can be done in the enhancement itself. But, here, requirement is a bit different. It is done by configuration using SPRO.
Assets are created under Asset class. And for each asset class, there is a layout assigned to it. For a layout, there are multiple tab pages assigned to it. And, for each tab page, there are multiple screen groups/field groups assigned.
Here, the requirement is to create these three custom fields in the tab page General of asset master screen ( AS01/AS02/AS03/AS91).
Determine the Layout
To achieve this, first of all, we need to find out which layout is assigned to asset class 1000.For that, go to transaction AOLK( information has to be obtained from functional consultant).Select the Asset Class 1000 and click on folder General Assignment of Layout.
Here, for Asset class 1000, for all the user groups, tab layout SAP is assigned. Since layout SAP cannot be changed, it has to be copied and manipulated to include our screen group. Later, the new layout has to be assigned over here.
Create new tab layout
Go to transaction AOLA. Copy the tab layout SAP to create another layout, say, YSUB.
System will copy all the settings and will inform you about that.
Select your newly created layout and double-click on the folder Tab page titles.
You want to put your custom fields in the tab page General. So, select this tab page entry and double-click on the folder "Position of Groups".
Here, all the field groups currently residing in the tab-page General are shown. Add an entry for your newly created fields.
Select the group box from the list. An entry will come with U padded with the custom subscreen prepared by you.
Then, save and come out.
Assign the new Layout to Asset Class
Now, go to tcode AOLK and assign tab layout YSUB for asset class 1000.
Save and come out.
Test the Exit
Everything is over. Now, go to transaction code AS01/02/03 or AS91 to deal with an asset of asset class 1000. You will see your new fields added to the screen. Add values to themsave. Then, enter into the tcodes again to see whether the values entered by you are being displayed or not.
Original Source: ittoolbox.com
Screen Exit is nothing but enhancing the screen like creating some more fields, subscreen and so on.
1. Go to the screen>System>Status-->Program (Double
click this program. It will take you to the program.
2. Now, Goto-->Object Directory Entry.
3. Make a note the package name.
4. Now run the transactions SMOD, press F4 and enter the
above noted package, press enter.
5. It will display list of Exits.
6. Now go back to the initial screen SMOD.
7. Specify the exit name here and select the radio button
Components.
8. It will display four group boxes one for FM, second
for Fcodes, thrid for Screen areas and last for
includes.
9. Goto transaction CMOD, create a new project, and
click the button "Enhancement assignments" and
specify your enhancements that you got in SMOD.
10. Now bouble clikc the enhancement, it will take you to editor with some includes starting with Z, double clikc the include you want to edit and proceed.
and you just go through these links also
Screen exit
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
screen-exits
Check the following link.
https://www.sdn.sap.com/irj/sdn/advancedsearch?query=how%20to%20find%20screen%20exits&cat=sdn_all

How to use the different class for each screen as well as function.

Hi Experts,
How to use the different class for each screen as well as function.
With BestRegards,
M.Thippa Reddy.

Hi ThippaReddy,
see this sample code
Public Class ClsMenInBlack
#Region "Declarations"
    'Class objects
    'UI and Di objects
    Dim objForm As SAPbouiCOM.Form
    'Variables
    Dim strQuery As String
#End Region
#Region "Methods"
    Private Function GeRate() As Double
            Return Double
    End Function
#End Region
Public Sub SBO_Appln_MenuEvent(ByRef pVal As SAPbouiCOM.MenuEvent, ByRef BubbleEvent As Boolean)
        If pVal.BeforeAction = True Then
            If pVal.MenuUID = "ENV_Menu_MIB" Then
            End If
        Else ' Before Action False
            End If
    End Sub
#End Region
End Class
End Class
Rgds
Micheal
Vasu Anna Regional Feeling a???? Just Kidding
Edited by: micheal willis on Jul 27, 2009 5:49 PM
Edited by: micheal willis on Jul 27, 2009 5:50 PM

What are the different options for implementing web security?

Hi,
Right now I am working on an internet website. We are using JSP for presentation and running Weblogic Application Server. I want to know different options for implementing website security. One of the options that I am aware of is to use LDAP. But we donot want to go and buy a LDAP Directory Server now. So I would really appreciate if somebody could let me know my choices here.
Thanks in advance.

Hi,
If you are working on a Windows 2000 platform, the most obvious choice would be Active Directory Server as this is shipped free with Server 2000. It is LDAP compliant, although does have a few differences that set it apart from the other X500 standard based solutions which I will mention in a moment. Details on these differences can be found at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnactdir/html/msdn_activedirvsnds.asp
Other options are openldap, an open source implementation of an ldap server or iPlanet's Directory Server. If you are initially doing an evaluation, a trial version is available of the iPlanet software and can be downloaded from their site. I found this particularly easy to get to grips with and their is excellent documentation available. There is also an offering from Novell, but I have no experience of this.
Hope this helps.
Jon

Implementing Screen Exit

Hi,
How to implement screen exit in a standard SAP transaction?
Thanks,
Raghavan

Hi
Check this:
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
this document will help you out.
regards,
Sreevani

Badi for fv05 screen exit

hi all,
i am finding the badi for fv05 screen exit.
please tell me the badi for fv05 screen exit.
thanks
Sachin
Edited by: Sachin Gupta on Jul 1, 2009 4:00 PM

S0006595706 wrote:>
> hi all,
>
> i am finding the badi for fv05 screen exit.
>
> please tell me the badi for fv05 screen exit.
>
>
> thanks
> Sachin
>
> Edited by: Sachin Gupta on Jul 1, 2009 4:00 PM
Hi,
Please use the following program to find out exits and badis by entering tcode to the program
*& Report Z_FIND_USEREXIT
report z_find_userexit.
*& Enter the transaction code that you want to search through in order
*& to find which Standard SAP User Exits exists.
*& Tables
tables : tstc,     "SAP Transaction Codes
         tadir,    "Directory of Repository Objects
         modsapt, "SAP Enhancements - Short Texts
         modact,   "Modifications
         trdir,    "System table TRDIR
         tfdir,    "Function Module
         enlfdir, "Additional Attributes for Function Modules
         tstct.    "Transaction Code Texts
*& Variables
data : jtab like tadir occurs 0 with header line.
data : field1(30).
data : v_devclass like tadir-devclass.
*& Selection Screen Parameters
selection-screen begin of block a01 with frame title text-001.
selection-screen skip.
parameters : p_tcode like tstc-tcode obligatory.
selection-screen skip.
selection-screen end of block a01.
*& Start of main program
start-of-selection.
* Validate Transaction Code
select single * from tstc
    where tcode eq p_tcode.
* Find Repository Objects for transaction code
if sy-subrc eq 0.
    select single * from tadir
       where pgmid    = 'R3TR'
         and object   = 'PROG'
         and obj_name = tstc-pgmna.
    move : tadir-devclass to v_devclass.
    if sy-subrc ne 0.
      select single * from trdir
         where name = tstc-pgmna.
      if trdir-subc eq 'F'.
        select single * from tfdir
          where pname = tstc-pgmna.
        select single * from enlfdir
          where funcname = tfdir-funcname.
        select single * from tadir
          where pgmid    = 'R3TR'
            and object   = 'FUGR'
            and obj_name = enlfdir-area.
        move : tadir-devclass to v_devclass.
      endif.
    endif.
* Find SAP Modifactions
    select * from tadir
      into table jtab
      where pgmid    = 'R3TR'
        and object   = 'SMOD'
        and devclass = v_devclass.
    select single * from tstct
      where sprsl eq sy-langu
        and tcode eq p_tcode.
    format color col_positive intensified off.
    write:/(19) 'Transaction Code - ',
    20(20) p_tcode,
    45(50) tstct-ttext.
    skip.
    if not jtab[] is initial.
      write:/(95) sy-uline.
      format color col_heading intensified on.
      write:/1 sy-vline,
      2 'Exit Name',
      21 sy-vline ,
      22 'Description',
      95 sy-vline.
      write:/(95) sy-uline.
      loop at jtab.
        select single * from modsapt
        where sprsl = sy-langu and
        name = jtab-obj_name.
        format color col_normal intensified off.
        write:/1 sy-vline,
        2 jtab-obj_name hotspot on,
        21 sy-vline ,
        22 modsapt-modtext,
        95 sy-vline.
      endloop.
      write:/(95) sy-uline.
      describe table jtab.
      skip.
      format color col_total intensified on.
      write:/ 'No of Exits:' , sy-tfill.
    else.
      format color col_negative intensified on.
      write:/(95) 'No User Exit exists'.
    endif.
else.
    format color col_negative intensified on.
    write:/(95) 'Transaction Code Does Not Exist'.
endif.
* Take the user to SMOD for the Exit that was selected.
at line-selection.
get cursor field field1.
check field1(4) eq 'JTAB'.
set parameter id 'MON' field sy-lisel+1(10).
call transaction 'SMOD' and skip first screen.
Edited by: Dande on Jul 1, 2009 2:27 PM
Edited by: Dande on Jul 1, 2009 2:30 PM

Special Scenarios for spl screening A1, A2, B1, B2, c1, C2 and C3

Hi Experts,
Can any one explain about the special senarios for SPL screening like A1, A2, B1, B2, and C1, C2, and C3.
I have little bit confuse when we use these scenarios can any one explain in details if possible.
Thanks in advance for who explain briefly

Hi Hari,
Below are the brief points on the scenario's that you just asked to be described.
A1:- SPL screening done during transfer itself i.e. immediately or synchronously for GTS business Partners against all SPL files
A2:-SPL screening done during transfer itself i.e immediately or synchronously for GTS documents for partner addresses against all SPL files
B1:-Periodic Screening done against all SPL files for GTS Business Partners
B2:-Periodic Screening done against all SPL files for GTS Documents for Partner Addresses
C1:- Periodic Screening done aagainst Delta SPL files for GTS Business Partners
C2:-Periodic Screening done against Delta SPL files for GTS Documents for Partner Addresses
Apart from these, there are other scenarios as well. Which are as follows.
S1:-SPL screening done during transfer itself for GTS business Partners against all SPL files but in simulation mode
S2:-SPL screening done during transfer itself for GTS documents for partner addresses against all SPL files but in simulation mode
These above 2 are similar to Scenario A1 and A2 but in simulation mode.
But I am not sure about the C3 scenario asked above. Probally other experts can put a light on it.
Regards,
Aman

Change log data is NOT captured for PO screen exit fields

Hi,
We created a new tab at item level for PO Screen(ME21N) for the purpose of STOs(Document Type UB) & created 3 New fields in that new tab through Screen Exit( SAPMM06E, SAPLXM06 0111 ).
When we are entering data in those 3 new fields while creating new STOs, those data are captured in EKPO table.
When we are changing the OLD STOs for those 3 new fileds, data is modifying in EKPO table. But changes are NOT inserted in CDHDR and CDPOS table for those 3 new fields.
Please help us to track the changes in those 3 new field data changes for old STOs.
Please let me know if you need any further clarification regarding this.
Thanks & Regards,
Mani.

Hai Naimesh Patel,
 Thanks for your promptly reply.
 Now My issue has been resolved successfully with your help.
 I rewarded Points for your reply.
Thanks & Regards,
Mani.

Implement screen exit for MM01

Hello all,
I follow the instructions from the link below for adding a new tab for MM02-MM03 tcodes.
<link to blocked site removed by moderator>
I added the tab and i created the screens but now i want to fill my tab with values from mvke table and i need to use values ( vkorg werks vtweg )which i entered on the organization level selection screen.
On MM02, On the first screen i enter matnr then i select my new tab view, then i enter ( vkorg werks vtweg ) values for organization levels.
Now i need these ( vkorg werks vtweg ) organization level values in my new tab but i cant get them. I tried get parameters but it is only working for matnr. Not these parameters. How can i get them any ideas? All global tables are empty in my tab.
Edited by: aydnbk on Oct 6, 2011 10:48 AM
Edited by: Thomas Zloch on Oct 6, 2011 8:36 PM

I managed to do it by using badi BADI_MATERIAL_OD

Table or FM for Implemented User Exits

Hi,
Are there any tables or function modules that can give me the user exits that have been implemented?
Thanks in advance.
Mick

Thanks for the reply.
Lets say for eg that for I have got a list of user exits available for creating Sales Order by using the package VA.
SDAPO001
SDTRM001
V45A0001
V45A0002
V45A0003
V45A0004
V45E0001
V45E0002
V45L0001
V45P0001
V45S0001
V45S0003
V45S0004
V45W0001
V46H0001
V60F0001
Now I want to know which amongst these have been implemented. How do I find that? Is it possible to find the implemented exits from some database tables or using a FM?
Regards,
Mick

Scenarios for implementing email

Hello,
Can anybody suggest some common scenarios where email notifications can be implemented in 4.6C?
Regards,
Sujith

Hi,
1. When you use workflow for approvals. For example if invoice is more than $ 1000 then you would need approval from the manager. Hence, you would send an email for approval if the invoice amount exceeds $ 1000.
2. In EDI processes. You would send an email to responsible persons when a document fails.
3. When you use workflow for notifications. To inform the responsible persons that a document has been created. etc
4. Handling of exception situations.
Regards,
Srilatha.

Scenarios for implementing workflow

Hello,
Can anybody suggest some scenarios where I can implement SAP work flow?
Some links will be very useful.
Regards,
Sujith

Hello,
Implementing the model for workflow execution
This section discusses the modeling option we implemented with the required task iteration functions for our client. The process model we created to represent the end-to-end process, and its mapping to the client's business scenarios, are shown. A snapshot of the process model, with its process modules and activities that each of the process modules orchestrate, are also discussed.
Rationale for the choice
To implement task rework we selected Option 2, the process-subprocess approach (stop, rewind, and start). This approach allows for better process simulation that helps optimize the business process. It also helps keep the model unchanged, even after the process improvements result in less rework. Although, it is recommended that the model is cleaned up to remove the unwanted rework steps.
Rework needs will likely be reduced because rework is not typically driven by process or business conditions. It is most often caused by operational constraints and lack of full understanding of the process. The rework occurrences would diminish as users gain better understanding by using a workflow solution and by applying monitoring results to improve the business process.
The business process model developed using WBI Modeler consists of process modules identified in the process scope. The end-to-end process is created by using the process modules and business rules to help choreograph these modules in the correct sequence.
The process model approach supports execution of business process for a "happy path." The process modules are used to execute the end-to-end process for happy path and the task rework requirement. The approach also supports reusability. The model information includes organization data, process data elements, and metrics data (KPIs).
End-to-end business process model
The contract management process involves various business activities that result in creation of proposals and contracts. The activities are logically grouped into process modules, which in turn make up the end-to-end process model. A business event in the CRM system triggers the launching of the process and executes the modules and activities based on business rules. The process execution creates and assigns tasks to sales support team members, who will work and complete the tasks. The process modules are mapped to the business scenarios as shown here.
Scenario 1: Execute Service Request 1 - Customer Research
Scenario 2: Execute Service Request 2 - Solution Configuration
Scenario 3: Execute Service Request 3 - Solution Pricing
Scenario 4: Execute Service Request 4 - Perform Customer Credit Check
Scenario 5: Execute Service Request 5 - Prepare Proposal and Contract

Can I use two different greens for green screening and keep one without it being keyed out?

I am using a green screen which is your standard light green fabric.
I am also wearing a bottle green cape.
I want to key out the standard green which is no problem. However it also takes out the bottle green on my cape.
Is there a way on either Premiere Pro or After Effects to ensure the bottle green stays as it is without being automatically keyed out?
Many thanks.

shooternz wrote:
rotoscope
There's your answer, most likely. I can think of a few methods you might try, but they're going to be labor intensive, and likely involve some roto.
Most keyers have a threshold setting that determines what colors stay and which ones go. You could keep tweaking that setting in very small increments, and if you get lucky, it might discriminate between two green values.
You might be able to precomp in Ae and use the Change Color plug to shift one of them to a more contrasty green or different hue altogether and create a luma matte.
But, you failed green screen 101, and you gotta' go to detention.
robodog, you're being a bit harsh on Jimmy Simon. He said "Might be worth a reshoot...." I can't disagree. Depending on arahman's situation, a reshoot might be easier and quicker. You never know.

Scenarios for implementing email notification

Hello,
Can anybody suggest some common scenarios where email notifications can be implemented in 4.6C?
Regards,
Sujith

Hi,
you can look into the following threads on SDN,
Two tasks under one change request
email
Re: Email

Different scenarios for implementing screen exits

Similar Messages

Maybe you are looking for