VC Transport WS References

Hi guys, I would like to ask how the transported VC models work when I transport them to a QA system using NWDI, the thing is that I have several WebServices in my models that I get from the service registry, every WS that I call in my VC are called from an SAP ABAP, SAP JAVA or third party system registered as physical and business system in my SLD /  Service Registry.
So, the question is, do the VC models take into account the Service Registry references in each environment where the model is moved ¡? Do I need to modify the model everytime I move it from one environment to another !? what is the best way to take care about the lifecycle of my models !?
Any help will be appreciated !
Thanks !

Hi Shaily,
7.01 SP 2 is having some additional features than 7.0 SP15 and these features not supported in Vc 7.0. So problem may come from this. Check it or upgrade your QA system to 7.01 SP 2.
Regards
Basheer

Similar Messages

  • Transportation Cost setting in SO, How?

    Hello All,
    Can somebody help me please? i want to set a transportation cost in my sales order but i have no idea how to set it up? can you help me please? please advise and let me know if there are configurations needed.
    Thank you.
    Regards,
    Lee T

    Hi,
    you need a transportation zone hierarchy to model transportation zones. In the transportation zone hierarchy, you assign several locations, for example customers, to a transportation zone.
    Using transportation zones has the advantage that you can reduce the number of transportation lanes that need to be processed.
    For each transportation zone, you have to create the following two transportation lanes:
    ●     A transportation lane between the source location and the transportation zone (reference transportation lane)
    ●     A transportation lane for transportation zone to itself, that is, you enter the same transportation zone as both the source and destination location (intrazone lane)
    The optimizer creates all of the other transportation lanes during the optimization run (runtime lanes):
    ●     All of the transportation lanes between the source location and every customer within the transportation zone (based on the reference transportation lane)
    ●     All of the transportation lanes between the individual customers within the transportation zone (based on the intrazone lane)
    Below document will give yoru clear idea,
    http://www.sap-press.de/download/dateien/1793/sappress_capable_to_match_with_sap.pdf
    Regards
    Nagaraju

  • Transport Protocol in NI-XNET

    Has anyone used the J1939 Transport protocol with NI-XNET in LabWindows?  Is there anything built in to XNET or do you just have to handle timing, acks, and message sequencing manually with the Raw Frame format?
    Anyone know of any LabWindows examples out there?  The only examples I see are in LabVIEW.  LabWindows support seems to pale in comparison...which is fun.

    Hi BLowery
    I looked through our internal servers and was not able to find any examples for J1939 for LabWindows CVI. As you mention, you can still use the XNET functions to build up your code from there. If you have the chance to open the VIs see the code in the J1939 Transport Protocol Reference Example, this could be a good start point for building up your code on CVI. 
    Hopefully, if someone has worked in this before, the might be able to provide suggestions or share their resources with you in this forum.
    WenR

  • Custom Transport Protocol in OSB

    Hi,
    How custom transport protocol can be created in OSB? can any one guide me on this?
    Regards,
    Amik

    Hi BLowery
    I looked through our internal servers and was not able to find any examples for J1939 for LabWindows CVI. As you mention, you can still use the XNET functions to build up your code from there. If you have the chance to open the VIs see the code in the J1939 Transport Protocol Reference Example, this could be a good start point for building up your code on CVI. 
    Hopefully, if someone has worked in this before, the might be able to provide suggestions or share their resources with you in this forum.
    WenR

  • Transport SAP HANA/BWA Index to Target

    Dear Experts,
    I have created SAP HANA/BWA index using t-code RSDDB in DEV system using BEx query. now i want to transport the BWA index to TEST system, but I don't know how?
    Already I have transported the BEx query to TEST system.
    Please help me to how we will transport the SAP HANA/BWA index to TEST system.
    Thanks,
    Regards,
    Karuppiah N

    Hi Karuppiah,
    I am not sure it is possible to transport BWA Index
    Analytic Indexes are not integrated in the BW repository and therefore cannot be transported.
    "Analytic indexes can be created and filled with (transformed) data quickly. They are intended for ad-hoc scenarios. They can also be created as InfoProviders without reference to InfoObjects. They are therefore not integrated into the metadata repository and cannot be transported. "
    Reference: http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/209f3aec-09d9-3110-339c-c127409aee06?QuickLink=index&…
    Regards,
    V Srinivasan

  • Transport request moved with error

    HI all
    We have transported base objects(Infoareas,application components,infoobject catalogs,infoobjects) all  in single request for both MM mdoule which got moved with lot of errors.Some of them are
    InfoObject 0COMPETITOR, version M being deleted, (basic char.   not found)
    InfoObject 0COMPONENT, version M being deleted, (basic char.   not found)
    InfoObject 0DEL_INDIC, version M being deleted, (basic char.   not found)
    InfoObject 0INT_CUST, version M being deleted, (basic char.   not found)
    InfoObject 0MPN_MATNR, version M being deleted, (basic char.   not found)
    InfoObject 0RT_CUSTPL, version M being deleted, (basic char.   not found)
    InfoObject 0WS_ERNAM, version M being deleted, (basic char.   not found)
    InfoObject 0WS_UMNAM, version M being deleted, (basic char.   not found)
    InfoObject 0WS_UMNAMP, version M being deleted, (basic char.   not found)
    Attribute 0WS_ERNAM from characteristic 0AGREEMENT not (actively) available
    Attribute 0CND_GRANT from characteristic 0AGREEMENT not (actively) available
    Attribute 0WS_UMNAM from characteristic 0AGREEMENT not (actively) available
    Attribute 0WS_UMNAMP from characteristic 0AGREEMENT not (actively) available
    Attribute 0CUSTOMER from characteristic 0AGREEMENT not (actively) available
    Attribute 0CUSTOMER from characteristic 0APO_LOCNO not (actively) available
    Attribute 0CUSTOMER from characteristic 0APO_LOCNO not (actively) available
    Key figure 0APO_LOCPRI: Aggregation reference char.0APO_LOCPRI is not (actively) available
    Key figure 0APO_MATDUR: Aggregation reference char.0APO_MATDUR is not (actively) available
    Reslut is on BI Production we found that some of the infoobjects are inactive.
    Please let me know how to solve this
    Thanks,
    Harika.

    Hi,
    You're facing three different kinds of errors
    1. InfoObject 0COMPETITOR, version M being deleted
    It appears that the InfoObjects you've transported have reference characteristics. For example, 0COMPETITOR has a reference characteristic 0CUSTOMER, 0COMPONENT has a reference char 0MATERIAL and so on. Please check if the reference characteristics (0MATERIAL, 0CUSTOMER etc) are already present in the target system. If not, you'll have to go to Development, include the reference characteristics in a request and re-transport.
    2. Attribute 0WS_ERNAM from characteristic 0AGREEMENT not (actively) available
    This is happening because the attribute InfoObject (example: 0WS_ERNAM) is not active in the target system. This object might not be active because it's reference characteristic (see point 1).
    3. Key figure 0APO_LOCPRI: Aggregation reference char.0APO_LOCPRI is not (actively) available
    The Key Figure (0APO_LOCPRI) has an exception aggregation defiend on a characteristic (0APO_LOCNO). This characteristic is not active in the target system. You'll need to re-transport the Key Figures along with the referene characteristic.
    Solution is: find out the reference characteristics of all the characteristics for which you are facing a problem. Collect the characteristics and their reference chars together in a TR in development and retransport.  Likewise, for all the KFs where you're facing an error, find out their reference chars and collect them together and retransport.
    Regards,
    Suhas

  • Error : While Importing the Objects in Quality

    Dear all,
           I'm facing some error while transporting the Objects to quality server. The error's like
    Start of the after-import method RS_ISFS_AFTER_IMPORT for object type(s) ISFS (Activation Mode)
    Source system RD1100LS does not exist
    Source system RD1100LS does not exist
    Source system RD1100LS does not exist
    Source system RD1110LS does not exist
    Start of the after-import method RS_ISTS_AFTER_IMPORT for object type(s) ISTS (Activation Mode)
    There is no DataSource with these attributes
    There is no DataSource with these attributes
    There is no DataSource with these attributes
    There is no DataSource with these attributes
    There is no DataSource with these attributes
    There is no DataSource with these attributes
        Anyone suggest me how to solve this error..,
    Thanx in Advance..
    Regards,
    Saran

    Hi saran,
    Check the source system connectivity of the Quality system. Also check whether you have transported the datasources related to those objects that you transported from DEV to QAS.
    First you need to transport the Datasources created in R/3 and then replicate them in QAS/Prod and then transport the objects in BW from DEV to QAS/Prod.
    Check all these things and if still the problem persists... Refer to the below threads which may help u...
    Transport Problem - Reference to Transfer Structure not available
    No Source system exist
    Assign points if this helps u...
    Regards,
    KK.

  • 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  SAP Business Workflow  Development Definition tools  Organizational Management  Organizational plan  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

  • Which clients for certain functionalities

    Hi all,
    I'm configuring SAP ERP 6.0 SR2 after installing. I use 2 physical servers, one for DEV+QAS, one for PRD.
    My 2 SAP systems contain ABAP+Java with all software units installed.
    In my DEV+QAS system, I don't know whether or not I should use client 001. As DEV role, it should have 1 client for GOLD, 1 for Sandbox, 1 for Unit-Test; and as QAS role, it should have 1 client for Integration-Test.
      - Should I use client 001 as any client above or I use client 000 as source client of copying?
      - Because client 001 is the client for J2EE portal, should I use it as portal or change the portal client to another client? I don't know how to make another client as a QAS portal client (I'm not sure it's right or wrong, may be wrong). Or we're ONLY able to use 1 client for J2EE portal? If yes (1 portal client only), do I have to configure portal manually in the PRD system's portal also without any transport?
      - If possible, someone please let me know your current System Landscape with Transport for reference.
    Thanks,
    Toan Do

    Toan,
    Use 000 as the default client when setting up the first new client in the DEV system. Subsequent new clients can and should be created from the new customizing client you create by copying 000.
    You will want at least one master customizing client (which you call 'gold') and one integration test client in QAS. On whether you need to create the remaining clients that you mentions depends on your organization (for larger organizations your answer is probably a yes).
    Hope that helps.
    J. Haynes
    Denver

  • Difference Between VL31N and MIGO

    Hi All,
    Whats the differnce between VL31N and MIGO as both of them does the same work as Receiving Goods.
    Regards,
    Ramaswamy

    Hi
    STEP-1
    ME21N -Create Purchase Order
    ME22N-Change Purchase Order
    STEP-2
    ME29N-Release Purchase Order
    STEP-3
    VL31N-Create Inbound Delivery
    STEP-4
    VT01N -Create Shipment for transportation -with reference to Inbound delivery number (Inbound Shipment)
    VI01N-Create Shipment Cost -for Transportation with reference to shipment number.
    STEP-5
    MIGO- Goods Receipt -Inbound delivery -Mov Type - 101.
    Thanks & Rgds
    Rajesh

  • Transporting 0material_attr gives reference source system error...

    Hi Experts,
    I know its not recommended but for some reasons we were trying to move 0material_attr data source and transfer rules and transfer structure 0material_attr_ba from quality system (QAS) to Development system. And every time we are getting the error "Source system QAS does not exist" while importing the request in DEV.
    The reason for this error is that it is still keeping the reference source system of quality as QAS which is not there as logical system in DEV. My question is isn't it should automatically refer to R/3 DEV when imported to development system.
    Thanks
    Vishal

    Hi,
    As pointed out by Joke in the previous post, you need to maintain the mapping of logical system name for transportation.
    In Dev,  go to RSA1> Tools--> Conversion of logical system names.
    Here create new entries.
    Your Original Source System would be the QAS Logical System Name & Target Source System would be DEV Logical System Name.
    Once entry is saved, re-import the transport request and check.
    Hope this helps!

  • Is it possible to transport Reference Operation Sets?

    Hallo,
    I want to transport Reference Operation Sets from the productive to the consolidation system. Later on I want to transport the Sets back to the productive system.
    Is this possible with a transport request or is their any other possibility?
    Thx in advance!

    Markus Meier ,
    To my knowledge there was a 3rd party tool named Infoshuttle which is add-on to SAP, if you have that in your system then it is possible to transfer transaction data from Production to Non-Production system. It can also transfer from Non-Production system to production system though this is NOT recommended at all as it could create data inconsistency.
    [Information on Infoshuttle|http://www.erpgenie.com/products/infoshuttle.htm]
    Hope this helps....
    Regards,
    Prasobh

  • How works transport request management tool? (Version / Reference)

    Hi,
    I would like to understand how is working the transport management tool.
    When you save an object in a transport request, what do we save exactly ?
         Is it just a reference to the object to lock it
         Or it is a specific instance/version of the object ?
    This question because I'd like to understand if it is possible to update an object in an older version in the next system.
    For example, I transport an Infocube v1 with TR1. Then I update this infocube and save the change in a TR2. I transport TR2 to my next system and I am getting here my V2 Infocube.
    Then, let's imagine that the TR1 is transported again by mistake. What will happen ? Will I get my infocube in version 1 in the next system ? Or will I keep the version 2 as it was just a reference saved in theTR ?
    Thanks,
    Nico.

    Hi Nicolas,
    Let me demonstrate  with example.
    Let's say there an InfoCube A v1 with 10 Infoobjects in Development system.
    Now we capture this in TR1and then we release the TP. So TR1 now contains the image of Infocube A v1 with 10 infoobjects .
    Then lets say we make some changes such that the Cube A v2 now have 20 infoobjects and capture it in TR2. After releasing TR2 ,it will contain 20 infobjects .
    So now when we move TR2 to next system(Production system lets say ) , the Infocube A v2 with 20 infoobjects will move and will be present in the Production system.
    And again if by mistake we move TR1 , then infocube A v1 with 10 infoobjects will move to Production system (next system).
    So in short the Transport stores the properties of the changes done to the BW object in tabular format and when we move a TR that corresponding tabular image gets replaced in the new system and the BW object gets modified accordingly .
    Hope I am able to explain the situation you are facing .

  • Error while creating part 1 in J1iex ( with reference to stock transport or

    Dear All
                  I have the scenario  stock transport order inter plants with excise invoice plant A create the sto order and sent that to plant B. and plant B against this order it has done Delivery and excise invoice also created in plant B now material also supplied to plant A now stock in intransit in plant A. they want to take Part1 based on the sto number at the time the error is throughing "maintain the vendor for the customer A attached to supplying plant A."
    Please help any one on this.
    Regards
    Kumar

    Hi Anand,
    Check whether you have created Masters for the Supplying & Vendor Plants.
    If you have already created your supplying Plant as a Vendor using the Plant refernce.
    Then maintain your Receiving Plant Customer Master no: in your Supplying Plant Vendor master
    control data - Customer Field.
    Also check your Customer master Receiving Plant Control Data whether your Supplying Plant Vendor no: is there after you have made the above assignment.
    Hope it wil solve your Problem.
    Regards,

  • Create Delivery with reference to seasonal stock transport order

    Hello Gurus
    How do we create a delivery with respect to seasonal stock transport order, in R/3 4.7.
    Thanks in advance

    Any answers/suggestion please

Maybe you are looking for

  • How can I achieve following results with a query

    Hello everyone, I have some data like the following sample and I need to convert it or kind of pivot it No.      P_1     P_2    P_3 1        1       1       5 1        2       3       1 I want above data to look like the following result set: P_type 

  • Collect Message without correlation

    Hi, I have a scenario. I have to collect 10 files which has like 100 bytes of information in each file and they should be collected into a single file every five minutes. I dont know whats inside the file. The data may vary...How  do I collect these

  • Is there any possibilities that the ipad screen get enlarged?

    Hello, For starter, I would like to say that I don't own a tablet yet. Now for the real question, with the new technologies everyday and with all the competition between the companies, is apple going to enlarge the size of the ipad screen or do they

  • Buying music while being abroad

    Hello, I live in Canada, but am working in a country which does not have an iTunes Music Store. Can I still buy music from the Canadian iTunes Music Store? My credit card is Canadian (but had to change my billing address to here). Thanks! Paul

  • Weblogic Timer Event Generator - How it works?

    Hello everyone! I have wrote simple wli-application, that subscribes to the message broker channel. I have deployed it to the cluster (managed servers 1 (ms1) and 2(ms2)). (I use Weblogic Server 10.3, cluster contains 1 admin server and 2 managed ser