WORK FLOW Structures
Hi, I'm authorization manager and I need to control the access to the work flow structures, we have several structure to different purposes like purshing, projects, human resources and financials, however, with PPOMW transaction you can modify all the structures, is there any solution in order to control the users to their own structure?
Hello Kumar,
For Downloading Organization structure use CRM Transaction code CRMC_R3_ORG_GENERATE.
You can manullay select here the required R/3 Sales Organization, Sales Office & Sales Group structure.
Then generate those selected structure from R/3 to CRM System.
You can use Transaction code PFAL in R/3 to download employees from R/3 to CRM.
You can select the required data by choosing in Object ID field.
Regards,
Rajendra Sonawane
Similar Messages
-
Hi All,
Plz. explain the Data/Work Flow in SAP
Is there any difference between this if so explain,
and kindly tell me the process.
thank you,
NarenderHii..
Work Flow- SAP Business Workflow
Purpose
SAP Business Workflow can be used to define business processes that are not yet mapped in the R/3 System. These may be simple release or approval procedures, or more complex business processes such as creating a material master and the associated coordination of the departments involved. SAP Business Workflow is particularly suitable for situations in which work processes have to be run through repeatedly, or situations in which the business process requires the involvement of a large number of agents in a specific sequence.
You can also use SAP Business Workflow to respond to errors and exceptions in other, existing business processes. You can start a workflow when predefined events occur, for example an event can be triggered if particular errors are found during an automatic check.
SAP provides several workflows that map predefined business processes. These workflows do not require much implementation. For an overview of these SAP workflows, refer to Workflow Scenarios in Applications.
Integration
SAP Business Workflow uses the existing transactions and functions of the R/3 System and does not change the functions. You can combine the existing functions of the R/3 System to form new business processes with SAP Business Workflow. The workflow system takes over control of the business processes. If you are already using SAP Organizational Management, you can use the organizational structure created there to have the relevant agents carry out the individual activities. It is possible to have an activity carried out by a position. This ensures that the respective occupiers of the position can carry out the individual activities during execution of the workflow. This means that personnel changes in your organization are taken into account immediately in the execution of a workflow.
Features
SAP Business Workflow provides a number of tools for defining and analyzing workflows as well as for monitoring operation.
The Workflow Builder is for displaying and making changes to workflows. You can make small extensions directly to the original workflows supplied by SAP, such as carrying out your own agent assignments or changing deadline monitoring.
There are several Workflow Wizards to support you in the definition of workflows, with which you can create specific parts of a workflow. The Workflow Wizard Explorer gives you an overview of the existing Workflow Wizards.
In order to make the functions of the R/3 Systems available to a workflow, you use business objects, which you can define and analyze in the Business Object Builder. These business objects are made available to the workflow in reusable tasks. The Business Wizard Explorer gives you an overview of all existing tasks.
The end user receives information about the activities they are to carry out in their Business Workplace. This provides them with a central overview of all the activities that they are authorized to carry out. They can commence the activities from here.
Several tools are available to the workflow system administrator, with which they can control and analyze the current workflows. The workflow system administrator is notified of problems automatically by the system.
DATAFLOW-Data flow means flow of data from one module to another within a sap system.
Regards,
Aakash -
How can we use TABLE CONTROL in BDC and WORK FLOW of ABAP.
how can we use TABLE CONTROL in BDC and WORK FLOW of ABAP.?
please explain the important questions.How to deal with table control / step loop in BDC
Steploop and table contol is inevitable in certain transactions. When we run BDC for such transactions, we will face the situation: how many visible lines of steploop/tablecontrol are on the screen? Although we can always find certain method to deal with it, such as function code 'NP', 'POPO', considering some extreme situation: there is only one line visible one the screen, our BDC program should display an error message. (See transaction 'ME21', we you resize your screen to let only one row visible, you can not enter mutiple lines on this screen even you use 'NP')
Now with the help of Poonam on sapfans.com developement forum, I find a method with which we can determine the number of visible lines on Transaction Screen from our Calling BDC program. Maybe it is useless to you, but I think it will give your some idea.
Demo ABAP code has two purposes:
1. how to determine number of visible lines and how to calculte page number;
(the 'calpage' routine has been modify to meet general purpose usage)
2. using field symbol in BDC program, please pay special attention to the difference in Static ASSIGN and Dynamic ASSIGN.
Now I begin to describe the step to implement my method:
(I use transaction 'ME21', screen 121 for sample,
the method using is Call Transation Using..)
Step1: go to screen painter to display the screen 121, then we can count the fixed line on this screen, there is 7 lines above the steploop and 2 lines below the steploop, so there are total 9 fixed lines on this screen. This means except these 9 lines, all the other line is for step loop. Then have a look at steploop itselp, one entry of it will occupy two lines.
(Be careful, for table control, the head and the bottom scroll bar will possess another two fixed lines, and there is a maximum number for table line)
Now we have : FixedLine = 9
LoopLine = 2(for table control, LoopLine is always equal to 1)
Step2: go to transaction itself(ME21) to see how it roll page, in ME21, the first line of new page is always occupied by the last line of last page, so it begin with index '02', but in some other case, fisrt line is empty and ready for input.
Now we have: FirstLine = 0
or FirstLine = 1 ( in our case, FirstLine is 1 because the first line of new page is fulfilled)
Step3: write a subroutine calcalculating number of pages
(here, the name of actual parameter is the same as formal parameter)
global data: FixedLine type i, " number of fixed line on a certain screen
LoopLine type i, " the number of lines occupied by one steploop item
FirstLine type i, " possbile value 0 or 1, 0 stand for the first line of new " scrolling screen is empty, otherwise is 1
Dataline type i, " number of items you will use in BDC, using DESCRIBE to get
pageno type i, " you need to scroll screen how many times.
line type i, " number of lines appears on the screen.
index(2) type N, " the screen index for certain item
begin type i, " from parameter of loop
end type i. " to parameter of loop
*in code sample, the DataTable-linindex stands for the table index number of this line
form calpage using FixedLine type i (see step 1)
LoopLine type i (see step 1)
FirstLine type i (see step 2)
DataLine type i ( this is the item number you will enter in transaction)
changing pageno type i (return the number of page, depends on run-time visible line in table control/ Step Loop)
changing line type i.(visible lines one the screen)
data: midd type i,
vline type i, "visible lines
if DataLine eq 0.
Message eXXX.
endif.
vline = ( sy-srows - FixedLine ) div LoopLine.
*for table control, you should compare vline with maximum line of
*table control, then take the small one that is min(vline, maximum)
*here only illustrate step loop
if FirstLine eq 0.
pageno = DataLine div vline.
if pageno eq 0.
pageno = pageno + 1.
endif.
elseif FirstLine eq 1.
pageno = ( DataLine - 1 ) div ( vline - 1 ) + 1.
midd = ( DataLine - 1 ) mod ( vline - 1).
if midd = 0 and DataLine gt 1.
pageno = pageno - 1.
endif.
endif.
line = vline.
endform.
Step4 write a subroutine to calculate the line index for each item.
form calindex using Line type i (visible lines on the screen)
FirstLine type i(see step 2)
LineIndex type i(item index)
changing Index type n. (index on the screen)
if FirstLine = 0.
index = LineIndex mod Line.
if index = '00'.
index = Line.
endif.
elseif FirstLine = 1.
index = LineIndex mod ( Line - 1 ).
if ( index between 1 and 0 ) and LineIndex gt 1.
index = index + Line - 1.
endif.
if Line = 2.
index = index + Line - 1.
endif.
endif.
endform.
Step5 write a subroutine to calculate the loop range.
form calrange using Line type i ( visible lines on the screen)
DataLine type i
FirstLine type i
loopindex like sy-index
changing begin type i
end type i.
If FirstLine = 0.
if loopindex = 1.
begin = 1.
if DataLine <= Line.
end = DataLine.
else.
end = Line.
endif.
elseif loopindex gt 1.
begin = Line * ( loopindex - 1 ) + 1.
end = Line * loopindex.
if end gt DataLine.
end = DataLine.
endif.
endif.
elseif FirstLine = 1.
if loopindex = 1.
begin = 1.
if DataLine <= Line.
end = DataLine.
else.
end = Line.
endif.
elseif loop index gt 1.
begin = ( Line - 1 ) * ( loopindex - 1 ) + 2.
end = ( Line - 1 ) * ( loopindex - 1 ) + Line.
if end gt DataLine.
end = DataLine.
endif.
endif.
endif.
endform.
Step6 using field sysbol in your BDC, for example: in ME21, but you should calculate each item will correponding to which index in steploop/Table Control
form creat_bdc.
field-symbols: <material>, <quan>, <indicator>.
data: name1(14) value 'EKPO-EMATN(XX)',
name2(14) value 'EKPO-MENGE(XX)',
name3(15) value 'RM06E-SELKZ(XX)'.
assign: name1 to <material>,
name2 to <quan>,
name3 to <indicator>.
do pageno times.
if sy-index gt 1
*insert scroll page ok_code"
endif.
perform calrange using Line DataLine FirstLine sy-index
changing begin end.
loop at DataTable from begin to end.
perform calindex using Line FirstLine DataTable-LineIndex changing Index.
name1+11(2) = Index.
name2+11(2) = Index.
name3+12(2) = Index.
perform bdcfield using <material> DataTable-matnr.
perform bdcfield using <quan> DataTable-menge.
perform bdcfield using <indicator> DataTable-indicator.
endloop.
enddo.
An example abap program of handling Table Control during bdc programming.
REPORT zmm_bdcp_purchaseorderkb02
NO STANDARD PAGE HEADING LINE-SIZE 255.
Declaring internal tables *
*-----Declaring line structure
DATA : BEGIN OF it_dummy OCCURS 0,
dummy(255) TYPE c,
END OF it_dummy.
*-----Internal table for line items
DATA : BEGIN OF it_idata OCCURS 0,
ematn(18), "Material Number.
menge(13), "Qyantity.
netpr(11), "Net Price.
werks(4), "Plant.
ebelp(5), "Item Number.
END OF it_idata.
*-----Deep structure for header data and line items
DATA : BEGIN OF it_me21 OCCURS 0,
lifnr(10), "Vendor A/c No.
bsart(4), "A/c Type.
bedat(8), "Date of creation of PO.
ekorg(4), "Purchasing Organisation.
ekgrp(3), "Purchasing Group.
x_data LIKE TABLE OF it_idata,
END OF it_me21.
DATA : x_idata LIKE LINE OF it_idata.
DATA : v_delimit VALUE ','.
DATA : v_indx(3) TYPE n.
DATA : v_fnam(30) TYPE c.
DATA : v_count TYPE n.
DATA : v_ne TYPE i.
DATA : v_ns TYPE i.
*include bdcrecx1.
INCLUDE zmm_incl_purchaseorderkb01.
Search help for file *
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
CALL FUNCTION 'F4_FILENAME'
EXPORTING
program_name = syst-cprog
dynpro_number = syst-dynnr
IMPORTING
file_name = p_file.
START-OF-SELECTION.
To upload the data into line structure *
CALL FUNCTION 'WS_UPLOAD'
EXPORTING
filename = p_file
filetype = 'DAT'
TABLES
data_tab = it_dummy.
Processing the data from line structure to internal tables *
REFRESH:it_me21.
CLEAR :it_me21.
LOOP AT it_dummy.
IF it_dummy-dummy+0(01) = 'H'.
v_indx = v_indx + 1.
CLEAR it_idata.
REFRESH it_idata.
CLEAR it_me21-x_data.
REFRESH it_me21-x_data.
SHIFT it_dummy.
SPLIT it_dummy AT v_delimit INTO it_me21-lifnr
it_me21-bsart
it_me21-bedat
it_me21-ekorg
it_me21-ekgrp.
APPEND it_me21.
ELSEIF it_dummy-dummy+0(01) = 'L'.
SHIFT it_dummy.
SPLIT it_dummy AT v_delimit INTO it_idata-ematn
it_idata-menge
it_idata-netpr
it_idata-werks
it_idata-ebelp.
APPEND it_idata TO it_me21-x_data.
MODIFY it_me21 INDEX v_indx.
ENDIF.
ENDLOOP.
To open the group *
PERFORM open_group.
To populate the bdcdata table for header data *
LOOP AT it_me21.
v_count = v_count + 1.
REFRESH it_bdcdata.
PERFORM subr_bdc_table USING: 'X' 'SAPMM06E' '0100',
' ' 'BDC_CURSOR' 'EKKO-LIFNR',
' ' 'BDC_OKCODE' '/00',
' ' 'EKKO-LIFNR' it_me21-lifnr,
' ' 'RM06E-BSART' it_me21-bsart,
' ' 'RM06E-BEDAT' it_me21-bedat,
' ' 'EKKO-EKORG' it_me21-ekorg,
' ' 'EKKO-EKGRP' it_me21-ekgrp,
' ' 'RM06E-LPEIN' 'T'.
PERFORM subr_bdc_table USING: 'X' 'SAPMM06E' '0120',
' ' 'BDC_CURSOR' 'RM06E-EBELP',
' ' 'BDC_OKCODE' '/00'.
MOVE 1 TO v_indx.
*-----To populate the bdcdata table for line item data
LOOP AT it_me21-x_data INTO x_idata.
CONCATENATE 'EKPO-EMATN(' v_indx ')' INTO v_fnam.
PERFORM subr_bdc_table USING ' ' v_fnam x_idata-ematn.
CONCATENATE 'EKPO-MENGE(' v_indx ')' INTO v_fnam.
PERFORM subr_bdc_table USING ' ' v_fnam x_idata-menge.
CONCATENATE 'EKPO-NETPR(' v_indx ')' INTO v_fnam.
PERFORM subr_bdc_table USING ' ' v_fnam x_idata-netpr.
CONCATENATE 'EKPO-WERKS(' v_indx ')' INTO v_fnam.
PERFORM subr_bdc_table USING ' ' v_fnam x_idata-werks.
v_indx = v_indx + 1.
PERFORM subr_bdc_table USING: 'X' 'SAPMM06E' '0120',
' ' 'BDC_CURSOR' 'RM06E-EBELP',
' ' 'BDC_OKCODE' '/00'.
ENDLOOP.
PERFORM subr_bdc_table USING: 'X' 'SAPMM06E' '0120',
' ' 'BDC_CURSOR' 'RM06E-EBELP',
' ' 'BDC_OKCODE' '=BU'.
PERFORM bdc_transaction USING 'ME21'.
ENDLOOP.
PERFORM close_group.
End of selection event *
END-OF-SELECTION.
IF session NE 'X'.
*-----To display the successful records
WRITE :/10 text-001. "Sucess records
WRITE :/10 SY-ULINE(20).
SKIP.
IF it_sucess IS INITIAL.
WRITE :/ text-002.
ELSE.
WRITE :/ text-008, "Total number of Succesful records
35 v_ns.
SKIP.
WRITE:/ text-003, "Vendor Number
17 text-004, "Record number
30 text-005. "Message
ENDIF.
LOOP AT it_sucess.
WRITE:/4 it_sucess-lifnr,
17 it_sucess-tabix CENTERED,
30 it_sucess-sucess_rec.
ENDLOOP.
SKIP.
*-----To display the erroneous records
WRITE:/10 text-006. "Error Records
WRITE:/10 SY-ULINE(17).
SKIP.
IF it_error IS INITIAL.
WRITE:/ text-007. "No error records
ELSE.
WRITE:/ text-009, "Total number of erroneous records
35 v_ne.
SKIP.
WRITE:/ text-003, "Vendor Number
17 text-004, "Record number
30 text-005. "Message
ENDIF.
LOOP AT it_error.
WRITE:/4 it_error-lifnr,
17 it_error-tabix CENTERED,
30 it_error-error_rec.
ENDLOOP.
REFRESH it_sucess.
REFRESH it_error.
ENDIF.
CODE IN INCLUDE.
Include ZMM_INCL_PURCHASEORDERKB01
DATA: it_BDCDATA LIKE BDCDATA OCCURS 0 WITH HEADER LINE.
DATA: it_MESSTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
DATA: E_GROUP_OPENED.
*-----Internal table to store sucess records
DATA:BEGIN OF it_sucess OCCURS 0,
msgtyp(1) TYPE c,
lifnr LIKE ekko-lifnr,
tabix LIKE sy-tabix,
sucess_rec(125),
END OF it_sucess.
DATA: g_mess(125) type c.
*-----Internal table to store error records
DATA:BEGIN OF it_error OCCURS 0,
msgtyp(1) TYPE c,
lifnr LIKE ekko-lifnr,
tabix LIKE sy-tabix,
error_rec(125),
END OF it_error.
Selection screen
SELECTION-SCREEN BEGIN OF LINE.
PARAMETERS session RADIOBUTTON GROUP ctu. "create session
SELECTION-SCREEN COMMENT 3(20) text-s07 FOR FIELD session.
SELECTION-SCREEN POSITION 45.
PARAMETERS ctu RADIOBUTTON GROUP ctu. "call transaction
SELECTION-SCREEN COMMENT 48(20) text-s08 FOR FIELD ctu.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(20) text-s01 FOR FIELD group.
SELECTION-SCREEN POSITION 25.
PARAMETERS group(12). "group name of session
SELECTION-SCREEN COMMENT 48(20) text-s05 FOR FIELD ctumode.
SELECTION-SCREEN POSITION 70.
PARAMETERS ctumode LIKE ctu_params-dismode DEFAULT 'N'.
"A: show all dynpros
"E: show dynpro on error only
"N: do not display dynpro
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 48(20) text-s06 FOR FIELD cupdate.
SELECTION-SCREEN POSITION 70.
PARAMETERS cupdate LIKE ctu_params-updmode DEFAULT 'L'.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(20) text-s03 FOR FIELD keep.
SELECTION-SCREEN POSITION 25.
PARAMETERS: keep AS CHECKBOX. "' ' = delete session if finished
"'X' = keep session if finished
SELECTION-SCREEN COMMENT 48(20) text-s09 FOR FIELD e_group.
SELECTION-SCREEN POSITION 70.
PARAMETERS e_group(12). "group name of error-session
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 51(17) text-s03 FOR FIELD e_keep.
SELECTION-SCREEN POSITION 70.
PARAMETERS: e_keep AS CHECKBOX. "' ' = delete session if finished
"'X' = keep session if finished
SELECTION-SCREEN END OF LINE.
PARAMETERS:p_file LIKE rlgrap-filename.
at selection screen *
AT SELECTION-SCREEN.
group and user must be filled for create session
IF SESSION = 'X' AND
GROUP = SPACE. "OR USER = SPACE.
MESSAGE E613(MS).
ENDIF.
create batchinput session *
FORM OPEN_GROUP.
IF SESSION = 'X'.
SKIP.
WRITE: /(20) 'Create group'(I01), GROUP.
SKIP.
*----open batchinput group
CALL FUNCTION 'BDC_OPEN_GROUP'
EXPORTING
CLIENT = SY-MANDT
GROUP = GROUP
USER = sy-uname.
WRITE:/(30) 'BDC_OPEN_GROUP'(I02),
(12) 'returncode:'(I05),
SY-SUBRC.
ENDIF.
ENDFORM. "OPEN_GROUP
end batchinput session *
FORM CLOSE_GROUP.
IF SESSION = 'X'.
*------close batchinput group
CALL FUNCTION 'BDC_CLOSE_GROUP'.
WRITE: /(30) 'BDC_CLOSE_GROUP'(I04),
(12) 'returncode:'(I05),
SY-SUBRC.
ELSE.
IF E_GROUP_OPENED = 'X'.
CALL FUNCTION 'BDC_CLOSE_GROUP'.
WRITE: /.
WRITE: /(30) 'Fehlermappe wurde erzeugt'(I06).
ENDIF.
ENDIF.
ENDFORM. "CLOSE_GROUP
Start new transaction according to parameters *
FORM BDC_TRANSACTION USING TCODE TYPE ANY.
DATA: L_SUBRC LIKE SY-SUBRC.
*------batch input session
IF SESSION = 'X'.
CALL FUNCTION 'BDC_INSERT'
EXPORTING
TCODE = TCODE
TABLES
DYNPROTAB = it_BDCDATA.
WRITE: / 'BDC_INSERT'(I03),
TCODE,
'returncode:'(I05),
SY-SUBRC,
'RECORD:',
SY-INDEX.
ELSE.
REFRESH it_MESSTAB.
CALL TRANSACTION TCODE USING it_BDCDATA
MODE CTUMODE
UPDATE CUPDATE
MESSAGES INTO it_MESSTAB.
L_SUBRC = SY-SUBRC.
WRITE: / 'CALL_TRANSACTION',
TCODE,
'returncode:'(I05),
L_SUBRC,
'RECORD:',
SY-INDEX.
ENDIF.
Message handling for Call Transaction *
perform subr_mess_hand using g_mess.
*-----Erzeugen fehlermappe
IF L_SUBRC <> 0 AND E_GROUP <> SPACE.
IF E_GROUP_OPENED = ' '.
CALL FUNCTION 'BDC_OPEN_GROUP'
EXPORTING
CLIENT = SY-MANDT
GROUP = E_GROUP
USER = sy-uname
KEEP = E_KEEP.
E_GROUP_OPENED = 'X'.
ENDIF.
CALL FUNCTION 'BDC_INSERT'
EXPORTING
TCODE = TCODE
TABLES
DYNPROTAB = it_BDCDATA.
ENDIF.
REFRESH it_BDCDATA.
ENDFORM. "BDC_TRANSACTION
Form subr_bdc_table *
text
-->P_0220 text *
-->P_0221 text *
-->P_0222 text *
FORM subr_bdc_table USING VALUE(P_0220) TYPE ANY
VALUE(P_0221) TYPE ANY
VALUE(P_0222) TYPE ANY.
CLEAR it_bdcdata.
IF P_0220 = ' '.
CLEAR it_bdcdata.
it_bdcdata-fnam = P_0221.
it_bdcdata-fval = P_0222.
APPEND it_bdcdata.
ELSE.
it_bdcdata-dynbegin = P_0220.
it_bdcdata-program = P_0221.
it_bdcdata-dynpro = P_0222.
APPEND it_bdcdata.
ENDIF.
ENDFORM. " subr_bdc_table
Form subr_mess_hand *
text *
-->P_G_MESS text *
FORM subr_mess_hand USING P_G_MESS TYPE ANY.
LOOP AT IT_MESSTAB.
CALL FUNCTION 'FORMAT_MESSAGE'
EXPORTING
ID = it_messtab-msgid
LANG = it_messtab-msgspra
NO = it_messtab-msgnr
v1 = it_messtab-msgv1
v2 = it_messtab-msgv2
IMPORTING
MSG = P_G_MESS
EXCEPTIONS
OTHERS = 0.
CASE it_messtab-msgtyp.
when 'E'.
it_error-error_rec = P_G_MESS.
it_error-lifnr = it_me21-lifnr.
it_error-tabix = v_count.
APPEND IT_ERROR.
when 'S'.
it_sucess-sucess_rec = P_G_MESS.
it_sucess-lifnr = it_me21-lifnr.
it_sucess-tabix = v_count.
APPEND IT_SUCESS.
endcase.
ENDLOOP.
Describe table it_sucess lines v_ns.
Describe table it_error lines v_ne.
ENDFORM. " subr_mess_hand
Also refer
http://sap.ittoolbox.com/groups/technical-functional/sap-dev/bdc-table-control-668404
and
http://www.sap-img.com/abap/bdc-example-using-table-control-in-bdc.htm
Regards,
srinivas
<b>*reward for useful answers*</b> -
Hey kids,
I have A BUNCH of video that I need to boil down in to multiple DVDs with multiple chapters per DVD (about 8 hours). Is there a description of a good work flow from iMove to iDVD described anywhere,....Do i need to export each "chapter" as a movie and then import them into iDVD in order to maintain a chapter structure?. If so what is the best way to do this,...HELP , PLEASE!!That's a lot of video! In general, the workflow I prefer is doing editing in iMovie, quitting, then open iDVD and import the video. iDVD has 3 options for converting video into the correct format for DVDs, and you set this in Preferences (up to 60 min=Best Performance; up to 120 min=Best Quality; the Pro setting takes longer, but does a better job with the more highly compressed 2hr video). With so much video, it might make sense to divide your footage by 110 minute blocks (there needs to be room for a few other files so you can't fit a full 120 minutes of video on a single layer DVD).
That's a high level overview; Klaus' links will give you more details; the "Missing Manual" and other books will provide lots more detail; and the forum here is good for questions.
John -
Possible work flow Shoot(RAW)-Aperture-CS2-Aperture-output
I have Aperture installed on two machines, my 15" 1.5Ghz/1.5GB-RAM and on my PoweMac dual 2Ghz G5/2 GB RAM and the speed is acceptable on both so far.
On the PowerMac I moved the Aperture library to a second SATA drive, which should speed things up a bit.
I have not had enough time to envelope myself in Aperture, only a hour here and there.... work keeps getting in the way But so far it looks like I could change my workflow.
CS2 cannot be removed from my workflow as I tweak all final images before output(print and jpg/tiff) in CS2. Layers and the healing brush is key in portrait work.
My workflow from shoot to output with D2X has been:
-Shoot(all RAW)
-FW transfer of files into date+clientname-named directory structure
-Bridge to sort, rank, annotate, etc
-ACR to make adjustments to files, copy and paste raw settings is great as well as synchronize make for quick post processing
-Web gallery is easy enough and IMO looks better than Aperture's
-Shots selected for final output by client are then opened in CS2, tweaked, cleaned, improved, vignettes applied, etc(according to client and contract), then saved off as jpg level 10(rarely as tiff)
--If it is a big or important portrait, I will save a PSD file with the layers etc
-Bridge to annotate the finished shots
-Output to Epson R2400 or lab
-Archive directory with sidecar files to two(just in case!) CD or DVD(depending on size)
While I can see a workflow improvement with Aperture replacing Bridge and ACR, issues I see:
-Aperture RAW conversions are not on par with ACR
-Raw workflow in Aperture is a completely different animal than ACR
-White balance in Aperture is hard to use
-Plugins? Like the vignette tool in ACR to dodge(great for white backgrounds) or burn corners
Possible pluses so far:
-More control over colors, luminance, etc in Aperture, although at the cost of simplicity(yes, this will diminish over time with more experience)
-The loupe tool is great, when it is too slow on the PB, I just use the "Z" key for toggling 100%..
-Integration of the photo books, although CS2 has something similar from Ofoto
-Stacking(this could be added to Bridge though)
-Vaults for archiving
-Coolness for being an Apple application(yes it is a cult and yes I joined of my own free will)
So, when 10.4.4 comes out with tweaks to Aperture like RAW conversions being on par with ACR and white balance tool option/fix, I could see Aperture replacing Bridge and ACR in my work flow.
Given my past four years with Apple and one iBook, two Powerbooks, two PowerMacs, one Indigo iMac, all of the OS X versions, and Final Cut Express, I have faith that the Aperture team is working feverishly to get theses initial issues fixed and am certain version two will be even better, AND encourage Adobe to add more wiz to their already great product, PhotoShop.
Tonight I will try this workflow, where I do the RAW conversion, send to CS2, and save back to Aperture....
So much to fiddle with, so little time!I'd love to hear how this works out for you as your workflow is virtually identical to mine. I haven't devoted much time to Aperture as I'm preparing for an xmas vacation and am hoping a big patch (or two!) are en route.
Rob -
Cc in work flow mail is required..
Hi,
cc in work flow mail is required.Please help me..
Balaji.TIn the function module SO_NEW_DOCUMENT_SEND_API1 if you see the table parameter RECEIVERS you have field COPY, you can mark it as 'X' for the user who should be copied to. Now since user can belong to any of the following categories. If you are using SAP inbox then use the first category.
SAP user name of the recipient
SAPoffice name of the recipient
Shared distribution list
Fax number in the form of structure SADRFD
Internet address in the form of structure SADRUD
Remote SAP name in the form of structure SADR7D
X.400 address in the form of structure SADR8D
You can directly invoke the function module whenever you want to send an eamil. I hope this answers your question.
Regards,
Kartik Nayak
Message was edited by:
KARTIK Nayak -
Hello experts ,
Created organization
Company
Hod of department user-mgr01 -- level 1
Manager user-mgr03 level 2
Employee 01 user-Emp01 level 3
Employee 02 user-emp02 level 3
Employee 03 user-emp03 level 3
In work flow I put two decision Step
1 for manager approval here I used rule 00000168.
2 for hod approval here I used rule 00000157.
After manager approved workitem should go to hod . this my scenario
employee 03 Trigger the workflow based on the rule 00000168 workitem will go to manager
It's working fine .
After manager approved
Next decision step will executed
Work Item should go to superior of ( Manager ) that is Hod of department, here I am using rule 157.
but it would go to manager.
How to solve .
Regards
Krishnan R.Hi
Thanks for response .
here we should not assign any hard coded values like position id, organisation id . but the workitem will go to his superior based on the organisation structure .
i did small mistake ,ok it is working in workflow . when i run the workflow seperately
i am executing the workflow through web dynpro abap ,
it getting started and working fine upto manager approvel .
but HOD approval decision step was not executed .here ( i am using rule 157 ) after approved manager .
but i specific organisation id instead of using rule 157 in HOD approver decision step of workflow .
it is working in uwl .
i want to use rule 157 in decision step of HOD
but it is not working in UWL . what should i change
Please give suggestion
Thanks and Regards
Krishnan R . -
Sql Query need to extract the Work Flow information from Hyperion Planning
Can Any one give me the sql query to extract the Work flow from Hyperion Planning in 11.1.2.1.
I can extract from the Hyperion Planning but it is not in required format again I need to do lot of formating. I need the information as per the flow structure is showing linke in one perticular planning unit in all coloumn format. Hence only sql query will help me to extract this kind of information. could any one provide the sql query to extract this kind of request.
Thanks in Advance.
Edited by: 987185 on Feb 9, 2013 10:57 PMIf you have a look at the data models in - http://www.oracle.com/technetwork/middleware/bi-foundation/epm-data-models-11121-354684.zip
There is the structure of the planning application tables, have a look at the HSP_PM_* tables
Alternatively you can look at extracting the information using LCM.
Cheers
John
http://john-goodwin.blogspot.com/ -
Populate dialogue processing box when raised work flow manually
Dear all,
Wish to seek your expertise on this. When users raise work flow manually using t-code OAWD, they have to fill in the dialogue processing box. In the dialog box, user need to fill in company code, division of the company and country of the company.
As this is prone to error, it is suggested that to enter the company code only, then the division and country will be auto populate. To do this, a customized table will be maintained for the company code, division and country.
The given function module to bring out the above dialogue is Z_POPUP_GET_REQ_VALUES as shown in the coding below.
Do you know how modify the function module to import back the country and division from the customized table and populate the fields? Is there a need to use User Exit or Screen Exit for the dialogue processing box so that when user press "Enter" the company code and division will be filled in automatically?
Thanks in advance for your help.
FUNCTION Z_POPUP_GET_REQ_VALUES .
*"*"Local Interface:
*" EXPORTING
*" VALUE(EV_BUKRS) TYPE BUKRS
*" VALUE(EV_LAND1) TYPE LAND1
*" VALUE(EV_SPART) TYPE ZELE_SPART
*" EXCEPTIONS
*" USER_CANCELLED
DATA LT_FIELDS TYPE TABLE OF SVAL.
DATA LS_FIELDS TYPE SVAL.
DATA LV_REPID TYPE SY-REPID.
DATA LV_RETURNCODE TYPE C.
LS_FIELDS-FIELD_OBL = 'X'.
LS_FIELDS-TABNAME = 'ZTBL_WF_DOCINFO'.
LS_FIELDS-FIELDNAME = 'BUKRS'.
APPEND LS_FIELDS TO LT_FIELDS.
LS_FIELDS-TABNAME = 'ZTBL_WF_DOCINFO'.
LS_FIELDS-FIELDNAME = 'ZLOC'.
APPEND LS_FIELDS TO LT_FIELDS.
LS_FIELDS-TABNAME = 'ZTBL_WF_DOCINFO'.
LS_FIELDS-FIELDNAME = 'SPART'.
APPEND LS_FIELDS TO LT_FIELDS.
* LS_FIELDS-TABNAME = 'ZTBL_WF_DOCINFO'. "Doc type is no longer required
* LS_FIELDS-FIELDNAME = 'AR_OBJECT'.
* APPEND LS_FIELDS TO LT_FIELDS.
LV_REPID = SY-REPID.
CALL FUNCTION 'POPUP_GET_VALUES_USER_CHECKED'
EXPORTING
FORMNAME = 'VALIDATE_VALUE'
POPUP_TITLE = 'DWM - Manual Workflow Entry'(001)
PROGRAMNAME = LV_REPID
* START_COLUMN = '5'
* START_ROW = '5'
* NO_CHECK_FOR_FIXED_VALUES = ' '
IMPORTING
RETURNCODE = LV_RETURNCODE
TABLES
FIELDS = LT_FIELDS
EXCEPTIONS
ERROR_IN_FIELDS = 1
OTHERS = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
IF LV_RETURNCODE = 'A'.
MESSAGE E000(K#) WITH 'User cancelled'(e01) RAISING USER_CANCELLED.
ELSE.
READ TABLE LT_FIELDS INTO LS_FIELDS INDEX 1.
EV_BUKRS = LS_FIELDS-VALUE.
READ TABLE LT_FIELDS INTO LS_FIELDS INDEX 2.
EV_LAND1 = LS_FIELDS-VALUE.
READ TABLE LT_FIELDS INTO LS_FIELDS INDEX 3.
EV_SPART = LS_FIELDS-VALUE.
* READ TABLE LT_FIELDS INTO LS_FIELDS INDEX 4. Doc type is no longer required
* EV_AR_OBJECT = LS_FIELDS-VALUE.
ENDIF.
ENDFUNCTION.
FORM VALIDATE_VALUE TABLES fields STRUCTURE sval
CHANGING error STRUCTURE svale.
TABLES ZTBL_WF_DOCINFO.
* Validate Company Code
READ TABLE fields INDEX 1.
ZTBL_WF_DOCINFO-BUKRS = fields-value.
SELECT SINGLE BUKRS INTO ZTBL_WF_DOCINFO-BUKRS FROM T001 WHERE BUKRS = ZTBL_WF_DOCINFO-BUKRS .
IF sy-subrc <> 0.
CLEAR error.
error-errortab = 'ZTBL_WF_DOCINFO'.
error-errorfield = 'BUKRS' .
error-msgty = 'E'.
error-msgid = 'GJ'.
error-msgno = '450'.
error-msgv1 = ZTBL_WF_DOCINFO-BUKRS .
exit.
ENDIF.
* Validate Country
READ TABLE fields INDEX 2.
ZTBL_WF_DOCINFO-ZLOC = fields-value.
SELECT SINGLE LAND1 INTO ZTBL_WF_DOCINFO-ZLOC FROM T005 WHERE LAND1 = ZTBL_WF_DOCINFO-ZLOC.
IF sy-subrc <> 0.
CLEAR error.
error-errortab = 'ZTBL_WF_DOCINFO'.
error-errorfield = 'ZLOC' .
error-msgty = 'E'.
error-msgid = '63'.
error-msgno = '721'.
error-msgv1 = ZTBL_WF_DOCINFO-ZLOC .
exit.
ENDIF.
* Validate Division
READ TABLE fields INDEX 3.
ZTBL_WF_DOCINFO-SPART = fields-value.
* Validate Document Type - No longer required
* READ TABLE fields INDEX 4.
* ZTBL_WF_DOCINFO-AR_OBJECT = fields-value.
* SELECT SINGLE AR_OBJECT INTO ZTBL_WF_DOCINFO-AR_OBJECT FROM TOADV WHERE AR_OBJECT = ZTBL_WF_DOCINFO-AR_OBJECT.
* IF sy-subrc <> 0.
* CLEAR error.
* error-errortab = 'ZTBL_WF_DOCINFO'.
* error-errorfield = 'AR_OBJECT' .
* error-msgty = 'E'.
* error-msgid = '00'.
* error-msgno = '058'.
* error-msgv1 = ZTBL_WF_DOCINFO-AR_OBJECT.
* error-msgv2 = SPACE.
* error-msgv3 = SPACE.
* error-msgv4 = 'TOADV'.
* exit.
* ENDIF.
ENDFORM.
Edited by: wanderer5 on Jul 12, 2010 5:00 PMHi Wanderer5 (is that your real name?)
I have no direct experience with starting workflows from OAWD, so I may be way off the mark...
So this is a workflow started by the creation of a stored document? What type? Can you tell if there are any normal events raised with the stored document? For example, if you are using invoice images, is the event BUS2081 CREATED raised? I ask because you could probably populate certain system fields from there.
You may also be able to make use of user parameters for certain fields.
Hope this helps,
Sue -
How to do release strategy work flow in MM
how to do release strategy work flow in MM. for purchase order release how to do release strategy work flow. please give elaberate steps
1: Install SAP - your IT support team should be able to help you with this
2: Start the SAP Logon Pad (it is in the Start menu if you use Windows - look around)
3: Go to transaction SPRO
4: Navigate the structure, go to materials management, purchasing and then look around
5: Read the documentation for each activity
6: Perform the activities
Seriously, you will be amazed by how much you can learn by actually making an effort.
PS: I see you <b>expect</b> 10 points for your one-line replies, so this one should be worth at least 50. -
Hi,
Can any1 tell me about the standard work flows (not work flow module) available in SAP. We want Purchase Requisition & PO release should be through email. (not SAP Inbox).
Thanks,
Rashid.hi rashid,
BC - Workflow Scenarios in Applications (BC-BMT-WFM)
Purpose
With SAP Business Workflow, SAP AG provides an efficient cross-application tool enabling integrated electronic management of business processes. SAP Business Workflow is a solution which has been integrated fully in the R/3 System and which enables customer-specific business process flows to be coordinated and controlled on a cross-application and cross-work center basis. SAP Business Workflow therefore enhances "ready-made" application software. The SAP Business Workflow definition environment can represent business processes simply and can respond to changing external conditions quickly, even in a live system, by adapting the existing business processes.
Workflow Scenarios
Many SAP applications use SAP Business Workflow enabling preconfigured workflow scenarios to be reused in various situations. The scenarios can either be implemented without any changes or configured for your business processes by making minor adjustments. These workflow scenarios reduce implementation time significantly and have been optimally configured for the respective application functions.
Many workflow scenarios are integrated in IDES (International Demonstration and Education System). It is possible to simulate the business processes of a model company in this fully-configured system.
Features
The workflow scenarios can be divided into three categories:
Creating events
Events are created to report status changes for an application object and to allow a reaction to the changes.
Document 4711/98 posted
Material XYZ created
These events can be used as triggering events for your own tasks or workflows. The events are therefore "connected" in a flexible and customer-specific way to application events, without having to modify the standard part of the application.
In some cases, the triggering of these events is not activated in the standard version, but depends on the Customizing settings. You can find further information in the application scenario documentation.
Providing SAP tasks
A task contains a task description and the connection to the application logic via the method for a business object. Before you can use a task productively, you must assign the tasks to its possible agents.
The tasks provided by SAP are generally used as steps in SAP workflows, but you can use them for your own developments as well.
Release change request
Change purchase order
If a workflow scenario only involves one task, the scenario can usually be regarded as a minimal solution for showing the connection between application functionality and SAP Business Workflow. For differentiated control, this SAP task should be replaced by a customer-specific task.
You can find further information in the application scenario documentation.
Providing SAP workflows
A workflow contains a complete workflow definition covering several steps. An SAP workflow has a complete workflow definition, but must still be adapted to the organizational environment of the customer.
Release a purchase requisition
Recruitment
In cases in which SAP workflows describe business processes which also occur in your company, or in cases in which changes should not be made to the SAP workflow for technical reasons, the SAP workflows supplied can be used without any changes or adapted using workflow configuration.
In all other cases, the SAP workflows can be used as templates for your own developments. The existing process structures of the business application components, which are often represented within a transaction, are generally not replaced. SAP Business Workflow is seen as an integration level "above" the standard business functions and uses the existing transactions, function modules, and reports.
see the below links for entire info on workflow.
help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMDEMO/BCBMTWFMDEMO.pdf
http://help.sap.com/saphelp_46c/helpdata/en/04/926f8546f311d189470000e829fbbd/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/103b1a61-294f-2a10-6491-9827479d0bf1
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/60559952-ff62-2910-49a5-b4fb8e94f167
http://www.sapmaterial.com/
thanks
sekhar
'reward me points if usefull -
Dear Friends,
1.Can somebody throw light on Work Flow management?
2.How is SD integrated with Work flow and what are the business processes that needs work flow in SD?
3.Is it like a Work flow consultant is required to handle this or can we handle the workflow from SD end itself?
Thanks
IsaacHi,
Few points on workflow was prepared by me and screen shots are not there. You can refer
ALE, EDI and IDOC Technologies for SAP by Arvind Nagpal
For further detail.
if the requirment is minimal then SD consultant can handle otherwise Workflow consultant is required.
Introduction
The workflow management system provides procedural automation of steps in business process. A business process can consist of several steps. Historically the tasks have been coordinated manually or by some means of communication (sticky note, email, shouting and so on). The common problem in these approaches is in efficiency; each lacks a way to trace where a task is, who executed (or executing) it, and how much time is required.
In contrast, workflow management system ensures that the right work is sent to the right person at the right time in the right sequence with the right information. The ALE/EDI interface mainly uses workflow for exception (or error) handling.
Application of Workflow in ALE/EDI
Error Notification
Error notification is the primary use of workflow. When exceptions are raised in the outbound and inbound process workflow is started and handled as shown in the below flow diagram.
Active Monitoring
Active monitoring allows you to specify threshold values for the state of the system. If the system crosses the threshold limit, a person responsible for the system problem can be notified. For example you can have some one notified when the number of failed invoice IDOCS in the system exceeds 50.
Rule Based Inbound Flow
This application of workflow in ALE/EDI does not under the category of error handling. You can set up workflow to handle processing of an inbound IDOC. Normally, an inbound IDOC starts a function module that invokes the posting program to create an application document from the IDOC.
In contrast, if you use a workflow, you can set up to do whatever is needed for your business process. SAP doesnu2019t provide standard workflows for the inbound ALE/EDI process, but you can develop your own workflows and tie them to the ALE/EDI process.
For example an incoming order change IDOC can be routed via workflow to a person for review. If the change requested are acceptable the IDOC can be posted.
The Architecture of ALE/EDI Workflow
The components used in ALE/EDI workflow fall into two categories:-
u2022 PD-ORG (organizational) object
u2022 Workflow object
You can view and maintain these components by using the T-code SWLD (Area Menu for workflow).
PD-ORG
Workflow
PD Organizational Objects
PD ORG object is used to represent the companyu2019s organizational structure in SAP. The following are the PD ORG objects.
u2022 Organizational Units (O)
An Organizational Unit can represent a department, physical location, division or subsidiary.
u2022 JOBS(C)
A job involves performing one or more business tasks. For example, sales order clerk, secretary and manager. Although it is possible to assign individual task directly to a position, it is advisable to group tasks together in a job and to assign the job to the position.
u2022 Position(S)
A position in a company represents his or her rank. If an employee is promoted, that person leaves his or her current position and is assigned to another position. For example, sales order clerk plant 1000, secretary of company code 1000 and manager of accounts.
u2022 Users (US)
A user is a person who has been granted access to the SAP system to use various functions.
All the above mentioned PD ORG objects can be created, changed and displayed by using following T-codes.
u2022 PPOCE Create mode.
u2022 PPOME Change mode.
u2022 PPOSE Display mode.
Screen shot1.
Work Flow Objects
Business objects
A business object represents a business entity that has a definite state and various properties. You can carry out various functions on the object. A business object encapsulates the entire functionality of an object. A business object is given a name in SAP.
For instance, a standard material is assigned the name BUS1001006; it has properties such as material number, description, and material type. These properties are represented using attributes of the business object. The various operations that can be carried out on an object are implemented with methods. For example, if you want to create a material, you can call that business objects create method. An object also has different states. It exposes its various states by publishing events. For example, the material object has created event that is published whenever a new material is created.
The T-code for Business Objects is SW01.
Screen shot2.
Tasks (T or TS)
A task defines a piece of work that can be executed and tracked in the system. Technically, a task points to a method of an object as shown in the below screen shot. In addition, a task defines the text the purpose of the task, the triggering event based on which the task is started, the terminating event that marks the completion of the task, and a role that contains the rules to identify the person who is responsible for executing the task. A task can be started in response to an event triggered in the system. Tasks are categorized as
u2022 Standard Task
Standard Task is provided by SAP and is client independent.
u2022 Customer Task
Customer Task is client dependent and is developed by customers.
The T-code for Tasks is PFTC.
Screen shot3.
Roles
Roles are workflow objects used to determine the person responsible for carrying out a specific task. Each task has a role assigned to it.
The T-code for Roles is PFAC.
Screen shot4.
Work item
A work item represents an instance of a task that needs to be executed. The work item can have various states that govern the operations allowed. The following table describes the various states of a work item and its effect on usability.
Status Description
Ready A work item is created and is visible to all selected agents.
Reserved A work item has been reserved by a user and disappears from all the inbox of other selected users.
In process A work item is being worked on and can be seen in the inbox of the user who started working on it.
Completed A work item is complete and cannot be seen in the inbox of any user
The SAP INBOX
The SAP inbox is an interface to manage workflow items and SAP office documents. The below screen shot shows a list of work items in a useru2019s inbox. The SAP inbox contains separate buckets for office documents and workflow items. Office documents are email documents and workflow items are work items. You can display and execute the work items from the inbox. The inbox is highly configurable.
Screen shot5.
Error Notification Process
The error notification process comprises the following steps:-
u2022 Determining the task to be started.
u2022 Routing the error to a responsible agent as a work item.
u2022 Processing of the work item by the responsible agent.
Possible Agents versus Selected Agents versus Actual Agents
A task has three types of agents based on rights to execute:
u2022 Possible agents
Possible agents represent persons who can execute a task. Not all the possible agents get a work item when a task is started.
Possible agents are configured in the system by assigning a task to
several HR objects (job, position, Org unit). A task can be set to
General task, which means that it can be executed by any one.
u2022 Selected agents
Selected agents are the users who get a work item in their inbox. They
are determined by role resolution logic. Selected agents must be a
subset of possible agents. If the selected agent is not found, the work
item is sent to all possible agents. The selected agents are configured
in the partner profile and the IDOC administrator in T-code WE46.
u2022 Actual agents
The actual agent is the person who executes the work item from the inbox. A work item can have several selected agents but only one actual agent. When a selected agent executes a work item, the actual agent for the work item is established, and the work item immediately disappears from the inbox of other selected agents. However, if an actual agent realizes that he or she cannot resolve the problem, the user can replace the work item, causing it to reappear in the selected agentu2019s inboxes.
Level of Agents in ALE/EDI process
Level 1
If a partner profile is located for the problem, the organizational object specified at the message level (inbound or outbound) in the partner profile is notified.
Level 2
If level 1 is cannot be identified because of the problem locating the record, the level 2 organizational object specified in the General View of the Partner profile is read.
Level 3
If neither level 1 nor level 2 can be identified, the system reads the EDICONFIG table for IDOC administrator and sends a notification.
Processing by the Responsible Agent
u2022 The steps necessary to fix an error for which a work item is generated are as follows.
u2022 Execute work item to display the error. Examples of errors include problems in the control record, errors in IDOC data, and incorrect configuration.
u2022 The cause of the problem can usually be determined from the error message. If applicable, additional error information is also available for certain type of errors (for example application errors).
u2022 After the cause of the problem has been determined, it must be fixed outside workflow (or in some cases, within workflow). The recovery procedure depends on the nature of the problem.
- If the error is in the IDOC data, the IDOC can be edited and then reprocessed from workflow.
- If the error requires restarting the process from the beginning, the IDOC has to be marked for deletion to stop it from further processing and to clear the work item from the inbox.
- If the error involves an IDOC that has not been created yet, the work item merely informs the person about the error.
Important T-codes
T-code Description
SWLD Area menu for work flow
SBWP or SO01 Sap inbox
SW01 Business object builder
PFTC Task/ Task Groups
PFAC Roles
SWU3 Maintain standard settings for SAP business workflow
PPOM To change ORG structure
SWUS Start workflow(Test Environment)
SWI15
SWI13 Task profile for user
Books Referred
ALE, EDI and IDOC Technologies for SAP by Arvind Nagpal -
Implementation work shop structure and questions
dear experts,
can some one get me detailed idea on the work shop structure before the blue print ?
what are the main activities need to covere ?
do some one have questions for the OM work shop ?
any high level diagram for OM process for reference ? any ppt ?
thanks and regards
chandraIn the workshop prior to the Bluerint you would need to cover the following points :
(Usually in the implemenatation projects the Core team is relatively new to Business process documentation )
1. identifying the list of business processes
2. identifying the person(s) responsible(functionally) for each business process
3. Breaking down the business process into business process steps.
4. The core team needs to be explicitly told that the same needs to be done irrespective of whether the step is in scope or not.
5. Drawing a flow chart based on the steps identified.
6. Ensuring that there are no open ends in the flow chart....i.e. every IF condition also has and else documentation/link
7. Start / end of process need to be clear
8. Input and output needs to be identified.
9.Owners (individual) and Unit (Owner Department) at each step need to be identified.
10.Process steps and flow chart needs to be verified with the business process owner.
11. Most Important : the Core team should not make any assumptions from what experience they have earlier, but get the facts from the team.
To Cover the points above we had done a smilar exercise at one of our projects using a case study of a a process of hypothetical company gave the same to each participant of the workshop. We then asked them to write down the process steps. We then got them to discuss the process steps as two seperate teams and draw a flow chart. All the above points came out as learnings.
All the Core team members and Functional consultants were involved in the workshop along with a few steer. com members -
Hi all,
i am new to Work flow,
can any body tell me how can i trigger the work flow from my abap program, and how can i send the required details from the program to W/F ?
kumarhi Narin,
i am new to WF,
it was not clear, actually i want to integrate the work flow with BPM in PI (Process Integration 7.0.
i am trying to create WF part in the SAP R/3, for the the Aproval part, because PI 7.0 doesnt have the feature User decision. So i am trying to push the data of Leave details to the WF and trigger the WF in the R/3 through a proxy program.
For creating Work flow, is Bussiness Object needed? What is the use of it, but i dont have any Business object for my Leave details, What to do?
My actual thought is,
1. create srcreen in SAP R/3, which has all the relevent fields of Leave details like emp_id, start date, end date, leave balance. i will put user commands(push buttons) like Approve, Reject, change.
In Wf this screen should apear with the leve fields with the corresponding values and push buttons.
once the manager or aprover clicks any the push buttons, in the next step the corresponding action should be done.
in this, is it possible to put the logic to capture the status of the WF like approved or Rejected? and send it back to the program in which this WF called?
Is it possible? or is there any alternative solution?
here in this i have query, how can i proceed? and what are the pre requisits to create WF?( like Busines Objects, triggring events, sep sequences, contaner elements, data base tables and structures etc.) and how do i create it?
can you give me the code? and Tcodes, to maitain events, etc....
can anybody help me?
thanks,
kumar -
Give me information about Work Flow Definition?
hi payal,
SAP Business Workflow
Purpose
SAP Business Workflow® is a cross-application tool which makes it possible to integrate business tasks between applications. This component supplements the existing, comprehensive, business functions of the R/3 System.
With this component, you can adapt the standard functions of the SAP R/3 System to the specific requirements of your enterprise. The component contains the functions and tools with which you can control and edit the cross-application processes.
Implementation Considerations
Many application components of the R/3 System use and integrate SAP Business Workflow functions. Therefore, be sure to execute the function Maintain standard settings for SAP Business Workflow in SAP Business Workflow Customizing.
Integration
Integration of SAP R/3 Functions
SAP Business Workflow is incorporated at an integration level above the transaction level. The component uses the existing transactions and function modules. The functionality and operability of the existing transactions and function modules are neither changed nor restricted by the workflow control. SAP Business Workflow does not intervene in the programmed processes within a transaction.
The component SAP Business Workflow, as a cross-application workflow management system, hence separates the organizational aspects of the control logic from the application logic. The component makes the R/3 System easier to operate, which is particularly useful for inexperienced or occasional users.
Integration of Organizational Management
The integration of the application component Organizational Management into SAP Business Workflow allows you to link tasks with the agents possible from an organizational point of view. This link allows the workflow management system to find the "right" agents and assign tasks to them.
Tasks and agents are linked on an abstract descriptive level based on jobs and organizational units. It is therefore possible for several employees having equal authorization within the organization to receive the same task for execution. One of these employees takes on this task and processes it. This assignment principle supports automatic load distribution within work groups with the same activity profile.
This means a high degree of transparency of business processes, including responsibilities.
Changes to the organizational structure of the enterprise and employee turnover therefore have direct effects in SAP Business Workflow as well, without changes having to be made there.
Features
With this component, you can automate and coordinate several business processes:
u2022 Complete work processes executed frequently
The level of complexity of these processes can vary. It ranges from functions which must be called by the user to continue processing, to event-driven business processes in which the R/3 System determines the individual steps by evaluating process-dependent information, and various agents then execute all the processing steps required.
The processing of activities is not necessarily tied to specific persons, but perhaps only to organizational units, project groups, or job descriptions.
u2022 Subprocesses
Examples of these include release or approval procedures involving two persons.
u2022 Reaction to error or exception situations
hope it helps u...
Maybe you are looking for
-
An important app won't work , just shows a black screen
Ok so I've got this app called "speedbit" , which happened to be important to me @_@ anyway , it won't work , whenever I open it , it just shows the program's Logo and then directly shows a black screen please , 1- I did restroe my Ipod touch (3g) 2-
-
I sync a Collection on my Mac with Lightroom Then I open lightroom on my iPad and I can see and work on it Then I activate syncing on a pc win, but I got a Warning about syncing catalogue and if I go on, I got the collection synced lost. thanks
-
Can I not download latest version of Safari without reinstalling OS X 10
Hi I have OSX 10.10.3 and Safari 8.4 I want to download the latest version of Safari without reinstalling Yosemite.
-
I have recently purchased a D300s and have tried import the raw files into LR but this fails with error "The files appear to be unsupported or damaged (1) " . I am OK with Jpegs and have been OK with other Nikon Raw files (D80). I can see the files i
-
Sip register message manipulation
Hi, I'm trying to register some third party Sip end point hat is not correct following the Sip rfc for cisco... what is does when it sends out a registrer message is: REGISTER sip:[email protected]:5060 SIP/2.0 Via: SIP/2.0/UDP 10.1.240.250:5060;rpor