SAP for Insurance Discussions
Engage in conversations about risk management, customer experience, and digital transformation using SAP in the insurance industry. Join the discussion!
cancel
Showing results for 
Search instead for 
Did you mean: 

Alternative zu Stornobelegen im Freigabeworkflow

thomas_janssen
Explorer
0 Kudos

In FS-CD existieren Belege die noch nicht freigegeben sind. Bei Ablehnung im Freigabe-Workflow werden Stornobelege gebucht. Abhängig von der Menge der abgelehnten Belege gibt es ein hohes Aufkommen an "eigentlich nicht benötigten" Belegen im Hauptbuch. Gibt es eine Möglichkeit, dass zur Freigabe im Workflow befindliche Belege erst ins Hauptbuch übergeleitet werden, wenn diese auch freigegeben sind?

Im OSS waren keine passenden Lösungen auffindbar.

Vielen Dank für einen Hinweis.

1 ACCEPTED SOLUTION

former_member185321
Active Participant
0 Kudos

Hi,

Documents planned for the release in the workflow will not be posted and will not be transferred to the GL in SAP until they have been “completed” and/or “approved” (as necessary) through the workflow process after they are released.

If they are getting posted & transferred after getting released without being approved then you might need to check the  payment authorization settings and the Organization hierarchy settings of users in PD Org ( tcode - PPOMW). You can also check if FM 'RH_STRUC_GET' is performing as required.

The document which is rejected is then parked and is sent back to the initiator to be corrected or deleted. These parked documents can be viewed through transaction code FBV3 – to view a list of all parked documents. This high volume of "not really necessary" can be deleted then if they are not required.

Thanks,

Sagar

View solution in original post

5 REPLIES 5

former_member185321
Active Participant
0 Kudos

Hi,

Documents planned for the release in the workflow will not be posted and will not be transferred to the GL in SAP until they have been “completed” and/or “approved” (as necessary) through the workflow process after they are released.

If they are getting posted & transferred after getting released without being approved then you might need to check the  payment authorization settings and the Organization hierarchy settings of users in PD Org ( tcode - PPOMW). You can also check if FM 'RH_STRUC_GET' is performing as required.

The document which is rejected is then parked and is sent back to the initiator to be corrected or deleted. These parked documents can be viewed through transaction code FBV3 – to view a list of all parked documents. This high volume of "not really necessary" can be deleted then if they are not required.

Thanks,

Sagar

0 Kudos

Hi,

and thanks for your answer.

That's correct for Financials. But for Insurance the documents are posted directly. So when they got declined in workflow they got reversed.

0 Kudos

Hi,

Did you get a chance to find out what is causing the issue where docs are getting reversed.

There is an option under; Basic Functions -> Postings and Documents -> Workflows for Postings and Approvals -> Define Check Reasons.

where "no change" / "no reversal" can be enabled for check reason.

0 Kudos

All check reasons are enabled.

In FI you can post a document and wait for decission in workfow. When the document is declined, you can delete your document.

In FSCD you have to reverse your document.

So in FSCD when you decline a document, you have two documents, one for the posting a second for the reverse. In FI you have no documents.

0 Kudos

Hi Thomas,

Thanks for your reply.

Assuming that in FSCD you have created an approval workflow based upon the sample workflow 21000088 (which is usually done) ... the FSCD system permits the reversal of documents which is usually not desired. You may need to put a validation in event 0070 to prevent this.

If you are fine with the reversal of documents and want to clear up the reversed documents ( which are high in volume) then you may need to look at archiving them.

Thanks