Regarding mm flow

hi ,
  pls anybody help me what is mm flow. as an abap developer what we have to know abt it.
thanks
mohan
Moderator  Message: As an ABAP Developer you are supposed to search. Second time you are asking the same question. One more rule violation and your ID will be sent to the gallows!
Edited by: kishan P on Dec 14, 2011 10:17 AM
Edited by: kishan P on Dec 14, 2011 10:36 AM

hi ,
  pls anybody help me what is mm flow. as an abap developer what we have to know abt it.
thanks
mohan
Moderator  Message: As an ABAP Developer you are supposed to search. Second time you are asking the same question. One more rule violation and your ID will be sent to the gallows!
Edited by: kishan P on Dec 14, 2011 10:17 AM
Edited by: kishan P on Dec 14, 2011 10:36 AM

Similar Messages

  • Issue regarding [Work Flow] Business Object Event Raise in ABAP Program

    Hi All,
    I have one issue regarding [Work Flow] Business Object Event Raise in ABAP Program.
    Actual TDS is as below:
    If E message type written, raise Business object BUS2005 (Production order) Event PickShortage for production order passing warehouse, transfer request
    (BUS2065 Object key) in event container. Also include table of text version of error
    messages for this set of Transfer
    Request.
    Can anybody tell me how can i write it technically in ABAP Code.
    Can anybody solve this issue!
    Thanks in advance.
    Thanks,
    Deep.

    Hi,
    Can anybody solve above posted issue!
    Thanks,
    Deep.

  • Regarding work flow

    hi,
    can you please  tell me wht is work flow .
    thanks & regards,
    ramnaresh

    Hi
    Workflow automates the steps and activities in a business process according to predefined procedures and rules.
    Workflow presents information and documents to the appropriate knowledge worker or agent (another entity such as a program) to make a decision or perform an activity.
    Workflow tracks each and every step in the process flow and maintains an ongoing status.
    Workflow also collects and reports all of the metrics associated with the execution and completion of the process.
    Check the below links u will get lot of info..
    http://www.sap-press.com/product.cfm?account=&product=H950
    Workflow
    http://www.sap-img.com/workflow/sap-workflow.htm
    http://help.sap.com/saphelp_47x200/helpdata/en/a5/172437130e0d09e10000009b38f839/frameset.htm
    For examples on WorkFlow...check the below link..
    http://help.sap.com/saphelp_47x200/helpdata/en/3d/6a9b3c874da309e10000000a114027/frameset.htm
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
    http://help.sap.com/saphelp_47x200/helpdata/en/4a/dac507002f11d295340000e82dec10/frameset.htm
    http://www.workflowing.com/id18.htm
    http://www.e-workflow.org/
    http://web.mit.edu/sapr3/dev/newdevstand.html
    Go through the following links on FORK :
    http://help.sap.com/saphelp_nw04/helpdata/en/24/e2283f2bbad036e10000000a114084/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/8d/25f1e7454311d189430000e829fbbd/frameset.htm
    http://help.sap.com/saphelp_46c/helpdata/en/c5/e4a930453d11d189430000e829fbbd/content.htm
    http://www.insightcp.com/res_23.htm
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMSTART/BCBMTWFMSTART.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMDEMO/BCBMTWFMDEMO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMPM/BCBMTWFMPM.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
    For more reference on workflow: http://****************/Tutorials/Workflow/Workflow.htm
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/04/9277a346f311d189470000e829fbbd/frameset.htm
    Check these links.
    http://www.sapgenie.com/workflow/index.htm
    /people/ginger.gatling/blog/2005/12/01/link-workflow-business-objects-to-your-collaboration-tasks
    http://help.sap.com/saphelp_nw04/helpdata/en/92/bc26a6ec2b11d2b4b5006094b9ea0d/content.htm
    http://help.sap.com/saphelp_bw33/helpdata/en/92/bc26a6ec2b11d2b4b5006094b9ea0d/content.htm
    http://help.sap.com/saphelp_bw31/helpdata/en/8d/25f94b454311d189430000e829fbbd/content.htm
    http://www.sap-press.com/product.cfm?account=&product=H950
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
    http://www.workflowing.com/id18.htm
    http://www.e-workflow.org/
    Workflow
    http://www.sap-img.com/workflow/sap-workflow.htm
    http://help.sap.com/saphelp_47x200/helpdata/en/a5/172437130e0d09e10000009b38f839/frameset.htm
    For examples on WorkFlow...check the below link..
    http://help.sap.com/saphelp_47x200/helpdata/en/3d/6a9b3c874da309e10000000a114027/frameset.htm
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
    http://help.sap.com/saphelp_47x200/helpdata/en/4a/dac507002f11d295340000e82dec10/frameset.htm
    http://www.workflowing.com/id18.htm
    http://www.e-workflow.org/
    http://web.mit.edu/sapr3/dev/newdevstand.html
    http://www.sap-img.com/workflow/sap-workflow.htm
    http://help.sap.com/saphelp_47x200/helpdata/en/a5/172437130e0d09e10000009b38f839/frameset.htm
    For examples on WorkFlow...check the below link..
    http://help.sap.com/saphelp_47x200/helpdata/en/3d/6a9b3c874da309e10000000a114027/frameset.htm
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
    http://help.sap.com/saphelp_47x200/helpdata/en/4a/dac507002f11d295340000e82dec10/frameset.htm
    http://www.workflowing.com/id18.htm
    http://www.e-workflow.org/
    http://web.mit.edu/sapr3/dev/newdevstand.html
    Workflow tutorials with step-by-step and with screenshots are available at http://www.****************/Tutorials/Workflow/Workflow.htm
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/42/c14a9b55103116e10000000a1553f7/frameset.htm
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/c5/e4a930453d11d189430000e829fbbd/frameset.htm
    http://www.sapgenie.com/workflow/
    http://www.sap-img.com/workflow/sap-workflow.htm
    http://help.sap.com/saphelp_47x200/helpdata/en/3d/6a9b3c874da309e10000000a114027/frameset.htm
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
    http://help.sap.com/saphelp_47x200/helpdata/en/4a/dac507002f11d295340000e82dec10/frameset.htm
    http://www.sap-basis-abap.com/wf/sap-business-workflow.htm
    https://forums.sdn.sap.com/click.jspa?searchID=791580&messageID=2857887
    https://forums.sdn.sap.com/click.jspa?searchID=791580&messageID=2855919
    https://forums.sdn.sap.com/click.jspa?searchID=791580&messageID=2735228
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMSTART/BCBMTWFMSTART.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMDEMO/BCBMTWFMDEMO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMPM/BCBMTWFMPM.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
    Debug a workflow.
    This has a step by step procedure :
    http://fuller.mit.edu/workflow/debugging.pdf
    www.erpgenie.com/sap/workflow/debugging.htm
    http://www.erpgenie.com/workflow/debugging.htm?2b5de440
    Workflow tutorials with step-by-step and with screenshots are available at
    http://www.****************/Tutorials/Workflow/Workflow.htm
    http://www.sapgenie.com/workflow/
    http://www.sap-img.com/workflow/sap-workflow.htm
    http://help.sap.com/saphelp_47x200/helpdata/en/3d/6a9b3c874da309e10000000a114027/frameset.htm
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
    http://help.sap.com/saphelp_47x200/helpdata/en/4a/dac507002f11d295340000e82dec10/frameset.htm
    http://www.workflowing.com/id18.htm
    http://www.e-workflow.org/
    http://web.mit.edu/sapr3/dev/newdevstand.html
    http://www.sap-basis-abap.com/wf/sap-business-workflow.htm
    https://forums.sdn.sap.com/click.jspa?searchID=791580&messageID=2857887
    https://forums.sdn.sap.com/click.jspa?searchID=791580&messageID=2855919
    https://forums.sdn.sap.com/click.jspa?searchID=791580&messageID=2735228
    http://www.sapbrain.com/TUTORIALS/TECHNICAL/WORKFLOW_tutorial.html
    Regarding Work Flow   
    work flow scenarios.
    1. applying for a leave.
    2. approval process.
    3. material creation process.
    4. mainly work flow is for notification purpose.
    chk this links
    http://help.sap.com/saphelp_erp2005/helpdata/en/fb/135962457311d189440000e829fbbd/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/c5/e4a930453d11d189430000e829fbbd/frameset.htm
    Workflow
    http://www.sap-img.com/workflow/sap-workflow.htm
    http://help.sap.com/saphelp_47x200/helpdata/en/a5/172437130e0d09e10000009b38f839/frameset.htm
    For examples on WorkFlow...check the below link..
    http://help.sap.com/saphelp_47x200/helpdata/en/3d/6a9b3c874da309e10000000a114027/frameset.htm
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
    http://help.sap.com/saphelp_47x200/helpdata/en/4a/dac507002f11d295340000e82dec10/frameset.htm
    http://www.workflowing.com/id18.htm
    http://www.e-workflow.org/
    http://web.mit.edu/sapr3/dev/newdevstand.html
    http://www.erpgenie.com/workflow/index.htm
    http://www.sap-basis-abap.com/wf/sap-business-workflow.htm
    http://www.insightcp.com/res_23.htm
    A good tutorial
    http://www.thespot4sap.com/articles/Invoice_Verification_Automation_Using_SAP_Workflow.asp
    http://www.sap-basis-abap.com/wf/sap-business-workflow.htm
    /people/alan.rickayzen/blog
    /people/jocelyn.dart/blog/2006/06/19/why-use-abap-oo-with-workflow
    a good book
    http://www.sap-press.com/product.cfm?account=&product=H950
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
    http://help.sap.com/saphelp_47x200/helpdata/en/4a/dac507002f11d295340000e82dec10/frameset.htm
    http://www.sap-press.com/downloads/h950_preview.pdf
    Check the following PDF
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMSTART/BCBMTWFMSTART.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMDEMO/BCBMTWFMDEMO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMPM/BCBMTWFMPM.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
    also seach the workflow forum: SAP Business Workflow
    Regards
    Anji

  • Regarding [Work Flow] Business Object Event  Raise in ABAP Program

    Hi All,
    I have one issue regarding [Work Flow] Business Object Event Raise in ABAP Program.
    Actual TDS is as below:
    If E message type written, raise Business object BUS2005 (Production order) Event PickShortage for production order passing warehouse, transfer request
    (BUS2065 Object key) in event container.  Also include table of text version of error
    messages for this set of Transfer
    Request.
    Can anybody tell me how can i write it technically in ABAP Code.
    Can anybody solve this issue!
    Thanks in advance.
    Thanks,
    Deep.

    Hi,
    Can anybody solve above posted issue!
    Thanks,
    Deep.

  • No document flow updated in Service Order regarding MM flow i.e. PR, PO, GR

    Hello,
    On creating a service order in CRM, the purchase requisition is created automatically in R/3 for the spare parts entered.
    But this PR information is not getting updated in the service order's document flow in CRM.
    I analysed the flow and found that PR gets successfully created and sends back the document flow data to CRM inbound queue.
    The BDoc type involved is CRM_SRV_XTN.
    In it's Extended part, there is a field called ORDERADM_H_GUID which is correctly filled in the BAPIMTCS structure in R/3 which is converted to probably XML format through macro MOVE_CASTING and sent to CRM inbound queue (function module BAPI_CRM_SAVE).
    However, on debugging the respective inbound queue in CRM, I noticed that the field ORDERADM_H_GUID value is not the same as filled in R/3 but some CONSTANT value like 00230023002300560023002300230023 in all the cases.
    Also, FYI, the fieldu2019s value in R3 after conversion looks like as following u2013
    #########################0000000000 ########䣴Ώ삷#耀諣뢮########     48F4038FC0B70093E10080008AE3B8AE
    While in CRM i.e. FM BAPI_CRM_SAVE it looks as follows u2013
    #########################0000000000 ########################     48F4038FC0B70093E10080008AE3B8AE
    So there I feel that the value what is sent from R/3 is not the same as recieved in CRM, on XML conversion.
    Please advise what could be the reason for this anomaly.
    Thanks and regards,
    Manish

    unfortunately document flow in PS is not like in SD
    only in ECP there is a limited possibility
    you can see the line item report and activate the relationship browser which will give the details of the documents related to that posting
    other than that nothing

  • Regarding work flow for credit block release in sales order

    Dear Experts,
    Kindly help me with work flow-
    my scenario is if customers credit limit of 5000$ exceeds in sales order it should be blocked and notification should go to authorize person through simple mail to release this block.
    for this i have done settings in out control i have used output type krml and determined partner as employee responsible to release block in customer master but mail is not triggered to authorized person for credit block and how i can create work flow for this so that authorized person should get notify for credit block as well he releases block also.
    Regards
    Supriya

    Dear supriyaparimal,
    Please find the below points to fix your issue.
    1. Configure the out put determination by using the condition type KRML.(Hope oyu have done it already).
    2.Maintain the condition records in VV11 for condition type "KRML"
    3.Then select the condition record and click the communication tab .
    4. If you want to give any information you can use "Note for recipient".
    5. If the information has to be sent to relevant person you recipient name in the recipient column.
    Save the documnet.
    If you raise the sales order and if it is blocked then system automatically send the information to respective person.
    You can get this in formation in ""SBWP" transaction code.
    Check the in box, the information what you have mentioned in the condition records will be appeared.
    Please let me know if you have any clarifications
    Thanks&Regards
    raghu.k

  • Regarding the flow logic in screen painter

    Hi Experts
    I am a BW guy and i am new to ABAP and i need your help to solve my problem.
    I have created a table for master data(zemp_data) in R/3 se11..which has fields like zempid,zempname,zmgrid,zdeptid,zdeptname and i have created the respective fields in screen painter too but my problem is i dont know how to link this fields  in the screen painter to the  fields in table .to be more clear i want the flow logic or module pool code to link this table when i give an entry in the screen painter for the respective  fields..i will really appreciate your answers and award the maximum points for the usefull answer ..as i dont know ABAP much if it is a step by step approach ..that would be helpfull
    Regards,
    RK.

    Hi Karthik,
    Please consider the following
    In the screen...the fields must be from the database table in Se11..(in screen painter -> use.."get from Dictionary" -> enter the table name -> select the fields -> drag and drop on the screen) or must have the same name in the database table..This will be a link but unless you code to fetch values from database or update values to database there will be no action taking place
    Usually in the PBO(process befor output) we write the code to display values before we accept data from the user ie,set default values on the screen if required and prepare the screen for user input
    in the PAI of the screen painter we can do data processing ie, data validations,checks and saving based on what the user wants
    So imagine you have buttons placed on the screen and there are buttons from standard application bar like BACK,SAVE, set using PFstatus..all the user actions will be linked to a function cod..ie whenever user presses a button we can uniquely idntify what was pressed by assigning a function code to each button in the menu painter or PF status and do the action accordingly
    Assume that you have created a push button on the screen painter and assigned it a function code "PUSH"
    so whenever you press the button in the variable sy-ucomm "PUSH" will be captured..this you can check in PAI for the screen like
    Case sy-ucomm.
    when 'PUSH'.
    do the needful coding
    when 'SAVE'
    Modify database table
    endcase.
    you can check the standard demo programs in SE38 -> program name-> display for basic ABAP coding you have asked for
    (1)demo_dynpro_input_output .
    (2)demo_dynpro_dictionary
    (3)demo_dynpro_push_button
    Pls let us know if you need more help on the same
    Reward if helpful
    Regards
    Byju

  • Regarding Business Flow of PP,PM,PS,QS Modules

    Hi,
    Can anybody tell me the Business Process<b>[Flow's]</b> of <b>PP, PM, PS, QS</b> modules in <b>SAP</b> with their respective transaction codes[TCode's] and important tables for each of them.
    Can anybody reply about the same.
    Thanks in advance.
    Thanks & Regards,
    Prasad.

    FI Financial Accounting
    designed for automated management and external reporting of general ledger, accounts receivable, accounts payable and other sub-ledger accounts with a user defined chart of accounts. As entries are made relating to sales production and payments journal entries are automatically posted. This connection means that the "books" are designed to reflect the real situation.
    The FI module has 8 sub modules:
    FI-GL
    General Ledger Accounting
    FI-LC
    Consolidation
    FI-AP
    Accounts Payable
    FI-AR
    Accounts Receivable
    FI-BL
    Bank Accounting
    FI-AA
    Asset Accounting
    FI-SL
    Special Purpose Ledger
    FI-FM
    Funds Management
    CO Controlling
    represents the company's flow of cost and revenue. It is a management instrument for organizational decisions. It too is automatically updated as events occur.
    The CO module has following sub modules:
    CO-OM
    Overhead Costing (Cost Centers, Activity Based Costing, Internal Order Costing)
    CO-PA
    Profitability Analysis
    CO-PC
    Product Cost Controlling
    for tables check out link..
    http://www.sapgenie.com/abap/tables_fi.htm
    MM Process flow:
    Process Flow
    The typical procurement cycle for a service or material consists of the following phases:
    1. Determination of Requirements
    Materials requirements are identified either in the user departments or via materials planning and control. (This can cover both MRP proper and the demand-based approach to inventory control. The regular checking of stock levels of materials defined by master records, use of the order-point method, and forecasting on the basis of past usage are important aspects of the latter.) You can enter purchase requisitions yourself, or they can be generated automatically by the materials planning and control system.
    2. Source Determination
    The Purchasing component helps you identify potential sources of supply based on past orders and existing longer-term purchase agreements. This speeds the process of creating requests for quotation (RFQs), which can be sent to vendors electronically via SAP EDI, if desired.
    3. Vendor Selection and Comparison of Quotations
    The system is capable of simulating pricing scenarios, allowing you to compare a number of different quotations. Rejection letters can be sent automatically.
    4. Purchase Order Processing
    The Purchasing system adopts information from the requisition and the quotation to help you create a purchase order. As with purchase requisitions, you can generate Pos yourself or have the system generate them automatically. Vendor scheduling agreements and contracts (in the SAP System, types of longer-term purchase agreement) are also supported.
    5. Purchase Order Follow-Up
    The system checks the reminder periods you have specified and - if necessary - automatically prints reminders or expediters at the predefined intervals. It also provides you with an up-to-date status of all purchase requisitions, quotations, and purchase orders.
    6. Goods Receiving and Inventory Management
    Goods Receiving personnel can confirm the receipt of goods simply by entering the Po number. By specifying permissible tolerances, buyers can limit over- and underdeliveries of ordered goods.
    7. Invoice Verification
    The system supports the checking and matching of invoices. The accounts payable clerk is notified of quantity and price variances because the system has access to PO and goods receipt data. This speeds the process of auditing and clearing invoices for payment.
    Common Tables used by SAP MM
    Below are few important Common Tables used in Materials Management Modules:
    EINA Purchasing Info Record- General Data
    EINE Purchasing Info Record- Purchasing Organization Data
    MAKT Material Descriptions
    MARA General Material Data
    MARC Plant Data for Material
    MARD Storage Location Data for Material
    MAST Material to BOM Link
    MBEW Material Valuation
    MKPF Header- Material Document
    MSEG Document Segment- Material
    MVER Material Consumption
    MVKE Sales Data for materials
    RKPF Document Header- Reservation
    T023 Mat. groups
    T024 Purchasing Groups
    T156 Movement Type
    T157H Help Texts for Movement Types
    MOFF Lists what views have not been created
    A501 Plant/Material
    EBAN Purchase Requisition
    EBKN Purchase Requisition Account Assignment
    EKAB Release Documentation
    EKBE History per Purchasing Document
    EKET Scheduling Agreement Schedule Lines
    EKKN Account Assignment in Purchasing Document
    EKKO Purchasing Document Header
    EKPO Purchasing Document Item
    IKPF Header- Physical Inventory Document
    ISEG Physical Inventory Document Items
    LFA1 Vendor Master (General section)
    LFB1 Vendor Master (Company Code)
    NRIV Number range intervals
    RESB Reservation/dependent requirements
    T161T Texts for Purchasing Document Types
    Tcodes:
    RFQ to Vendor - ME41
    Raising Quotation - ME47
    Comparison of Price - ME49
    Creation of PO - ME21N
    Goods Receipt - MIGO
    Invoice (Bill PAssing) - MIRO
    Goods Issue - MB1A
    Physical Inventory - MI01( Create doc)
    MI04 (Enter Count)
    MI07 (Post)
    SD FLOW..
    Main steps:
    Creation of Inquiry - VA11
    Creation of Quotation - VA21
    Creation of Sale Order - VA01
    Delivery - VL01
    Billing - VF11
    TAbles:
    6 Sales and Distribution (SD) :
    VBFA Document flow (alg.)
    VTFA Flow shipping documents
    6.1 Sales order :
    VBAK Header data
    VBAP Item data
    VBPA Partners in sales order
    VBKD Sales district data
    VBEP Data related to line items, delivery lines
    6.2 Billing document :
    VBRK header data
    VBRP Item data
    6.3 Shipping :
    VTTK Shipment header
    VTTP Shipment item
    VTTS Stage in transport
    VTSP Stage in transport per shipment item
    VTPA Shipment partners
    VEKP Handling Unit - Header Table
    VEPO Packing: Handling Unit Item (Contents)
    6.4 Delivery :
    LIKP Delivery header
    LIPS Delivery item
    6.5 Pricing :
    KONH Conditions header
    KONP Conditions items
    KONV Procedure ( billing doc or sales order)
    KOND
    6.6 contracts :
    VEDA Contract data
    Refer this link:
    http://www.sap-img.com/sap-sd.htm
    Document Flow in Sales
    The sales documents you create are individual documents but they can also form part of a chain of inter-related documents. For example, you may record a customer’s telephone inquiry in the system. The customer next requests a quotation, which you then create by referring to the inquiry. The customer later places an order on the basis of the quotation and you create a sales order with reference to the quotation. You ship the goods and bill the customer. After delivery of the goods, the customer claims credit for some damaged goods and you create a free-of-charge delivery with reference to the sales order. The entire chain of documents – the inquiry, the quotation, the sales order, the delivery, the invoice, and the subsequent delivery free of charge – creates a document flow or history. The flow of data from one document into another reduces manual activity and makes problem resolution easier. Inquiry and quotation management in the Sales Information System help you to plan and control your sales.
    Technical Details
    Inquiry - va11/va12/va13
    Quotation - Va21/va22/va23
    Sales Order - va01/va02/va03
    Delivery - vl01n/vl02n/vl03n
    Billing/Invoicing - vf01/vf02/vf03
    PP FLOW..
    SAP - Project Planning
    Project Planning
    PROJ
    (Project Definition)
    PRPS
    (WBS Elements)
    PRPS-PSPHI =
    PROJ-PSPNR
    PRTE
    (Schedule Data for
    Proj. Item)
    PRPS-PSPNR =
    PRTE-POSNR
    and
    PRPS-PSPHI=
    PRTE-PSPHI
    PRTX
    (Texts(WBS))
    PRTX-PRPSPNR =
    PRTE-POSNR
    PRHIS
    (Proj. Hierarchy for
    WBS Element)
    PRPS-PSPNR =
    PRHIS-POSNR
    and
    PRPS-PSPHI=
    PRHIS-PSPHI
    PSTX
    (Project Texts
    (Header))
    PSTT
    (Project Texts)
    PRTX-PRTXTKY =
    PSTX-PRTXTKY
    PSTX-PRTXTKY =
    PSTT-PRTXTKY
    PP
    Table Mapping
    SAP PP - Project Planning
    PROJECTS
    Project and WBS element numbers have a domain with a conversion
    function module which converts it from 8 numc input to 24 char on output.
    PROJ
    (Project definition)
    Project Number (PSPNR)
    Project Name (PSPID)
    PRPS
    (WBS (Work Breakdown Structure)
    Element Master Data))
    Project Number (PSPHI)
    WBS Element Number (PSPNR)
    WBS Name (POSID)
    Project Number (PSPHI)
    WBS Element Number (POSNR)
    PRTE
    (Scheduling Data for Project Item)
    PRTX
    (PS Texts (WBS)
    Project Number (PSPHI)
    WBS Element Number (POSNR) PSTX
    (PS Texts (Header))
    Text Identifier (PRTXTKY)
    PS text description (PSTXTTI)
    WBS Element Number (PRPSPNR)
    Text Identifier (PRTXTKY)
    PRHIS
    (Standard WBS, Edges (Hierarchy
    pointers))
    PSTT
    (PS texts (description))
    Text Identifier (PRTXTKY)
    PS text: Description(PTKTEXT)
    Message was edited by: kishan negi

  • Regarding Message Flow in XI

    Hi Experts,
    I was go through the Blog given by Siva Maranani
    /people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi
    But in this After sending the Xi Message from send Queue to Integration Engine...
    What wi be the process inside this IE.
    Please let me know
    Regards
    Khanna

    <i>But as per my knowledge in the IS the Pipeline services wil be done( Includes Receiver det, Interface Det, Mapping, Logical rout, Tech. routing, Call Adapter, Message Split )
    It means there is no further process inside the IE??????????</i>
    Messages received at the Integration Server are processed through a defined series of steps called Pipeline Services. These pipeline services are part of Integration Engine which in turn is a part of Integration Server
    <i>Only the XI Adapter wil pick the Xi msg from Send Queue to IE.......Thats it?????/</i>
    Yes. Thats the main task of XI Adapter. It also does the SLD lookup.
    <i>
    then this IE wil pass this XI Msg to the IS ..... Right????????</i>
    As mentioned, IE is part of IS
    Regards,
    Prateek

  • Regarding data flow in SAP XI

    Hello Friends,
    In Landscape where XI connected to system(s), is there any way to find how the data flows through or how it is designed to connect other systems in SAP XI other than SLD
    thanks

    If you are looking for any specific landscape and trying to make out how the message flow, then i think you need
    to get the Technical and functional specification documents and based on that you can get a clear picture of
    how different interface are designed and which systems they are connecting.
    Regards
    Srinivas

  • Regarding Docment flow in DMS

    Hi , DMS Gurus
    I have created  no of document types, in dms system.now i want the moment I created the document , an information messages should reached to the particular  users
    Therer are two types of users herer, one for
    1.One have authorit to make changes in the docuemnts
    2.others have to display only nad information.
    Could anybody guide how to do this with Workflow and without workflow

    Hi Bhupendrasingh
    First Deceide what process you want to happen in workflow using SAP DMS.
    Means Draft Process flow which mentions what happens when a DIR is created?
    Which are the users who should have change and display rights.Decide the logic to whom this documents should be sent.If you have Organizational Structure( SAP HR ) Implemented in your company use it or create yuou own logic.
    Make sure the user who are viewing the document must have SAP user IDs with proper Authorization objects assigned to him.
    And also my request is you sit with a Workflow consultant to design your workflow requirement.He will guide you properly.Try to use MS Visio tool provided by Microsoft for designing workflow.
    I have used it it and helped me and my workflow consultant to do workflow design very fast.
    with Regards
    Mangesh Pande

  • Regarding Execution flow in webdynpro component

    Hi all,
              I am confused regarding the execution flow.
    we have "component controller" and "view controller" in a webdynpro component.
    I have written some code in "wdDoInit" of  "component controller" and in "wdDoInit" of "view controller" and in "wdDoModifyView" of  "view controller" .
    If I do "Deploy and Run " the application , Which one is executed first ,I mean how is the code processed ,where the control reaches first?
    Thanks in advance.

    In a web dynpro application there is always a interface view specified.
    This interface view is associated with a window. The window has set of views with one as default view.
    When Web Dynpro application is launched, the window is instantiated via interface view specified. The window after instantiation is rendered on the brower/some other UI client.
    The window when instantiated will instantiate the default view also. So wdDoInit of view controller will be called now. Now if navigation happens to some other view in the window that particular view has to be instantiated. So the wdDoInit of that view will be called then.
    Is your question answered ?
    Regards,
    Ashwani Kr Sharma

  • Regarding document flow

    what is document flow in abap.
             could u plz explain clearly,.

    Hi,
    Document flow is not in ABAP, it is with respect to a Functional Module like SD, MM ,FI or PP or PM etc.
    In each module there will be business flow, means which document comes first and which document comes late.
    For example If take SD:
    Inquiry, quotation, sales Order, Delivery (PGI) and billing is the document flow
    In MM:
    PR, RFQ, PO, GR and Invoice Verification is the document flow
    Hope this helps,
    regards,
    Anji

  • Best practice regarding work flow (cutting, applying effects, exporting etc)

    Hi!
    I've been asked to shoot and edit a music video for a friend of mine, and I'm trying to figure out the best way to manage this project in PrE (in what order to do things and so on). I have a picture in my head which make sence, but I'd like to have it confirmed. If you've been following the "Very disappointed with Premiere Elements" thread, you know I'm not a fan of how the applying of effects works, when having a lot of cuts between scenes and clips etc. A few of the steps below is meant to make that process more effective.
    So, here's my idea, from the begining and in detail:
    1. Download the appropriate clips from the camera (in this case 1280x720, H.264 mov's from an EOS 500D).
    2. Create a PrE-project for each clip and maybe trim the in and outs a bit, if needed.
    3. Export each clip to uncompressed avi's.
    4. Create the main project file and import all the uncompressed avi's.
    5. Insert the clips in on appropriate tracks in the timeline.
    6. Do all the cutting, triming and sync as complete as possible, without thinking about effects.
    7. When finished, open up each of the smaller clip projects and add the desired effects. This will mainly include contrasts, color corrections, noise etc, in order to get the right look and feel to each clip/scene.
    8. Again, export the clips to uncompressed avi's and overwrite the previous versions.
    9. Open up the main project, which now should contain the clips with look-and-feel effects visible.
    10. Add some additional effects if needed.
    11. Export/share, and you're done.
    Of course I will end up going back and forth through these steps anyway, but as a basic plan it seems reasonable. I see three main positive aspects:
    1. The look-and-feel effects will be applied on the raw material, before the converting process. This should result in a slightly better quality. Perhaps not noticeable, but anyway.
    2. The main project will be more CPU friendly and easier to work with.
    3. If I want to tweek the look-and-feel effect to a clip/scene, I don't have to do it on every split (I will have a lot of splits, so applying and changing the effect parameters will be time consuming and ineffective). Of course, opening up the clip's specific project, changing the effect and then export to avi, will also take time, but point 1 and 2 makes up for that.
    Have in mind that it is a music video project, to put things in the right context. We'll probably have a few parallel stories/scenes, with lots of cutting in and out between them. The timeline will probably look insane.
    So, am I thinking in the right direction here? Any traps I might fall into along the way?
    Regards
    Fredrik

    Fredrik,
    Though similar to your workflow, here is how I would do it.
    Import those "raw" Clips into a Project, and do my Trimming in that Project, relying on the Source Monitor to establish the In & Out Points for each, and also using different Instances of any longer "master Clip.". I would also do my CC (Color Correction), and all density (Levels, etc.) Effects here. Do not Trim too closely, as you will want to make sure that you have adequate Handles to work with later on.
    Use the WAB (Work Area Bar) to Export the material that I needed in "chunks," using either Lagarith Lossless CODEC, or UT Lossless CODEC *
    Import my music into a new Project and listen over and over, making notes on what visuals (those Exported/Shared Clips from above) I have at my disposal. At this point, I would also be making notes as to some of the Effects that I felt went with the music, based on my knowledge of the available visuals.
    Import my Exported/Shared, color graded Clips.
    Assemble those Clips, and Trim even more.
    Watch and listen carefully, going back to my notes.
    Apply any additional Effects now.
    Watch and listen carefully.
    Tighten any edits, adjust any applied Effects, and perhaps add (or remove existing) more Effects.
    Watch and listen carefully.
    Output an "approval" AV for the band/client.
    Tweak, as is necessary.
    Output "final approval" AV.
    Tweak, as is necessary.
    Export/Share, to desired delivery formats.
    Invoice the client.
    Cash check.
    Declare "wine-thirty."
    This is very similar to your proposed workflow.
    Good luck,
    Hunt
    * I have used Lagarith Lossless CODEC with my PrE 4.0, but have not tried UT. Both work fine in PrPro, so I assume that UT Lossless will work in PrE too. These CODEC's are fairly quick in processing/Exporting, and offer the benefit of smaller files, than Uncompressed AVI. They are visually lossless. The resultant files will NOT be tiny, so one would still need a good amount of HDD space. Neither CODEC introduces any artifacts, or color degredation.

  • Regarding work flow in the organisation

    Hello,
          I am new to SAP XI. I want to join as a SAP XI developer. So I want to know about the work flow in the organisation. Means who will raise issues and who will take care of it first. and how it will reach to SAP XI developer.
        What are the human roles in the SAP XI Work flow in the organization and what are their responsibilities. Who will responsible to  write the Java mapping coding or ABAP mapping coding or XSLT mapping coding.
    Thank you
    Edited by: jyotsna dm on Apr 12, 2008 6:54 AM

    Hi,
    In XI: It is separated in two parts
    1) XI basis (Administration)
    Activites are:
    1) XI installation
    2) Configuration activitie
    3) Post installation checks
    4) SLD configuration
    5) Create Users,
    6) Role assignments.
    And many more
    2) XI Implementation and development.
    Under the development you have two parts Integration repository which is desing part which involves small amount of Java knowledge whenever your requirement is not fulfilled by standard SAP XI function.
    and integration Configuration:
    This is very simple stpes once your design is over.Based on your requirement you have to use the standard adapter provided by SAP for example if file is coming then u will go for File adapter,if IDOC is psoted to R3 then you go for IDOC adapter,communication with remote client u go for SOAP adapter.
    XI Project lifecycle:
    1) Blue printing phase (Design phase).
    2) Build phase (Development)
    3) Integration testing
    4) Project go live
    5) Support.
    Now coming to ur question.
    XI Developers role and responsibilities are:
    •     Analysis of the Functional Specifications which is received from Function people.
    •      Understanding the processes related to the third party non SAP and SAP systems.
    •     Raise issue log for the business requirement which is not understood from functional spec.
    •     Prepare Technical Specification Document,
    •     Do the development: now developer has to do the coding which either involved java,XSLT,abap mapping.
    •     Prepare the UTC
    •     Reviewing Interface Technical Specifications and Unit Test Document, Interface build and Unit Test, Self and peer review of the deliverables, develop Interface Object via Design and Configuration.
    •     Project golive and give support and do bug fixing,change request n all.
    hopw u got the prefect workflow.
    chirag

  • Regarding work flows

    hi can any one tell me what is workflow? where is it used ? how a workflow is created in SAP XI

    Work Flow
    Unit 1: Organizational Structure
    Use
    In order for the workflow system to establish the relationship between the requester and their superior, you must create an organizational plan in the system.
    For this tutorial, of course, this organizational plan does not have to be complete and valid across the enterprise. To keep the test as simple as possible initially, define an organizational plan that only contains one administrator and one head of department.
    Assign both items to yourself. As a result, all work items will appear in your own Business Workplace. Later you will modify the organizational plan such that you will have to work through the scenario with two users.
    Procedure
    The organizational plan required for this tutorial consists, when complete, of one organizational unit (= "department"), which contains two positions: a head of department and an administrator.
    Each position is described by one job and each position is assigned one user as holder. The head of department position is also designated as chief position of the organizational unit.
    Of course, a "real" organizational plan is created by arranging several organizational units with their positions in a hierarchy. Usually several positions are described by one job.
    For further information, refer to the documentation  Organizational Plan.
    The procedure in this unit is divided into four parts:
    1.     You create an organizational unit.
    2.     Enter necessary jobs as required.
    3.     You create a position for the head of department in the new organizational unit.
    You define a position in three steps:
    i.     You create a position that is assigned your organizational unit.
    ii.     You assign a holder to the position.
    iii.     You assign a job to the position.
    3.     You create a position for the administrator in the organizational unit.
    Creating an organizational unit
    1.     Choose Tools &#61614; SAP Business Workflow &#61614; Development &#61614;&#61472;Definition tools &#61614; Organizational Management &#61614; Organizational plan &#61614; Create (T.Code: PPOCW).
    2.     Confirm the validity period proposed in the dialog box Creating a Root Organizational Unit.
    This takes you to the Create Organization and Staffing (Workflow) screen. This user interface is divided into four screen areas:
    3.     On the Basic Data tab in the details area, enter an abbreviation and a name in the Organizational unit input fields.
    Abbreviation: <ini_sales>
    Name: <OrgUnit: Sales (ini)>
    4.     Choose  .
    You can now create the position for a head of department and one administrator.
    Create jobs
    When enhancing an organizational unit, the necessary jobs are usually already available. For this tutorial however, you create the necessary jobs for head of department and administrator yourself.
    1.     Choose Edit &#61614; Create jobs.
    You go to the dialog box Create jobs. The lower area contains a list of existing jobs and the upper area contains an input table in which you can create new jobs by entering abbreviations and names.
    2.     In the input table, enter an abbreviation and a name for each of the new jobs.
    Job - head of department:
    Object abbreviation: < ini_dhead_C >
    Name: < job: head of department (ini) >
    Job administrator:
    Object abbreviation: < ini_admi_C >
    Name: < job: administrator (ini) >
    3.     Choose  .
    Creating Position for Head of Department
    1.     Change to the overview area in the staff assignments of the organizational unit, in order to assign positions, jobs and holders. Choose the arrow  on the right next to the  and then the staff assignments (list).
    2.     Choose  .
    A new position is then created in the staff assignments and is displayed in a new line in the table. The position is vacant and no job is assigned to it.
    3.     Open the details view for the new position in the details area by double-clicking on the entry in the table.
    4.     On the Basic Data tab, enter a code and a description in the Position input fields. Overwrite the previous contents.
    Abbreviation: < ini_dhead_S >
    Description: < position: head of department ( ini ) >
    Assigning a holder to the position
    You now assign R/3 users to the positions. The staff assignments for your organizational unit are displayed and you see the vacant position in the table.
    5.     Select User in the search area and enter the search criteria in order to find your user names.
    All of the user names that match your search criterion are listed in the selection screen.
    6.     Select your user name in the selection area and drag it to the Person/User column of the position in the overview area.
    Confirm the message that the relationship period of the validity has been changed.
    7.     Set the Head of own organizational unit indicator in the details area.
    Assigning a job to the position
    Assign the job of the head of department you created earlier to the position.
    8.     Select Job in the search area and enter the search criteria in order to find the job of the head of department.
    All jobs that match your search criterion are listed in the selection screen.
    9.     Select job: head of department ( ini) in the selection area and drag it to the Job column of the position in the overview area.
    10.     Choose  .
    The job is assigned the position. Check this by switching to the staff assignments of the organizational unit. Select the organizational unit in the overview area, choose the arrow  on the right next to the  and then the staff assignments (list). The newly created job is displayed in the job column.
    Create position for administrator and assign holder and job
    You are now in the staff assignments of the organizational unit.
    1.     Choose  .
    A new position is then created in the staff assignments and is displayed in a new line in the table. The position is vacant and no job is assigned to it.
    2.     On the Basic Data tab in the details area, enter an abbreviation and a name in the Position input fields. Overwrite the previous contents.
    ID: <ini admiS >
    Description: < position: administrator ( ini ) >
    3.     Choose  .
    4.     Select User in the search area and enter the search criteria in order to find your user names.
    5.     Select your user name in the selection area and drag it to the Person/User column of the position in the overview area.
    Confirm the message that the relationship period of the validity has been changed.
    6.     Select Job in the search area and enter the search criteria in order to find the job of the administrator.
    7.     Select job: administrator ( ini) in the selection area and drag it to the Job column of the position in the overview area.
    8.     Choose  .
    Result
    Display your entire staffing schedule again and make sure that all the information listed is correct.
    You can display a detailed view of jobs, users, and positions. Choose the relevant cell in the table by double-clicking it.
    In the details view of a position or job, all of the assigned tasks are displayed on the Tasks tab.
    You have now completed the first unit (defining the organizational plan). You can now start on the next unit. To exit processing of the organizational structure, choose Back.
    Unit 2: Creating a Workflow
    Use
    To define the flow of the approval process in the system, you first create a multistep task workflow template.
    For further information, refer to Definition of Multistep Tasks in the SAP Business Workflow documentation.
    Procedure: Creating a workflow template
    1.     Choose Tools &#61614; Business Workflow &#61614; Development &#61614;&#61472;Definition Tools &#61614; Tasks/Task Groups &#61614; Create (T.Code PFTC_INS)
    This takes you to the Task: Maintain screen.
    2.     In the Task type field, choose the Workflow template entry.
    3.     Choose  .
    The Workflow Template: Add screen is then displayed.
    Entering the basic data for the workflow template
    1.     Enter an abbreviation (of your choice) and a name (of your choice) for the workflow template to be created.
    Abbreviation: < ini _ws>
    Name: <Workflow: notification of absence ( ini )>
    2.     Choose  .
    3.     In the Create Object Directory Entry dialog box, choose Local object.
    The system has now allocated an 8-digit number for your workflow template. This number is made up of the 3-digit prefix number (Customizing setting) and a 5-digit number taken from a number range. This number together with the letters WS forms the workflow ID. Make a note of the ID so that you can later call the workflow more quickly.
    Entering a workflow description
    4.     Go to the Description tab.
    5.     Choose the text type Task description and then  .
    The SAPscript text editor is then launched.
    6.     Enter a text that describes the task. You can use the following proposal:
    <You can use this workflow to create a notification of absence. This will then be sent to your superior for review. You will be notified of the result of this review.
    If your request is rejected, you can revise it and resubmit it for review or withdraw it completely.>
    7.     Choose  to return to the workflow template and then save the workflow template.
    Determining agents
    To enable the workflow template to be started in dialog, the workflow template must be assigned to its possible agents.
    8.     Select Additional data &#61614;&#61472;Agent assignment &#61614; Maintain
    The workflow template: agent assignment screen is displayed.
    9.     Position the cursor on the name of your workflow template.
    10.     Choose Properties…
    The dialog box Task: <Workflow: Notification of absence (ini)> is displayed.
    11.     Set the General task flag.
    12.     Choose  Copy and then  .
    Designating your workflow template as a general task means that every user in the system is authorized to start this workflow template in dialog.
    Result
    You have now created a workflow template as a "framework" for a workflow definition.
    To create a workflow definition, you need tasks that are used as steps in the workflow definition.
    Additional information: Tasks
    A task can either be a single-step task or a multistep task. In our example of the notification of absence, making the application and checking the application are single-step tasks. The entire procedure involved in processing a leave request consists of these (and other) single steps, and is therefore a multistep task.
    In this tutorial, a single step task is generally described as a task. The difference between the task types is only explicitly explained if there is a risk of confusion over multistep tasks. The term workflow is used as the umbrella term for the workflow template (and thus the multistep task) and the workflow definition. More precise differentiation only takes place if there is a risk of confusion.
    On a technical level, the main difference between single-step tasks and multistep tasks is that:
    •     Every single-step task refers to an object method
    •     Every multistep task refers to a workflow definition
    A workflow definition is made up of a sequence of different steps (for example, all steps required to process a leave request).
    Standard tasks and workflow templates are client-independent. Customer and workflow tasks are client-dependent. Customer and workflow tasks are no longer supported and are therefore no longer used in this tutorial.
    An Activity is a possible step type in a workflow definition. An activity refers to a task. It references a task, which can be a single-step or multistep task (subworkflow).
    For further information, refer to Tasks and Task Groups in the SAP Business Workflow documentation.
    Unit 4: Defining and Inserting Task "Create Notification of Absence"
    Use
    The notification of absence is created in the first step of the workflow. You will also need a task that executes this function. You can create the task separately from the workflow definition or directly from the Workflow Builder. This unit describes how you create the task from the Workflow Builder.
    For further information on creating an individual task, refer to Definition of Single-Step Tasks in the SAP Business Workflow documentation.
    Prerequisites
    This task is a single-step task and it references one object method. The object type used (FORMABSENC (notification of absence)) and the required method (Create) are already defined and implemented in the Business Object Repository.
    You are in the Workflow Builder and the initial workflow definition is displayed.
    Procedure
    Creating an Activity as a Step in the Workflow Definition
    Add a first step of the type Activity to the workflow definition.
    1.     Choose  under step type. The cursor changes shape.
    2.     Position the cursor on the Undefined step and click.
    By doing so, you add an activity to your workflow definition. The step definition is shown in the right-hand part of the screen. You are on the tab page Control.
    Defining a Task "Create Notification of Absence"
    You now create a new task, with which a notification of absence can be created.
    1.     Choose the arrow  on the right next to the  and then Create task.
    The Basic data tab in the Standard task: Create screen is then displayed.
    Entering the basic data
    2.     Enter an abbreviation (of your choice) and a name (of your choice) for the standard task to be created.
    Abbreviation: < ini _creat>
    Name :<Create notification of absence (ini)>
    Work item text
    The work item text appears as an information text in the Business Workplace as soon as there is a work item for the step with this task.
    3.     Enter Create notification of absence in the Work item text field.
    Object type and method
    4.     Enter an object type and a method:
    Object type: FORMABSENC
    Method: CREATE
    You can also use the F4 input help to select the method. Additional indicators associated with this method are set automatically.
    You can view the definition of the object type entered by double-clicking on it. Information about its components is provided.
    5.     Save your task as a local object.
    The system has now allocated an 8-digit number for your task. This number is made up of the 3-digit prefix number (Customizing setting) and a 5-digit number taken from a number range. The identification of this task consists of TS and the eight digit number.
    Determining agents
    Selecting the possible agents for this task determines who is to be authorized to make leave requests. For this task, this should be all employees in your enterprise. Define the task as a general task.
    1.     Select Additional data &#61614;&#61472;Agent assignment &#61614; Maintain
    This takes you to the Standard task: Maintain Agent Assignment screen.
    2.     Position the cursor on the name of your task.
    3.     Choose Properties…
    The dialog box Task: <Notification of absence (ini)> is displayed.
    4.     Set the General task indicator.
    5.     Choose  Copy and then  .
    6.     Exit the task definition with  .
    Interim result
    You have now defined your first task in full. This task is used in the activity that you created in the Workflow Builder.
    Completing Activity
    The Define Container Elements and Binding dialog box is then displayed in which the system proposes a change to the workflow container and a binding definition.
    •     Upper part of the dialog box: Proposal for new container elements in the workflow container.
    The system proposes that you create a local container element in the workflow container, which can store the reference to the notification of absence created in this step. The element has the technical name AbsenceForm .
    •     Lower part of dialog box: Proposed binding definition
    The system proposes that you define a binding from the task container to the workflow container. This binding transports the reference to the generated object (i.e. the created notification of absence) from the task (from the WIObject_ID element in the task container) to the workflow (to the AbsenceForm element in the workflow container).
    Further information on automatic binding definition proposals is available under Binding Definitions from the Workflow Container and Binding Definitions from the Task Container in the documentation on SAP Business Workflow.
    1.     Confirm the proposal with  .
    The new AbsenceForm container element is displayed in the workflow container. Local container elements are marked  . The remaining elements in the workflow container are workflow system elements. For further information, please refer to Workflow System Elements in the Workflow Container.
    2.     Enter a text to describe the step.
    You can, of course, leave the description of the task that is proposed by the system.
    (The current step in your workflow definition appears here.)
    3.     Go to the Outcomes tab.
    All of the outcomes for this step are displayed here.
    4.     Enter a text for the description.
    The description (proposal: < Application filled out> ) in the Task executed synchronously line.
    Each step has at least one subsequent event (in this case: Task executed synchronously). The description is the text with which the outcome is labeled in the workflow definition.
    The Form does not exist and Form could not be generated outcomes are the possible exceptions that could occur in the method execution. You "run the risk" of not intercepting these exceptions and not modeling any exception handling in your workflow definition. If one of the exceptions actually occurs at runtime, the workflow will assume the error status.
    Checking the binding definition (optional)
    1.     Go to the Control tab.
    2.     Choose  Binding (present).
    The WF Builder: Binding for Step ‘<Create notification of absence>’ dialog box is then displayed.
    o     In the upper part of the screen, the binding defined from the workflow container to the task container is displayed. The system executes this binding before providing the task for execution.
    This binding direction is not relevant for this step since no information is to be transported from the workflow to the task.
    o     In the lower part of the screen, the binding defined from the task container to the workflow container is displayed. This system executes this binding after the user has processed the task.
    Here, the binding is WIObjectId.  &ABSENCEFORM& has been automatically defined here by the system. This binding ensures that the reference to the notification of absence created is not only known in the single-step task, but also in the workflow.
    You can view the contents of both containers by choosing Workflow container or Task container.
    (The element of the task container WIObject_ID is called Notif. of absence .)
    3.     Choose  .
    You then return to the step definition.
    Entering the agents responsible
    On the tab page Control, choose the entry Workflow initiator (expression) in the area agent as the agent responsible.
    The system enters the expression &_WF_INITIATOR& in the Expression field and in the input field beside the checkbox.
    You start your executable workflow later manually. At this point in time, the system fills the workflow container element WFInitiator automatically with your user name.
    The above assignment informs the workflow system that the first work item for creating the notification of absence should be addressed as the "starter" as the workflow.
    You return to the screen Workflow definition: Create step: Activity
    Concluding step definition
    1.     Choose  to check the step definition.
    2.     Choose  to exit the step definition.
    3.     Choose  to view the entire workflow definition in the workflow area on the screen.
    You will notice that your workflow definition now contains a new step (the activity just created). The undefined step is also still there.
    4.     Choose  .
    The workflow definition is checked, saved, and, provided it does not contain any errors, activated. The system displays a message if problems are encountered during the test.
    5.     Exit the Workflow Builder.
    Result
    You have now completed this unit and can start the next unit.
         Unit 3: Starting the Workflow Builder
    Use
    A workflow definition is created with the help of the Workflow Builder.
    Prerequisites
    You have now created a workflow template ( Unit 2: Creating a Workflow).
    Procedure
    Calling the Workflow Builder
    1.     Choose Tools &#61614; Business Workflow &#61614; Development &#61614; Definition Tools &#61614; Workflow Builder.
    The Workflow Builder is then launched with the workflow definition that was processed last. If the Workflow Builder has not yet been called, then an initial workflow definition is displayed.
    The Workflow Builder screen is divided into the following areas.
    The workflow definition is displayed in the Workflow area on the screen. If the workflow is shown in display mode, the step type area is not displayed. For further information, refer to Workflow Builder in the SAP Business Workflow documentation.
    2.     Choose  and enter the abbreviation of your workflow template (< WSeight digit number >) .
    You can use the F4 input help. Enter the start of the abbreviation for your workflow (for example: < ini*> ) and choose  All of the workflows that match are displayed. Select your workflow and choose  .
    Result
    The workflow definition is displayed and if necessary can be processed. If the Workflow Builder is called for the first processing of a newly created initial workflow definition, the following graphic is displayed:
    If the graphic displayed differs from that above, check the graphic settings in the Workflow Builder. Choose Extras &#61614; Options, and click the Graphic tab. Choose the Without event-driven process chains view.
    •     The start of the workflow definition is indicated by  Start Workflow. If the new workflow definition has been called from the definition of a multistep task for which triggering events are defined, these are represented by the symbol  and their description.
    •     The end of the workflow definition is indicated by  Workflow terminated.
    •     The area in which the new workflow definition can be added is indicated by an undefined step with an outcome. Steps are displayed in the form of symbols. The description of an outcome is illustrated in the standard view with an arrow.
    This unit is now complete. In the following unit you create the first step in your workflow and define a task for this purpose at the same time.
    Creating an Activity as a Step in the Workflow Definition
    Add a first step of the type Activity to the workflow definition.
    1.     Choose  under step type. The cursor changes shape.
    2.     Position the cursor on the Undefined step and click.
    By doing so, you add an activity to your workflow definition. The step definition is shown in the right-hand part of the screen. You are on the tab page Control.
    Entering basic data for control
    3.     Enter the abbreviation ( TS<8-digit number> ) of the standard task Create Notification of Absence in the Task field and choose  .
    If you no longer know the full abbreviation, you can use different methods to search for it:
    o     Use the F4 input help to search via the object type and method of the single-step task.
    This brings you to the Search and Find: Tasks dialog box.
    On the tab page Obj. type and method, enter the object type FORMABSENC and the method CREATE .
    Then double-click your single-step task in the list. You should recognize your single-step task from your initials in the abbreviation. Choose  .
    o     Enter a character string in the abbreviation or description and choose  .
    A list of tasks is then displayed in which you can double-click the desired task.
    Every activity, as a step in a workflow definition, refers to a task.
    At this point, the unique reference to this task is entered. The identification is made up of an abbreviation (T, TS, WF, or WS) followed by an 8-digit number.
    If you select a workflow task (WF) or workflow template (WS) as your task, your activity is a subworkflow. If you select a customer task (T) or standard task (TS), your activity is a single step.
    The Define Container Elements and Binding dialog box is then displayed in which the system proposes a change to the workflow container and a binding definition.
    o     Upper part of the dialog box: Proposal for new container elements in the workflow container.
    The system proposes that you create a local container element in the workflow container, which can store the reference to the notification of absence created in this step. The element has the technical name AbsenceForm .
    o     Lower part of dialog box: Proposed binding definition
    The system proposes that you define a binding from the task container to the workflow container. This binding transports the reference to the generated object (i.e. the created notification of absence) from the task (from the WIObject_ID element in the task container) to the workflow (to the AbsenceForm element in the workflow container).
    Further information on automatic binding definition proposals is available under Binding Definitions from the Workflow Container and Binding Definitions from the Task Container in the documentation on SAP Business Workflow.
    4.     Confirm the proposal with  .
    The new AbsenceForm container element is displayed in the object area of the workflow container folder. Local container elements are marked  . The remaining elements in the workflow container are workflow system variables. For further information, please refer to Workflow System Variables in the Workflow Container.
    5.     Enter a text to describe the step.
    You can, of course, leave the description of the single-step task that is proposed by the system.
    (The current step in your workflow definition appears here.)
    6.     Go to the Events tab.
    All of the outcomes for this step are displayed here.
    7.     Enter a text for the description.
    The description (proposal: < Application filled out> ) in the Task executed synchronously line.
    Each step has at least one subsequent event (in this case: Task executed synchronously). The description is the text with which the outcome is labeled in the workflow definition.
    The Form does not exist and Form could not be generated outcomes are the possible exceptions that could occur in the method execution. You "run the risk" of not intercepting these exceptions and not modeling any exception handling in your workflow definition. If one of the exceptions actually occurs at runtime, the workflow will assume the error status.
    Checking the binding definition (optional)
    1.     Go to the Control tab.
    2.     Choose  Binding (present).
    The WF Builder: Binding for Step ‘<Create notification of absence>’ dialog box is then displayed.
    o     In the upper part of the screen, the binding defined from the workflow container to the task container is displayed. The system executes this binding before providing the task for execution.
    This binding direction is not relevant for this step since no information is to be transported from the workflow to the task.
    o     In the lower part of the screen, the binding defined from the task container to the workflow container is displayed. This system executes this binding after the user has processed the task.
    Here, the binding is WIObjectId.  &ABSENCEFORM& has been automatically defined here by the system. This binding ensures that the reference to the notification of absence created is not only known in the single-step task, but also in the workflow.
    You can view the contents of both containers by choosing Workflow container or Task container.
    (The element of the task container WIObject_ID is called Notif. of absence .)
    3.     Choose  .
    You then return to the step definition.
    Entering the agents responsible
    Choose Workflow initiator (expression) under Agents.
    The system enters the expression &_WF_INITIATOR& in the Expression field and in the input field beside the checkbox.
    By doing so, you choose the agent responsible.
    You start your executable workflow later manually. At this point in time, the system fills the workflow container element WFInitiator automatically with your user name.
    The above assignment informs the workflow system that the first work item for creating the notification of absence should be addressed as the "starter" as the workflow.
    You return to the screen Workflow definition: Create step: Activity
    Concluding step definition
    1.     Choose  to check the step definition.
    2.     Choose  to exit the step definition.
    3.     Choose  to view the entire workflow definition in the workflow area on the screen.
    You will notice that your workflow definition now contains a new step (the activity just created). The undefined step is also still there.
    4.     Choose  .
    The workflow definition is checked, saved, and, provided it does not contain any errors, activated. The system displays a message if problems are encountered during the test.
    5.     Exit the Workflow Builder.
    Result
    You have now completed this unit and can start the next unit.
    Unit 5: First Test
    Use
    You are now going to start a workflow in dialog for the first time, which will run according to your workflow definition. This workflow definition only contains a step for creating a notification of absence so far.
    For further information on starting workflows, refer to Starting Workflows (Test Environment) in the SAP Business Workflow documentation.
    Prerequisites
    The creation of a notification of absence, which you carry out within your workflow, is reported on a system-wide basis by an event. Other workflows entered as event receivers for this event may therefore be started. The notification of absence created by you (and published by the event) is then also processed with these workflows.
    This event is not used in connection with this tutorial.
    To ensure that only you work exclusively with the notification of absence, you can deactivate any existing linkages between the event and its receivers. Proceed as follows:
    If you carry out the following steps, you prevent other workflows being started unintentionally by your notification of absence.
    However, you may interrupt other workflow demonstrations. Therefore, be careful and speak to the colleagues involved if necessary.
    1.     Choose Tools &#61614; Business Workflow &#61614; Development &#61614; Utilities &#61614; Events &#61614; Simulate Event.
    2.     Enter FORMABSENC in the Object type field.
    3.     Enter created in the Event field.
    4.     Choose  .
    The system simulates the event FORMABSENC.Created and establishes which workflows would be started.
    5.     If you find one or more entries in the list under the branch Tasks without syntax errors to be started, position the cursor on an entry and choose  Event linkage.
    The dialog box Event linkage: Triggering events is displayed.
    6.     Position the cursor on the entry with the red background for the event and choose  .
    The linkage between workflow and event is deactivated.
    7.     Choose  .
    8.     Repeat steps 5 to 7 or repeat the whole simulation as applicable.
    Procedure
    Starting the workflow and filling out the form
    1.     If you are still in the Workflow Builder, choose  .
    The Start Workflow (Test Environment) screen is then displayed. The number of your workflow template is entered.
    If you are no longer in the Workflow Builder, choose Tools &#61614; Business Workflow &#61614; Development &#61614; Runtime Tools &#61614; Start Workflow (Test Environment). Enter the identification of your workflow or use the F4 input help.
    2.     Choose  .
    To handle work processes more quickly, SAP Business Workflow supports Advancing with Immediate Dialog. When a workflow is started in dialog, this means that the first work item of the workflow is made available for processing immediately provided that the user who starts the workflow is also one of the recipients of this first work item. This is the case here because you entered the container element WFInitiator as the agent in the step definition.
    The Create notification of absence screen, therefore, is displayed immediately where you can see the notification of absence form. It is the method Create that is executed with the first work item.
    3.     Fill out the form with entries of your choice.
    4.     Choose  .
    The Start Workflow (Test Environment) screen is then displayed again.
    5.     Choose  and exit the Workflow Builder if necessary.
    Starting a workflow / Business Workplace
    Before you extend your workflow definition, carry out the following test. It will familiarize you with the Business Workplace.
    1.     Start your workflow in dialog again. Choose Tools &#61614; Business Workflow &#61614; Development &#61614; Runtime Tools &#61614; Start Workflow. (T.Code SWUI)
    You go to the screen Start task.
    2.     Choose your workflow in the table on the left.
    3.     Choose Start on the right-hand side of the screen.
    The notification of absence form is displayed.
    4.     Do not make any entries and do not save. Instead, choose  .
    You have now started the workflow but canceled the processing of its first step. But the processing of the work item is not yet completed. You have only broken the processing chain of advancing with immediate dialog.
    5.     Choose  .
    6.     Choose Tools &#61614; Business Workflow &#61614; Development &#61614; Runtime Tools &#61614; Business Workplace.
    7.     Open the Inbox node and choose the Workflow folder.
    Your workflow inbox now contains (at least) one work item for processing. This is the work item for creating a notification of absence, the processing of which you canceled previously.
    8.     Select the work item, if necessary, and choose  .
    You return to the Create notification of absence screen where the notification of absence form is displayed.
    9.     Fill out the form and choose  .
    The work item disappears from your workflow inbox.
    Result
    You have now completed this unit and can start the next unit.
         Reporting and analysis
           In this first test, you will take a look at the work item analysis function.
    1.     Choose Tools &#61614; Business Workflow &#61614; Development &#61614; Reporting &#61614; Work Item Analysis &#61614; Work Items Per Task
    The Work Items Per Task screen is then displayed.
    2.     Select the monitoring period Today.
    3.     Select the work item type (Sub-)Workflow only.
    4.     Choose  .
    The system then determines all of the workflows that were started today. These are then listed on the Work Items Per Task from <Date> to <Date> screen. The number of work items in each workflow is also shown here.
    Make sure that you only ever analyze the work items for your workflow and your absence notification.
    5.     Display the list of associated work items by double-clicking the workflow ID.
    Both the workflows you just started for this workflow identification are displayed with status Completed.
    6.     Display the workflow log by double-clicking a work item ID.
    The Workflow Log screen is then displayed.
    For information on the workflow log, see Workflow Log in the SAP Business Workflow documentation.
    7.     Exit the work item analysis function.
         Unit 6: Creating a Task "Check Notification of Absence"
    Use
    You define the task Check notification of absence. This task is incorporated into your workflow definition as the second step.
    As this is not the first task you have defined, many steps will doubtless be familiar to you. (Refer to Unit 4: Defining and Inserting Task "Create Notification of Absence.)
    Prerequisites
    The object type used (here: FORMABSENC (notification of absence)) and the required method (here: Approve) are already defined and implemented in the Business Object Repository.
    Procedure
    1.     Choose Tools &#61614; Business Workflow &#61614; Development &#61614;&#61472;Definition Tools &#61614; Tasks/Task Groups &#61614; Create.
    The screen Task: Maintain is displayed.
    2.     In the Task type field, choose the Standard task entry.
    3.     Choose  .
    The Basic data tab in the Standard task: Create screen is then displayed.
    Entering the basic data
    1.     Enter an abbreviation (of your choice) and a name (of your choice) for the task to be created.
    Abbreviation: < ini _check>
    Name: <Check notification of absence (ini)>
    Object type and method
    2.     Enter an object type and a method:
    Object type: FORMABSENC
    Method: APPROVE
    You can also use the F4 input help to select the method.
    Work item text
    3.     In the Work item text field, enter the text Check notification of absence from .
    4.     Choose  . Save your standard task as a local object.
    5.     You can include variables in your work item text to be filled with values from the task container at runtime..
    The name of the creator of the notification of absence is to be included into the work item text. As soon as the work item appears in the superior’s Business Workplace, the name of the creator appears in the work item information text.
    Position the cursor in the work item text after the word of .
    6.     Choose  .
    The Please choose an expression dialog box is then displayed.
    7.     Choose the expression Notif. of absence by double-clicking the Container node. &#61614; Issuer object ref. &#61614; Name.
    If WIObject_ID is displayed instead of Notif. of absence, choose  . The system then displays the description of the expressions instead of their technical names.
    The variable &_WI_Object_ID.Creator.Name& has been added to the work item text automatically. The variable name displayed here is the technical name of the expression.
    You can integrate all of the elements in the task container in your work item text. This enables you to include information into the work item text, which is not available until runtime.
    Entering the description text
    1.     Go to the Description tab.
    2.     Choose Task description in the Test type field.
    The current task description is then displayed. This text is intended to inform future recipients of a work item in which this task is referenced and help them in their work.
    The text will often be similar to the work item text or may supplement it.
    3.     Choose  .
    4.     Enter the following text:
    Please check notification of absence no. &_WI_OBJECT_ID.NUMBER& from &_WI_OBJECT_ID.CREATEDATE& of employee &_WI_OBJECT_ID.CREATOR.NAME& .
    Decide whether to approve the request.
    If you want to insert an expression from the task container as a text variable, choose Include &#61614; Expression. Then choose the relevant expression in the Please choose an expression dialog box by double-clicking the Container node.
    5.     Choose  .
    6.     Choose  .
    Determining possible agents
    1.     Select Additional data &#61614;&#61472;Agent assignment &#61614; Maintain
    This takes you to the Standard task: Maintain Agent Assignment screen.
    2.     Position the cursor on the name of your task.
    3.     Choose  .
    You go to the dialog box Choose agent type.
    4.     Double-click Job.
    The dialog box Choose Job is displayed.
    5.     Enter either part of or the full abbreviation of the job that you created for the head of department in Unit 1: Organizational Plan.
    You return to the screen Standard task: Maintain agent assignment.
    6.     Choose  .
    You have linked the task to the job of a head of department. In the organizational plan, you use this job to describe a position. The holder of the position is also displayed.
    7.     Choose  .
    8.     Choose  .
    Result
    The task for checking the notification of absence is defined in full. You can now exit the screen for defining a task.
    In the next unit, you will incorporate this task into the workflow definition.
    Display your organizational plan again.
    a.     Choose Tools &#61614; Business Workflow &#61614; Development &#61614; Definition Tools &#61614; Organizational Management &#61614; Organizational Plan &#61614; Display.
    b.     Choose your organizational unit in the search area. Display it by double-clicking the entry in the table.
    c.     In the overview screen, choose the arrow  on the right next to the  and then Staff assignments (list).
    d.     Display a detailed view of the position of the head of department by double-clicking the entry in the list.
    Here, you can see that this position is assigned to the job and, on the Tasks tab, that it is also assigned to the task Check notification of absence.
         Unit 7: Including "Check Notification of Absence" in the Workflow Definition
    Use
    The task with which an employee can check a notification of absence is ready to be included into your workflow definition as the next step.
    Prerequisites
    You have defined a workflow with a step ( Unit 4: Task Defining and Inserting "Create Notification of Absence") and created the task Check Notification of Absence ( Unit 6: Create Task "Notification of Absence").
    Procedure
    Calling the Workflow Builder
    1.     Choose Tools &#61614; SAP Business Workflow &#61614; Development &#61614; Definition Tools &#61614; Workflow Builder.
    The Workflow Builder is then launched in display mode with the workflow that was processed last.
    2.     Work through the following steps to display your workflow for this tutorial in change mode.
    i.     If the workflow you created for this tutorial is already displayed, choose  . Go to step 3.
    ii.     If a different workflow is displayed, check whether the workflow you created is listed in the My available tasks area. Double-click it and choose  . Go to step 3.
    iii.     Choose  . Enter the complete abbreviation in the Task field on the Open other workflow definition dialog box and press RETURN. You can now also enter the workflow abbreviation. Enter either the full abbreviation or just the first characters (for example: < i*> ). Press F4 . The search result is then displayed. Choose your workflow by double-clicking it. When you enter the abbreviation in the Task field on the Open other workflow definition dialog box, all of the available versions are displayed. Since you have not created any versions, select version 0000 and choose  . The workflow is then loaded in display mode. To switch to change mode, choose  .
    1.     Choose  to display the entire workflow in the workflow area on the screen.
    Creating a container element in the workflow container
    You need an additional container element in the workflow container to store the name of the user who will execute this step. This user name is to be used later in the notification text that is sent to the requester.
    1.     Choose the entry <Double-click to create> by double-clicking in the Workflow Container.
    The dialog box for entering a container element is displayed.
    2.     Make the following entries:
    Element: Approver
    Name: Approver
    Description: Approver of the absence request
    Reference table: WFSYST
    Reference field: AGENT
    3.     Choose  .
    You have now added a local container element to the workflow container, which is ready to take an agent name, based on its data type reference. However, you have not yet determined a value for this container element.
    Creating an Activity as a Step in the Workflow Definition
    1.     Choose  under step type. The cursor changes shape.
    2.     Position the cursor on the Undefined step that follows the outcome Request completed and click.
    By doing so, you add an activity to your workflow definition. The step definition is shown in the right-hand part of the screen. You are on the tab page Control.
    Entering basic data for control
    3.     In the Task field, enter the abbreviation ( TS<8-digit number> ) of the task Check Notification of Absence that you defined in the previous unit. Choose  .
    If you no longer know the full abbreviation, you can use different methods to search for it:
    o     Use the F4 input help to search via the object type and method of the task.
    This brings you to the Search and Find: Tasks dialog box.
    On the tab page Obj. type and method, enter the object type FORMABSENC and the method CREATE .
    Then double-click your task in the list. You should recognize your task from your initials in the abbreviation. Choose  .
    o     Enter a character string in the abbreviation or description and choose  .
    A list of tasks is then displayed in which you can double-click the desired task.
    Every activity, as a step in a workflow definition, refers to a task.
    At this point, the unique reference to this task is entered. The identification is made up of an abbreviation (T, TS, WF, or WS) followed by an 8-digit number.
    If you select a workflow (WS or WS) as your task, your activity is a subworkflow. If you select a task (TS or T), your activity is a single step.
    You go to a dialog box in which the system proposes binding from the workflow container to the task container.
    Here, the object reference to the notification of absence is transported from the workflow container (container element AbsenceForm ) to the task container (to the container element WIObject_ID ).
    1.     Choose  to confirm the proposal.
    Extending the binding definition
    Now define another binding via which the current agent of the work item (the superior) is stored in a container element of the workflow container.
    2.     Choose  Binding (present).
    The Binding for Step 'Check notification of absence' dialog box is then displayed. If the first column is entitled Element, choose  to display the element description.
    The system has created the following binding definition from the workflow container to the task container:
    Notif. of absence  &AbsenceForm&
    This binding ensures that the correct notification of absence is checked in the task.
    3.     Choose  .
    All of the container elements in the task container are now displayed on the left-hand side. You can define a binding from these container elements to the workflow container.
    4.     Position the cursor in the lower half of the screen, in the empty input field beside the container element Actual agent and call the F4 input help.
    5.     Double-click Approver.
    In addition to the bindings already existing, the following binding is now defined:
    Actual Agent  &Approver&
    6.     Choose  .
    Determining outcomes
    The method APPROVE of the object type FORMABSENC, to which you refer in the standard task definition, is defined with a result. The three possible values of this result are offered on the tab page Outcomes as outcomes of this step:
    •     Approved
    •     rejected
    •     New
    The  indicates that these outcomes have already been transferred to the workflow definition. The outcome New is not really appropriate at this point. At this stage of processing, the notification of absence cannot be "new" any more. It should therefore not be incorporated in the definition.
    1.     Click on the symbol  in front of the outcome New.
    The symbol changes to  .
    The outcome Processing obsolete is processed if the relevant work item is set to obsolete via a process control step. This functionality is not used in this tutorial.
    The outcome Form not available results from the exception defined for the method APPROVE. You could include this outcome into the workflow definition and would then have to model appropriate subsequent steps. However, you do not model anything for the purposes of this tutorial and accept that your workflow will have an error at runtime if this exception is raised.
    2.     Choose  .
    Two branches are now inserted in your workflow definition for the two marked outcomes Approved and Rejected.
    Inputs for the agent
    If you are working through this tutorial alone, do not specify anything for responsibility at this point. If it is processed when the workflow is executed, therefore, this step will be "offered" for processing to all employees declared as possible agents of the single-step task Check notification of absence. This means all user whose positions are described with the job head of department.
    In your organizational plan, there is only one users who is a possible agent -> you.
    •     You have maintained the organizational plan with jobs, positions, and user assignments in Unit 1: Organizational Plan.
    •     You have defined the single-step task "Check notification of absence" and have assigned the possible agents in Unit 6: Definition of the Standard Task "Check Notification of Absence".
    Concluding step definition
    Choose  .
    The workflow definition is checked, saved, and, provided it does not contain any errors, activated. The system displays a message if problems are encountered during the test.
    Result
    You can subject your workflow definition to a second test.
      Unit 8: Second Test 
    Use
    You start your workflow in dialog and two steps are executed. The notification of absence is created in the first step and then checked in the second.
    Procedure
    Starting the workflow and filling out the form
    1.     If you are still in the Workflow Builder, choose  .
    The Start Workflow (Test Environment) screen is then displayed. The number of your workflow is entered.
    If you are no longer in the Workflow Builder, choose Tools &#61614; Business Workflow &#61614; Development &#61614; Runtime Tools &#61614; Start Workflow (Test Environment). Enter the number of your workflow or use the F4 input help.
    2.     Choose  .
    You go to the screen Create Notification of Absence.
    From the requester’s perspective
    When the workflow is started, the work item for creating the notification of absence is provided to you directly for processing. This is because of advancing with immediate dialog. You were introduced to this in the first test.
    3.     Fill out the form and choose  .
    From the head of department's perspective
    You created the step for checking the notification of absence in your workflow definition without specifying the agents responsible. This means that all of the possible agents of the single-step task are recipients of the work item. Since you occupy the position of both requester and head of department, you are automatically and immediately presented with the work item for approving the application. This is again because of advancing with immediate dialog.
    As the superior, you have several options:
    •     Approve the request
    •     Reject the request
    •     Cancel processing of the request.
    4.     Choose  to cancel processing.
    The Start Workflow (Test Environment) screen is then displayed again.
    Exit this dialog and, if necessary, the Workflow Builder.
    Reporting and analysis: Workflow outbox
    In the first test of your workflow, you were introduced at this point to work item analysis. Now, you will be introduced to the workflow outbox.
    Amongst other things, the work items which you started in dialog along with date, time and current status are displayed in the workflow outbox.
    1.     Choose Tools &#61614; Business Workflow &#61614; Development &#61614; Runtime Tools &#61614; Business Workplace.
    2.     In the tree displayed, choose Outbox &#61614; Started workflows.
    3.     Choose the arrow  on the right next to the  and then Today only.
    The work items for all the workflows you started today are then displayed. Note the statuses of the work items displayed in the Status column of the Business Workplace. Read the F1 help for the Status column.
    4.     Position the cursor on the work item for the workflow just started. This work item has the status in process.
    From the current workflow data, you can see that the step Create notification of absence has been completed successfully, when that was, and who processed it. The work item has the status completed.
    You can also see that the work item representing the task for checking the request still has status ready and can therefore still be seen in the superior’s Business Workplace.
    Business Workplace - check notification of absence
    You now once again occupy the position of the superior who canceled processing earlier when the application was to be checked.
    5.     In the tree, choose Inbox &#61614; Workflow.
    The work items for you to process are displayed with their work item texts and certain other attributes.
    A preview of the selected work item is displayed below the list and contains the description of the work item.
    6.     Select the work item for checking the notification of absence and choose  .
    You go to the work item display. There you find amongst other things the description text, also with replaced text variables.
    7.     Choose  to return to the Business Workplace.
    8.     Choose  or start execution by double-clicking the entry.
    9.     Either reject or approve the request. You should start the workflow twice and test each variant.
    To check whether the workflow was completed correctly, go to your workflow outbox. The procedure is described above.
    Result
    Your workflow definition has now been tested and you can continue with the next unit.
      Unit 9: Adding a User Decision 
    Use
    In the previous units, you created a workflow whose definition contains two activities. These activities are based on two standard tasks that you created.
    In this unit, you will add a user decision to your workflow definition.
    With the user decision, the requester can decide to revise and resubmit the notification of absence if the head of department rejects it.
    For further information, refer to Maintaining a User Decision in the SAP Business Workflow documentation.
    Procedure
    You start the Workflow Builder and open your workflow definition in Change mode. Proceed as described in Unit 7: Including "Check Notification of Absence" in the Workflow Definition.
    Creating a user decision as a step in the workflow definition
    1.     Choose  under step type. The cursor changes shape.
    2.     Position the cursor on the Undefined step that follows the outcome Rejected and click.
    By doing so, you add a user decision to your workflow definition. The step definition is shown in the right-hand part of the screen. The Decision tab is displayed.
    Entering basic data for user decision
    3.     Enter Your request was rejected by &. Revise? in the Title field.
    This text is used as the title for the alternative decisions when the workflow is executed. The variable & is a placeholder for a parameter that is filled from the task container at runtime.
    4.     Choose the F4 input help in the Parameter 1 field.
    The Expression for first parameter of user decision dialog box is then displayed.
    5.     Choose the Approver container element by double-clicking it.
    Entering alternative decisions
    6.     Define the alternative decisions. Enter the following texts:
    Decision texts     Name
    Decision: Revise request?     Revise
    Decision: Withdraw request?     Withdraw
    7.     The decision texts you enter here appear as decision options on the screen that can be processed by the requester after their leave request has been rejected.
    8.     The descriptions are the terms used to describe the outcomes in the workflow definition.
    9.     Entering the agents responsible
    10.     Choose Workflow initiator (expression) under Agents.
    The system enters the expression &_WF_INITIATOR& in the Expression field and in the input field beside the checkbox.
    Concluding step definition
    1.     Choose  to check the step definition.
    2.     Choose  to exit the step definition.
    3.     Choose  to view the entire workflow definition in the workflow area on the screen.
    You can see that your workflow definition contains a user decision in the rejected branch. This has two outcomes whose branches converge again in the rejected branch. Each new branch contains an undefined step.
    4.     Choose  .
    The workflow definition is checked, saved, and, provided it does not contain any errors, activated. The system displays a message if problems are encountered during the test.
    Result
    You can now subject your workflow definition to another test.
      Unit 10: 3rd Test 
    Use
    You start your workflow in dialog and three steps are executed: Two activities, for creating and checking a notification of absence, and one user decision.
    Procedure
    Starting the workflow and filling out the form, checking the notification of absence, user decision
    1.     If you are still in the Workflow Builder, choose  .
    The Start Workflow (Test Environment) screen is then displayed. The number of your workflow is entered.
    If you are no longer in the Workflow Builder, choose Tools &#61614; SAP Business Workflow &#61614; Development &#61614; Runtime tools &#61614; Start workflow (test environment). Enter the number of your workflow or use the F4 input help.
    2.     Choose  .
    You go to the screen Create Notification of Absence.
    From the requester’s perspective
    3.     Fill out the form and choose  .
    When you save the form, you (as superior) can immediately approve or reject the application (reason: advancing with immediate dialog).
    From the superior’s perspective
    4.     Do not approve the application.
    5.     Choose  .
    If the request is not approved, the next step in the workflow definition is the user decision. The requester was entered as the agent for the step. The decision is therefore offered to you again as the requester (reason: advancing with immediate dialog).
    From the requester’s perspective
    You are given three options:
    •     Revise request?
    •     Withdraw request?
    •     Cancel
    It is irrelevant which option you choose since you have not defined any follow-up steps. You should start the workflow several times and try out the different options. The complete process flow can be checked each time in the work item analysis or workflow outbox.
      Unit 11: Define and Include "Revise Notification of Absence" in the Workflow Definition 
    Use
    You will now add the activity Revise notification of absence to your workflow definition. You will create the necessary task within the

Maybe you are looking for

  • Camera Roll Trouble

    OK, so when I go to the photos app on my iPhone 3GS, and I tap Camera Roll, only about half of my pictures show up. The rest are simply black thumbnails. However, when I tap on one, the picture shows up full screen. This is really annoying, and I wou

  • LabVIEW example problem

    i have install labview 7.1 development software with driver , on windows xp i am not able to open example . it shows following errors "CAN NOT FIND LabVIEW SERVICE PORT FROM SERVICE LOCATER YOU WILL BOT BE ABLE TO BROWS DIRECTRY STRUCTRY" while when

  • Dreamweaver Help | Packaging web applications as native mobile applications with PhoneGap Build

    This question was posted in response to the following article: http://helpx.adobe.com/dreamweaver/using/packaging-web-apps.html

  • "Sorry we could not reach the Netflix Service. Please try again...  (112)"

    Twice this week I have watched a several episodes of a TV show on Netflix through my Apple TV and then try to go to the next episode but get the a message that says: SORRY WE ARE UNABLE TO CONNCT TO THE NETFLIX SERVICE. PLEASE TRY AGAIN LATER. IF THE

  • Can't create remittance bank

    Hi when i've trying to create remittance bank, i've got a problem in the field unearned discounts, i got the message "FRM-40212 Invalid value for field UNEARNED_DISK_ACTIVITY". can i have a solution plz, thanks lot