Standard Workflow for Infotype 0019

is there any SAP standard WF for monitoring of task IT 0019

Hi,
There is no standard flow for the down payment request generally in many projects down payment requests are rarely created process starts with Down payment request F-47 then Down payments F-48
then clearing of Down Payment f-54
Down PAyment request is just a template.If you want to use then use then u can skip this step.
regards
Deepa

Similar Messages

Standard workflow for downpayment request approval

Hi,
Is there any standard workflow for downpayment request approval?
Please suggest.

Hi,
There is no standard flow for the down payment request generally in many projects down payment requests are rarely created process starts with Down payment request F-47 then Down payments F-48
then clearing of Down Payment f-54
Down PAyment request is just a template.If you want to use then use then u can skip this step.
regards
Deepa

Standard workflow for FB60 vendor invoice

Dear experts,
I am looking for a standard workflow for transaction FB60. Is that WS00400012(BO: BSEG)?
I just wonder if I could check the link between a transaction and business object.
In SWO1, BSEG is noted as "Accounting document line item". So i am not sure if it is for Vendor Invoice.

There are several standard workflows for vendor invoices. WS00400012 is for release of payment. If that is what you are looking for, it is fine. But go to the customizing to find more information about both the release for payment solution and the release for posting solution from SAP. Can't recall the customizing path now, but it is in Financial Accounting, I think the path is Accunts Receivable and Payable, then Business Transactions, and there you will at least find the Release for Payment part of it. The customizing screens are partly common, but the help available for the customizing nodes is most likely specific for each solution. I have never set up release for posting, so I don't know it.

Standard Workflow for Logistics invoice blocked for Quality

Hi friends
Edd here
I am wondering if there is a standard workflow for invoice verification if the invoice is blocked for QUALITY (not quantity)
i.e. if the Goods have been receipted Movement Type 103, to blocked stock, this should block the invoice.
Is there a standard workflow to pick up this event (RSEG-SPGRC ('Blocking Reason: Quality' = X)
Thanks and regards
Edd

There is no standard workflow for Quality, but you can create your custom wrokflow using similar logic what has been used for the Qty workflow.

Can i use standard workflow for invoice block ? (BUS2081 . WS20000397)

Hi Experts ,
Please any one help me to use the standard workflow for Handlinig invoices blocked(T-code MIRO ).
I want an email sent , when PO invoice is posted and blocked with attched PDF format .
checked Business object BUS2081 . and Workflow WS20000937.
But not sure how to use . Please help me to used to get the mail using the standard Workflow .
Thanks .

HI
Iam not pretty much sure about MM or Invoices I found one of the [SAP Help documentation|http://help.sap.com/erp2005_ehp_04/helpdata/EN/0e/0e3b0cb84111d3b5b2006094192bbb/frameset.htm] . This might help you to process ahead.
Regards
Pavan

Standard workflow for FBD1

Hi FI Guru
As per requirement,we have to create approval flow for recurring document (created in FBD1 for first time) also like FV60.
Is there any SAP Standard Workflow for this and how to see that.
Thanks in advance

Hi,
There is no standard flow for the down payment request generally in many projects down payment requests are rarely created process starts with Down payment request F-47 then Down payments F-48
then clearing of Down Payment f-54
Down PAyment request is just a template.If you want to use then use then u can skip this step.
regards
Deepa

Whether any bapi is available or not for infotype 0019(monitoring of dates)

Dear abapers,
can u plz guide me whether any bapi is available or not for infotype 0019(monitoring of dates)
i need to upload data from the text file to sap with the following fields.
*Pers No.     *
*Task Type     *
*Date Type     *
*Processing Indicator     *
*Reminder date     *
*Lead/follow-up time     *
*Lead/follow-up time     *
Comments
regards,
manoj

Hi,
Use this FM HR_INFOTYPE_OPERATION
Regards,
Shan

What is the standard workflow for Travel expense ?

Hi guys
i am looking for the standard workflow for travel expense. I did a search on the forum but count find a answer. I also searched SWDM - Workflow browser. I coudnt find one. Can anybody let me know which is the standard workflow for Travel Expense?

Hi
Check out these links.
[http://help.sap.com/saphelp_47x200/helpdata/en/04/928ba746f311d189470000e829fbbd/frameset.htm]
[http://help.sap.com/saphelp_47x200/helpdata/en/19/8460e002474d4a866da32a8d9c6c73/frameset.htm]
[http://help.sap.com/saphelp_47x200/helpdata/en/cb/c11038b42b7858e10000009b38f8cf/frameset.htm]
Regards
viijay

SAP Standard Workflow for PR Release (with user exit)

Hi SAP WF Gurus,
Good day!
I just wanted to check with you if you have ever used a user exit in the activation of the standard workflow for PR (overall ( release. What we have is a two0step approval process wherein each level has a proxy/alternate approver. We used the available user exit to accommodate this customer requirement since the standard release would only allow us to define 1 approver as a prerequisite for the next level. We were able to execute this on the first level approval; however, we observed that the workflow is not anymore triggered (i.e. does not send work items to agents) for the level 2 release. My questions therefore are:
1. How to set up SWEC? I already executed SWELS and SWEL to check if the events are being created and event linkage is automatically deactivated after running into an error regarding the binding...My initial SWEC setup is for BANF BUS2105 RELEASED On Change. I am assuming that since the workflow was released from the first level, this should be the starting point
2. How to rectify the binding error? I already executed automatic binding in the WF header for the start events but still face it
Your inputs/comments are most welcome
Regards,
DeLo

Just to add:
The error that I am encountering in the second run/cycle for the PR approval workflow is Import container contains errors (are any obligatory elements missing?)
Basically, WS20000077 will be executed if an approval level is seen. Once the approval is made, then the workflow is also completed. However, for multiple approvers, I only get to execute successfully the first level approval. The succeeding levels are encountering errors as stated above

Maintain texts for Infotype 0019 via ABAP.

Hi,
The issue is related to maintaining texts for Infotype 0019. I have a program below. The main problem is I am facing is for some records it inserts text in Infotype (0019) but for some it does not. Can anyone suggest why so or a way to resolve this problem ???
REPORT ytbctest009.
TABLES: pernr, pcl1.
INFOTYPES: 0019.
DATA: key LIKE pskey.
DATA: BEGIN OF ptext OCCURS 200.
DATA:   line(72).
DATA: END OF ptext.
SELECTION-SCREEN BEGIN OF BLOCK abc WITH FRAME TITLE text-001.
PARAMETERS:               p_pernr LIKE pernr-pernr.
SELECTION-SCREEN END OF BLOCK abc.
ptext-line = 'TEST 1'.
APPEND ptext.
ptext-line = 'Test 2'.
APPEND ptext.
ptext-line = 'Test 3'.
APPEND ptext.
rp-read-infotype p_pernr 0019 0019 '18000101' '99991231'.
SORT p0019 DESCENDING.
READ TABLE p0019 INDEX 1.
p0019-itxex = 'X'.
MOVE-CORRESPONDING p0019 TO key .
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
EXPORTING
    infty         = '0019'
    number        = p_pernr
    validityend   = p0019-endda
    validitybegin = p0019-begda
    record        = p0019
    operation     = 'MOD'.
EXPORT ptext TO DATABASE pcl1(tx) ID key.
Thanks in advance.

Hi Rajashree,
I hope , below code will solve the problem.
<b>Main Code</b>
FUNCTION zhr_mustus_update_it0019.
*"*"Local interface:
*" IMPORTING
*"     VALUE(IM_PERNR) TYPE P0019-PERNR OPTIONAL
*"     VALUE(IM_USRID) TYPE PA0105-USRID OPTIONAL
*"     VALUE(IM_SUBTY) TYPE P0019-SUBTY
*"     VALUE(IM_TERMN) TYPE P0019-TERMN OPTIONAL
*"     VALUE(IM_MNDAT) TYPE P0019-MNDAT OPTIONAL
*"     VALUE(IM_BVMRK) TYPE P0019-BVMRK OPTIONAL
*"     VALUE(IM_TEXT) TYPE CHAR30 OPTIONAL
*" EXPORTING
*"     VALUE(EX_RETURN_MESSAGE) TYPE STRING
*"     VALUE(EX_MESSAGE_ID) TYPE ARBGB
*"     VALUE(EX_MESSAGE_NUMBER) TYPE MSGNR
*" EXCEPTIONS
*"      SYSTEM_FAILURE
*"      COMMUNICATION_FAILURE
REFRESH bdcdata.
REFRESH it_bdc_message.
* Validations
PERFORM validations USING im_usrid im_subty im_mndat
                   CHANGING im_pernr
                            g_task_date
                            g_rem_date.
* Return message
MOVE:
    g_message TO ex_return_message,
    'ZMSGHR' TO ex_message_id,
    g_msgno   TO ex_message_number.
* If there any error don't process
CHECK ex_return_message IS INITIAL.
* If reminder date is missing then its creation
IF im_mndat IS INITIAL.
* Fill BDC for PA30 Creation
    PERFORM fill_bdc_for_creation USING im_pernr
                                        im_subty
                                        im_text
                                        g_task_date
                                        g_rem_date.
ELSE.
* Its a change, Fill BDC for PA30 change
    PERFORM fill_bdc_for_change USING im_pernr
                                      im_subty
                                      im_termn
                                      im_bvmrk
                                      im_text.
ENDIF.
* Call transaction PA30
PERFORM bdc_call_transaction.
* Return message
MOVE:
    g_message TO ex_return_message,
    g_msgid   TO ex_message_id,
    g_msgno   TO ex_message_number.
ENDFUNCTION.
<b>All Above Subroutines,</b>
*& Form Validations
* Validations for MUS/TUS
*      -->U_USRID      User id for TUS
*      -->U_SUBTY      Subtype 10 - MUS, 11 - TUS
*      -->U_MNDAT      Reminder date
*      <--PERNR        Person for MUS
*      <--U_TASK_DATE Task date
*      <--U_REM_DATE   Reminder date
FORM validations USING u_usrid     LIKE pa0105-usrid
                       u_subty     LIKE p0019-subty
                       u_mndat     LIKE p0019-mndat
              CHANGING u_pernr     LIKE p0019-pernr
                       u_task_date LIKE sy-datum
                       u_rem_date LIKE sy-datum.
DATA:
    BEGIN OF it_tmp_0019 OCCURS 0,
     termn LIKE pa0019-termn,
    END OF it_tmp_0019.
CLEAR g_message.
* Validations for MUS
IF u_subty EQ c_subty_10.
    MOVE sy-datum TO u_task_date.
    IF u_pernr IS INITIAL.
* Person number is missing
      MOVE:
        text-001 TO g_message,
        '003' TO g_msgno.
    ELSEIF u_mndat IS INITIAL.
* Its creation, check if there is already a open item
      SELECT pernr
        FROM pa0019
        INTO u_pernr
       WHERE pernr EQ u_pernr
         AND subty EQ u_subty
         AND bvmrk NE '2'.
        EXIT.
      ENDSELECT.
      IF sy-subrc EQ 0.
* Throw an error if there is already a open item
        MOVE:
          text-006 TO g_message,
          '004'    TO g_msgno.
      ENDIF.
    ENDIF.
ENDIF.
* Validations for TUS
IF u_subty EQ c_subty_11.
    IF u_usrid IS INITIAL
   AND u_pernr IS INITIAL.
* User/Person number is missing
      MOVE:
        text-002 TO g_message,
        '005'    TO g_msgno.
    ELSEIF NOT u_usrid IS INITIAL.
      SELECT pernr
        FROM pa0105
        INTO u_pernr
       WHERE usrid EQ u_usrid.
      ENDSELECT.
      IF u_pernr IS INITIAL.
* Person number is missing
        MOVE:
          text-001 TO g_message,
          '006' TO g_msgno.
      ENDIF.
    ENDIF.
    IF g_message IS INITIAL.
      SELECT termn
        FROM pa0019
        INTO TABLE it_tmp_0019
       WHERE pernr EQ u_pernr
         AND subty EQ u_subty
         AND bvmrk NE '2'.
      READ TABLE it_tmp_0019 WITH KEY termn = sy-datum.
* There is no open task for today
      IF sy-subrc NE 0.
        MOVE sy-datum TO u_task_date.
      ELSE.
* There is a open task for today, new task should be created next
* available date and reminder date is yesterday's date
        SORT it_tmp_0019 DESCENDING.
        READ TABLE it_tmp_0019 INDEX 1.
        u_task_date = it_tmp_0019-termn + 1.
        u_rem_date = sy-datum - 1.
      ENDIF.
    ENDIF.
ENDIF.
ENDFORM.                    "VALIDATIONS
*& Form Fill_bdc_for_creation
* BDC data for creation , Transaction PA30
*      -->U_PERNR      Person
*      -->U_SUBTY      Subty MUS - 10, TUS - 11
*      -->U_TEXT       Text
*      -->U_TASK_DATE Task date
*      -->U_REM_DATE Task date
FORM fill_bdc_for_creation USING u_pernr LIKE p0019-pernr
                                 u_subty LIKE p0019-subty
                                 u_text TYPE char30
                                 u_task_date LIKE sy-datum
                                 u_rem_date LIKE sy-datum.
* Scree1
DATA:
    l_task_date(10),
    l_rem_date(10).
* Use system date as Task date
WRITE:
    u_task_date TO l_task_date,
    u_rem_date TO l_rem_date.
PERFORM bdc_dynpro      USING 'SAPMP50A' '1000'.
PERFORM bdc_field       USING 'RP50G-PERNR'
                                u_pernr.
PERFORM bdc_field       USING 'RP50G-CHOIC'
                                '0019'.
PERFORM bdc_field       USING 'RP50G-SUBTY'
                                u_subty.
PERFORM bdc_field       USING 'BDC_OKCODE'
                                '=INS'.
* Screen2
PERFORM bdc_dynpro      USING 'MP001900' '2000'.
PERFORM bdc_field       USING 'P0019-TMART'
                                u_subty.
PERFORM bdc_field       USING 'P0019-TERMN'
                                 l_task_date.
IF NOT u_rem_date IS INITIAL.
    PERFORM bdc_field       USING 'P0019-MNDAT'
                                   l_rem_date.
ENDIF.
PERFORM bdc_field       USING 'RP50M-TEXT1'
                                u_text.
PERFORM bdc_field       USING 'BDC_OKCODE'
                                '/00'.
PERFORM bdc_dynpro      USING 'MP001900' '2000'.
PERFORM bdc_field       USING 'P0019-TMART'
                                u_subty.
PERFORM bdc_field       USING 'P0019-TERMN'
                                 l_task_date.
IF NOT u_rem_date IS INITIAL.
    PERFORM bdc_field       USING 'P0019-MNDAT'
                                   l_rem_date.
ENDIF.
PERFORM bdc_field       USING 'RP50M-TEXT1'
                                u_text.
PERFORM bdc_field       USING 'BDC_OKCODE'
                                '=UPD'.
ENDFORM.                    "fill_bdc_for_creation
*& Form fill_bdc_for_change
* BDC data for change , Transaction PA30
*      -->U_PERNR    Person
*      -->U_SUBTY    subtype MUS - 10 , TUS - 11
*      -->U_MNDAT    Reminder date
*      -->U_BVMRK    Status
*      -->U_TEXT     Text
FORM fill_bdc_for_change USING   u_pernr LIKE p0019-pernr
                                 u_subty LIKE p0019-subty
                                 u_termn LIKE p0019-termn
                                 u_bvmrk LIKE p0019-bvmrk
                                 u_text TYPE char30.
* Scree1
DATA l_termn_date(10).
WRITE u_termn TO l_termn_date.
PERFORM bdc_dynpro      USING 'SAPMP50A' '1000'.
PERFORM bdc_field       USING 'RP50G-PERNR'
                                u_pernr.
PERFORM bdc_field       USING 'RP50G-CHOIC'
                                '0019'.
PERFORM bdc_field       USING 'RP50G-SUBTY'
                                u_subty.
PERFORM bdc_field       USING 'RP50G-BEGDA'
                                l_termn_date.
PERFORM bdc_field       USING 'RP50G-ENDDA'
                                l_termn_date.
PERFORM bdc_field       USING 'BDC_OKCODE'
                                '=MOD'.
* Screen2
PERFORM bdc_dynpro      USING 'MP001900' '2000'.
PERFORM bdc_field       USING 'P0019-TMART'
                                u_subty.
PERFORM bdc_field       USING 'P0019-TERMN'
                                 l_termn_date.
PERFORM bdc_field       USING 'RP50M-TEXT1'
                                u_text.
PERFORM bdc_field       USING 'P0019-BVMRK'
                                u_bvmrk.
PERFORM bdc_field       USING 'BDC_OKCODE'
                                '=UPD'.
ENDFORM.                    "fill_bdc_for_change
FORM bdc_call_transaction.
DATA:
    l_mode(1) TYPE c VALUE 'N',
    l_lines   TYPE i,
    l_msgvar1 LIKE balm-msgv1,
    l_msgvar2 LIKE balm-msgv2,
    l_msgvar3 LIKE balm-msgv3,
    l_msgvar4 LIKE balm-msgv4.
CALL TRANSACTION 'PA30' USING bdcdata MODE l_mode
                           MESSAGES INTO it_bdc_message.
* Get last message
DESCRIBE TABLE it_bdc_message LINES l_lines.
READ TABLE it_bdc_message INDEX l_lines.
MOVE:
    it_bdc_message-msgid TO g_msgid,
    it_bdc_message-msgnr TO g_msgno,
    it_bdc_message-msgv1 TO l_msgvar1,
    it_bdc_message-msgv2 TO l_msgvar2,
    it_bdc_message-msgv3 TO l_msgvar3,
    it_bdc_message-msgv4 TO l_msgvar4.
* Prepare message
CALL FUNCTION 'MESSAGE_PREPARE'
    EXPORTING
      language               = sy-langu
      msg_id                 = g_msgid
      msg_no                 = g_msgno
      msg_var1               = l_msgvar1
      msg_var2               = l_msgvar2
      msg_var3               = l_msgvar3
      msg_var4               = l_msgvar4
    IMPORTING
      msg_text               = g_message
    EXCEPTIONS
      function_not_completed = 1
      message_not_found      = 2
      OTHERS                 = 3.
IF sy-subrc <> 0.
    MOVE text-005 TO g_message.
ENDIF.
ENDFORM.                    "BDC_FIELD
*        Start new screen                                              *
FORM bdc_dynpro USING program dynpro.
CLEAR bdcdata.
bdcdata-program = program.
bdcdata-dynpro   = dynpro.
bdcdata-dynbegin = 'X'.
APPEND bdcdata.
ENDFORM.                    "BDC_DYNPRO
*        Insert field                                                  *
FORM bdc_field USING fnam fval.
CLEAR bdcdata.
bdcdata-fnam = fnam.
bdcdata-fval = fval.
APPEND bdcdata.
ENDFORM.                    "BDC_FIELD
Cheers.
Santosh.

Standard workflow for SO approval process in CRM

Hi all
I would like to know if there is any standard workflow for Sales order approval process. I have tried my best and couldnt come across any.
And also what is the commonly used approval process?
Thanks & Regards
Mui Kanva

Hi
check workflows: WS10000279 and WS10001068 (aut approval).
But we created our own schema to implement two step approval.
Regards
Radek

Standard workflow for Service Order

Dear Experts,
I am working in SAP-CRM Implementation Project.Is there any Standard workflow for Service Order.It is very urgent Please help me.
Thanks & Regards,
Ashok.

Hi
go through the link below for workflow
http://help.sap.com/saphelp_46c/helpdata/en/a1/172437130e0d09e10000009b38f839/frameset.htm
Dinaker vikas

Activate standard workflows for ECM Approval

Hello,
I have to activate these standard workflows for ECM. Can anyone help me with the steps I need to follow?
WS04000022 ECM_SUBMIT
WS04000023 ECM_APPROVE
WS04000024 ECM_REJECT
WS04000025 ECM_CREATE
Regards,
MAK.

Hello,
Have you tried to activate the workflows in the Workflow Builder:
SWDD -> enter workflow -> Activate
Cheers,
Adalbert

SAP Standard Workflow for REFUNDS in FS-CD

Hi
We have a requirement to implement SAP Workflow in Financial Services Collections & Disbursements (FS-CD) module for REFUNDS Approval.
Is there any SAP standard Workflow available to meet the requirement?
How to find the Standard SAP workflows available for different Modules (MM, SD, PM, FI, FS-CD etc)?
Correct answers will be rewarded with points.
Thanks
Nikhil.B

Just to add:
The error that I am encountering in the second run/cycle for the PR approval workflow is Import container contains errors (are any obligatory elements missing?)
Basically, WS20000077 will be executed if an approval level is seen. Once the approval is made, then the workflow is also completed. However, for multiple approvers, I only get to execute successfully the first level approval. The succeeding levels are encountering errors as stated above

Standard Workflow for ESS changes.

Hi Experts,
We have a requirement where we need to change the Employee personal data and it has to be approved by the manager and then update the database.
We can do it by custom workflow, but is there any standard workflow template for this process and any standard screens for Manager approval process.
Kindly help. Thanks in advance.
Regards
Vijay.

go to swo3 and find related bo, then go to swe2 to find workflow according to bo

Standard Workflow for Infotype 0019

Similar Messages

Maybe you are looking for