Soundtrack 'noise fix' work flow?

Howdeedo all,
I am editing an interview footage, that has a hum noises and cracks all over. Terrible matirial really.
I just started editing, but wonder if it's really a good idea to edit this now and fix audio later, or just fix up the audio for whole original material, then edit.
I have 6 different interviews tapes all lasting around an hour. Each will be cut up to a 5 minute piece, Mixed in with some music. The interview will be used as sound bite, and will be majorly cut up. total length used for audio is about 60-120 seconds, depending on section.
I tried taking a peak in how Soundtrack works in fixing the sound. Since the whole interview clip that needs fixing, and since the interview bits will be sliced up quite a bit, I'm not sure if I should fix this later, but rather I think i should fix it right away.
If there is the same humm noise on the whole 60 min tape, isn't it easier to filter the whole footage first?
If I leave the mastering last, will that mean I have to export-fix-reimport for each and all the cuts of the edit? Is there a shortcut for this? Is there a way to cut and paste Sountrack changes, as if I put an video effect?
Thanks for any help.
Tak.

K and Andy,
Thanks for your advice.
I think I will take your advice. I'm just leaving this question not solved since there might be some solutions. Thanks for the time and advice.
Marked you two as helpful.
See you around.
Tak
PB 1GHz, Powermac G5   Mac OS X (10.4.6)  

Similar Messages

  • Soundtrack Pro Work Flow

    Can anybody share their work flow. I'm doing titles in LiveType, editing in FCP, scoring in Logic and final mix in Soundtrack Pro. I am having a difficult time finding a natural flow. Any advice would be appreciated. If there is already a thread on this, please guide me in the right direction. Thx.

    Zsion wrote:
    That's what I was thinking. How can I get the video to play on my external monitor via Logic?
    Logic uses quicktime to play the video so whatever quicktime can do, logic can do. If the movie is DV format for eg you can play it out via firewire. There's a setting in logic to to "play via firewire" (or something). I think its in the song settings under the video section. I haven't got Logic handy to check. If you do a quick search in the manual or help guide it'll be in there.
    If you have decent video I/O interface you can be watching full HD 1080p uncompressed movies on a plasma screen with logic if you want. Obviously that will put a huge strain on your computer though and not really advisable! As a rough 'n' ready solution I once used a cheap camcorder connected to a tv (analogue) with a firewire cable connected to my computer. Logic played my dv movie to the tv ok but I noted the picture was delayed a few frames. Its worth checking the sync and for this reason its always useful to have "burned in timecode" on the picture. You can adjust picture sync in Logic via a slider (song settings again I think). Its worth double checking everything is as it should be before you start work proper. Once its all set up right I find things work very well.
    You should not have any issues with sync when the movie is on your computer monitor and that is a significant advantage. I've seen folk use a second computer monitor for their movie for this reason.

  • File not found error at Attachement link in GroupVote of Human Work Flow

    Hi Gurus
    In Human Work flow,
    I have created the GroupVote and assigned to two person.
    I checked "share attachments and comments" to share their issues.
    One signed on to WorkApplist and review the forms and attached the file,
    The file link was created but it could not be downloaded.
    it could not delete.
    I tested several times it occured same results.
    It did not be happend when this option "share attachments and comments" was not checked.
    domain log and opmn log are as below.
    <2008-08-25 14:55:15,468> <ERROR> <oracle.bpel.services.workflow> <::> Identity Service Authentication failure.
    Identity Service Authentication failure.
    Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
    ORABPEL-10528
    Identity Service Authentication failure.
    Identity Service Authentication failure.
    Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
         at oracle.tip.pc.services.identity.jazn.xml.XMLAuthenticationService.authenticateUser(XMLAuthenticationService.java:150)
         at oracle.tip.pc.services.identity.jazn.xml.XMLIdentityService.authenticateUser(XMLIdentityService.java:426)
         at oracle.bpel.services.workflow.verification.impl.VerificationService.authenticateUser(VerificationService.java:299)
         at oracle.bpel.services.workflow.query.impl.TaskQueryService.authenticate(TaskQueryService.java:135)
         at worklistapp.servlets.Login.handleRequest(Login.java:101)
         at worklistapp.servlets.BaseServlet.doPost(BaseServlet.java:157)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
         at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:396)
         at java.security.AccessController.doPrivileged(Native Method)
         at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
         at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:410)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
         at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
         at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
         at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:302)
         at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:190)
         at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
         at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
         at java.lang.Thread.run(Thread.java:595)
    OAS version is 10.1.3.1.
    Any advice will be appricated.
    Thanks

    You are getting : ORABPEL-10528
    Identity Service Authentication failure.
    Identity Service Authentication failure.
    This means that you have wrong username/password entries in your configuration files. Please recheck them and then things should be fine...
    Hope this helps!
    Cheers
    Anirudh Pucha

  • Regarding work flow in the organisation

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

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

  • 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>

  • Work Flow in Status Error

    Hi Experts,
    I have a Workflow which triggers on record update.
    After the start step i have 3 assignment Fields and then Some validations etc.
    I can see that this workflow is stopped at First assignment step Some times with Error.
    And when i Open the workflow and close it again, then the next time there is a Update to a Record this workflow works fine...
    This is strange..
    the Workflow entry which is in ERROR will remain the same, Even if i press 'Perform' ..
    DId anyone face this issue earlier!!!
    It works fine for 2 days and suddenly i can see in Workflow table there is a entry with Error at First Assignment step of Workflow.
    when i Open work flow, Edit some description and save it back and the rest of the workflows from then are executing without error.
    But the one with Error in WF table still remains the same even after selecting 'Perform' on it.
    KR
    John

    Hi John,
    Please find details of a SAP Note 1553992 on this issue:
    Symptom
    - Data Manager crashes when trying to click on workflow job line (only    in MDM 5.5).
    - Workflow jobs are in error state due to executing next step such as     syndication step after a job was in error state due to bad assignment.
    Other terms
    - Workflow crash Data Manager, O28627 2011
    Reason and Prerequisites
    o Description of the root cause of the bug and ways to reproduce and/or diagnose the issue:
    Reproducing the scenario can be done by creating a workflow with the following steps:
    1. Start
    2. Bad Assignment (e.g. assignment created unique constraint violation)
    3. Syndication
    4. Stop
    After executing the workflow job, the job is shown in error state in MDM Data Manager.
    Clicking on next -> Syndication step changes the workflow job to a job that only the owner can see. The job is shown in MDM Data Manager in error state, its step description is empty and no user specified in user column.
    Clicking on the workflow job will lead to a crash in Data Manager.
    MDM Data Manager crashes since the workflow job is is in error state but none of his steps is in error state.
    In this mode(unlisted), MDS prepares the workflow list to be send to Data Manager with user name with value NULL.
    Data Manager crashes when it tries to access the user name of the workflow.
    The issue was introduce with MDM 5.5.
    Issue is not relating to a specific platform/DBMS.
    Solution
    o The workaround is:
    Delete workflow job in error state using Java API.
    o The description of the fix is:
    The fix handles two scenarios:
    1. Existing workflow jobs in error state that caused a crash
       in MDM Data Manager. A fix was made in MDS to add the owner as user
       name to the workflow jobs in such scenario.
       As a result users are able to delete the workflow job or show its
       history.
    2. New workflow job will not stay in Error state and the next step will
       be correctly performed.
    o The issue was fixed in the following code lines and versions:
    - MDM 5.5 SP06 Patch05 Hotfix 45 (Build 5.5.65.125) -
        change list #94328
    - MDM 7.1 SP07 (Build 7.1.07.113) - change list #94340
    - MDM 7.11     (Build 7.11.0.146) - change list #94339
    o What areas of the code were fixed?
    Workflow Run Time
    o What areas of the code were affected by the fix?
    Workflow Run Time
    o The following component(s) need to be replaced to correct the specific flaw addressed by this note:
    In 5.5 Version:
    Master Data Server
    MDM SERVER 5.5
    In 7.1 Version:
    Master Data Server
    o Additional component(s), if any, that were impacted and should be regression-tested by the code change:
    In 5.5 Version:
    GUI Clients
    JAVA API
    In 7.1 Version:
    Data Management Clients
    JAVA API
    Hope this helps.
    Thanks,
    Ravi

  • Regarding work flow for credit block release in sales order

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

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

  • 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

  • Work Flow & Procedure For Transportation Module Of SD

    Dear All,
    Currently, we have just got SD implemented. Now, we shall like to go for the Transportaion Module i.e. Order Booking, delivery and the PGI followed by Auto Invoicing. Now, we wants to go for Transportation Module  i.e. Shipment Creation, Shipment cost calculation , Service Order Creation etc. As we are quite new to this. So, we shall like to know the complete work flow & the procedure  for implementing the same. i.e. in what sequence the various transactions to be used for Master / Transaction.
    Please advise further.
    With Best Regards,
    Sanjeev Chugh

    Thanks for the reply. Definitely, i can share the details to the best of my knowledge about the transportation module.
    This module is basically meant for controlling purpose. Our main objective is to control the Transportaion Charges. Vendor Invoice must be cross verified from the sytem as well.
    Our Current Business Process : As per business process, we are having fixed rates per transporter for the type of vehicle and the source - destination combination. So, whenever, we are stock transferring the material from our mfg. plants to various depots, we are using various transporters (some one are specialised for south, some are spl. for east, so on and so forth). On the receipt of the material, receiver i.e. the destination branch , confirms the material receipt.. MIGO / MIRO etc. . We wants to capture the cost of the shipment as per the system and then on the receipt of the bill from transporter, the same must be cross verified.
    On going thru various documents from Web, I could gather the following details :
    1. After making deliveries, we have to make a shipment document. In our case, max. time it shall be an individual Shipment i.e. Tcode VT01N. Other type of shipment be Collective Shipment, which we use very less no. of times.
    2.  We have to prepare Shipment Cost document by using Tcode VI01
    3. We have to create a service Purchase Order By using ME21N.
    In our business scenario, we shall not be using legs concept as our shipments generally used to be from point to point basis.
    Sir, logically, i know our needs.. But getting stuck at a couple of points ... Like where to define various rates per transporter..That's why, i named the subject as the Work  Flow & Procedure for Tpt.Module.
    I shall like to request you to kindly advise further in this regard or kindly let me know if some study material is available from where i can comes to know about the exact work flow of the Transportation Module As Such.
    From Where I Can Get Help on Any Tcode Usage i.e How to use a Tcode and what be its basic functionality.
    With Best Regards,
    Sanjeev Chugh

  • UCCE 7.2 Missing Skill Groups in Supervisor Work Flow Setup

    Hi, one of our customers reported that when they try to configure a Work Flow for their supervisors in Supervisor Desktop, there are Skill Groups missing from the Available Skill Group List.
    I've tried to figure out what might cause this, and the only thing I've found that is different between the visible Skill Groups and the missing ones is that in Desktop Administrator => Personnel Configuration => Teams  I can see that the missing Skill Groups don't have any Skills listed in Selected Skills under the Skills tab.
    I've tried to find out where in ICM I can add the Skills, as the documentation says it's configured there, but I haven't had any luck so far.
    Anyone have any helpful tips please?

    Hi
    From the problem description I understand that you are seeing "available Skill groups"  empty  while trying to add a new work flow through CSD.
    This is a known defect with 5.x version which has not been fixed yet
    http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCth04959
    In 7.x this issue is not seen
    Hope this helps
    Regards
    Anuj

  • Work flow management - SD

    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
    Isaac

    Hi,
    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

  • Whats wrong with my work flow

    Ok this is my work flow for color and I am having problem at the very last stage of retuning to fcp.
    I have tried with DVCPRO changed to apl pro res and still it crashes. but then it can surprise me and it works so I retest and it's crash next time. 1 in 20 I would say.
    my system you can now see below as you can see it's as it should be thanks to Apple and there sales team. so the problem can't be there.
    so
    1 fcp to color corection work great.
    to render fine and then I save and then back to fcp
    2 fcp opens and it tries hard but then it back down and it's suck and start again all day I been trying
    3 is the last update that should come off and go back to 1.0
    4 bits i read could be to high tryed that no diffreance
    5 one clip at a time still no luck
    aslo taken of all effects still no luck
    So if you any one could help me out please write.
    Oh I am no good at spelling just a handicap I have.

    Hi it been night here and slepp is wounderful but thank you for your reply and yes i send to color.
    and if this helsp compression dose not work either has't since i move to the mac pro is all to with the intell ,
    would be great to fix all once and for all
    chres
    from blue skys from london

  • Adjustments Work Flow Question

    From what I have read the best approach for a work flow when adjusting raw images is to pretty much follow the order that the adjustments appear in the adjustments tab.  So one would do any RAW tuning followed by white balance then exposure and so on.
    Now if I have an image that I know I will want to crop........do I crop before I make and adjustments or do I crop after the adjustments and if I do crop first, does the histogram reflect the entire raw image or just the cropped area ?
    Thanks in advance for any input.

    Crop as early in the adjustment-making process as you can.  Likewise (but much less influential) with Straighten.
    Note that automatic adjustments (Exposure, Levels, Curves) are not "live" or dynamic -- once you make them, the result of the optimization is what is saved.  That means that if you apply Auto-Levels (for instance) and then crop, you will not get auto-leveling of the cropped Image -- you'll get whatever Levels settings were set when you activated the Auto-Leveler.
    This is easy to see.  Find a photo with some broad areas of different luminance, apply Auto-Levels to the entire Image, then crop an area of low luminance and -- keeping an eye on the histogram -- re-apply Auto-Levels.  Then, just for fun, uncheck the Crop Brick.
    To add to what Corky reported, the order of the Bricks is fixed, and that order is used whenever the Image is rendered -- whether to the screen or to a file or to a printer.
    In a gross sense, apply your Adjustments in the order of their Bricks.  But don't let that stop you from going back and tweaking Adjustments.  And, as above, know that all the auto-adjustments are optimized once, and then saved as the results of the optimization.
    I listed a suggested Adjustment-making order in this post.
    Message was edited by: Kirby Krieger

  • Service WO through IW31 (Control Key-PM03)- PR gets work flow error

    Hello All,
    When we create a Service Work order (Control Key "PM03") through the operations tab in a Work Order(IW31), When we open the PR we recieve an error:
    "Entry missing in table for Fund Center SP/"
    The work flow recieves an error message and an email will not be sent out to be approved.
    Any suggestions on to fix this.
    Thanks...

    Thanks Pete,
    Here is the error when we open the PR in ME53n or ME54n: "Entry missing in table for Fund Center SP"
    We checked our work flow table and the SP fund center is correct.
    When we create a service pr through me51n we do not get this error. Only when we create a service PR through IW31 (Control Key- PM03).
    THanks.

  • Better work flow for final audio mix

    Hi everyone,
    I just finished a 20min documentary shot on miniDV. I did the offline cut on my Powerbook G4 then took it to a post house for online and recording the narration and final mix.
    They exported my project to Pro Tools for the audio work. Evidently, when exporting to PT, all my level settings and audio transitions are lost, and we had to re-mix everything from scratch.
    Is this the typical work flow? This is my first paid gig as director/editor, so I'm new at this. But it seems quite ineffiecient.
    Is there a way to export my audio with all my audio settings intact? or at least the level settings. That way, the mixing engineer can fine-tune my rough mix rather than re-mixing from scratch. I'm wondering because I'm cutting another 20min piece where the audio mix, as rough as it is, is quite intricate, and I'd hate to have to re-do it all in PT.
    I suppose one way around this is to work with Soundtrack Pro. But I'm living in Vietnam, and the post houses/recording studios all use Pro Tools.
    Thanks.

    When we send out audio for sweetening we export the show as an OMF 2 file. This allows the PT folks to start with your exising clips and settings and then change them accordingly.
    From FCP you select your sequence and goto file>export>Audio to OMF. We usally give them a version with transitions and one without selectable on the export window. Once the OMF file is created you then image to a disk and hand it over. In return, they will give you bavk an OMF file which you reimport into your show and sync with your show. If your show starts at the 01 hour mark, start the show with one frame of bars and tone. Then have your show start two seconds later. This will make it easy for you to match back up. Also, you should give them a QT of the show with the same one frame of bars and tone for a visual reference for them.
    Hope that helps.
    Mac G5 Dual 2.0   Mac OS X (10.4.3)   Kona 2 HD SDI

Maybe you are looking for