Skip to Content

Process Models and H99_POST_PAYMENT

Our process models are broken, and do not post payments to either FI or 3rd Party. The FI documents are created, but not posted. The 3rd party evaluation runs are created, but not stored (URMU) or posted (URMP).

In reviewing our models, we do not use H99_POST_PAYMENT. Is that our problem? Is there any guidance anyone can provide on setting up and using H99_POST_PAYMENT in our off-cycle process models?

Thanks in advance.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

7 Answers

  • Best Answer
    Sep 20 at 10:50 PM

    Hello Deborah Moses - thanks for the response. The program category CIPE is for execution (posting execution step). I believe for transfer to finance and release it will be CIPS. And the categories are assigned programs in config tables. Take a look at tables T52SE and T52SES or T52SES_C. Refer to Note 408953 on this. It explains the issue and steps to take to add these programs to process model. These programs may have to be mapped to correct category to make it available in a process model. The note also has a recommendation to add a breakpoint using a function module to stop release for incorrect statuses.

    I'm really surprised that SAP isnt including a step for release and transfer to FI in their "template" process model. May be because SAP wants the release and transfer steps to be executed manually?thats what the above referenced note is alluding to.

    Thanks

    Chandra

    Add comment
    10|10000 characters needed characters exceeded

  • Sep 12 at 12:05 AM

    You can refer to standard delivered process model SAPUSOC or SAPUSPAY (there are several other; all US delivered model process model start with SAPUS) and compare with your set up and adjust accordingly. For third party postings, I believe you are using the old multi-stage 3rd party process (U500, URMU); you may want to check the single step process RPURME00.

    Add comment
    10|10000 characters needed characters exceeded

  • Sep 16 at 01:43 PM

    Chandramouly Veeramony Thank you for your response.

    If we don't use the single step posting process, could I still use it in my process model?

    My issues with the current setup (see attached) are:

    1. FI posting documents get created, but don't get released or posted
    2. 3rd party temse files get created (U500), but don't store (URMU) or post (URMP)
    Add comment
    10|10000 characters needed characters exceeded

  • Sep 16 at 05:09 PM

    You can try adding steps for RPCIPA00 and RPCIPP00 to release and post. However I do not know if those are supported inside the process model. Check SAP delivered model SAPUSBON and adapt accordingly.

    Add comment
    10|10000 characters needed characters exceeded

  • Sep 18 at 06:28 PM

    I added the 2 programs you mentioned, but get an error in my consistency check. I'm guessing this means they are not supported.

    I checked SAPUSBON, and the only difference is that the payroll run isn't needed in my process model. Do you have other suggestions? I do appreciate your guidance.


    Add comment
    10|10000 characters needed characters exceeded

  • Sep 25 at 01:53 PM

    Chandramouly Veeramony - THANK YOU THANK YOU! The Note was not applicable to our system, but following your guidance to add the 2 program categories CIPA and CIPP for execution in the process model worked. I was able to post to both FI and to 3rd party.

    I have one other question. If the posting to FI results in incorrect documents, is there a way to restart that process in PUST? Or does the incorrect run have to be rerun manually (PC00_M99_CIPE)?

    Add comment
    10|10000 characters needed characters exceeded

  • Sep 26 at 08:15 PM

    Deborah Moses great to hear! glad it was helpful.

    Regarding restarting a failed run via PUST. Yes there is a start/repeat option at each step (right click>step>start/repeat). Its been a while I worked on process model and it isnt activated in my current system, but I do remember, once a step has failed, it goes into "stop" mode and after the issue is resolved, you would have to repeat that step to complete it. Even if you complete that step manually (by doing a manual post via PCP0 or via direct programs), you do have to mark the steps "complete" in PUST. Now that the main portions are working, you should be able to test these scenarios in Dev/QA systems.

    Add comment
    10|10000 characters needed characters exceeded