{"id":3378,"date":"2016-02-29T16:23:23","date_gmt":"2016-02-29T15:23:23","guid":{"rendered":"https:\/\/compera.vanvlerken.nl\/tweaken-van-sap-invoice-management-by-opentext\/"},"modified":"2018-03-26T14:43:46","modified_gmt":"2018-03-26T13:43:46","slug":"tweaken-sap-invoice-management-opentext","status":"publish","type":"post","link":"https:\/\/compera.vanvlerken.nl\/en\/tweaken-sap-invoice-management-opentext\/","title":{"rendered":"Tweaking SAP Invoice Management by OpenText"},"content":{"rendered":"<p>[et_pb_section bb_built=&#8221;1&#8243; admin_label=&#8221;section&#8221; prev_background_color=&#8221;#000000&#8243;][et_pb_row admin_label=&#8221;row&#8221; background_position=&#8221;top_left&#8221; background_repeat=&#8221;repeat&#8221; background_size=&#8221;initial&#8221;][et_pb_column type=&#8221;4_4&#8243;][et_pb_text background_layout=&#8221;light&#8221; text_orientation=&#8221;left&#8221; use_border_color=&#8221;off&#8221; border_color=&#8221;#ffffff&#8221; border_style=&#8221;solid&#8221; background_position=&#8221;top_left&#8221; background_repeat=&#8221;repeat&#8221; background_size=&#8221;initial&#8221;]<\/p>\n<p>I noticed it in my SAP\u00a0career several times and maybe you recognize it too: Sometimes we forget that implementing and\/or activating a small functionality in a system, can result in a major improvement. There are various reasons why these features are not implemented, like time and money or they are just unknown to you.<\/p>\n<p>SAP Invoice Management by OpenText (VIM) and Invoice Capture Center (ICC) have several features which optimize\u00a0your already streamlined invoice management without any major effort. Please find below two of these features available in the current release of VIM 7.0 and ICC 7.0. These small\u00a0tweaks will help you to get more out of your system.<\/p>\n<h4>Return to vendor<\/h4>\n<p>With the latest Support Pack (SP4) of VIM 7.0 the Return to Vendor (RTV) functionality is introduced. This function allows you to inform the vendor via email that the invoice is being returned. It also terminates the Document Processing (DP) workflow. The vendor is informed by an e-mail that is generated based on a template that the VIM user selects. The email lists the return reasons. It may contain additional comments and may have the invoice image or additional images attached. VIM users can select several return reasons that are maintained in VIM customizing.<\/p>\n<p>When the user clicks the Return to Vendor process option in the DP dashboard, a new screen opens where all RTV-related information must be entered.<\/p>\n<p>When the RTV function is performed successfully, the generated email is sent using standard SAP functionality. The DP document is set to obsolete and the DP workflow is finished. Return reasons are stored along with the DP step comments.<\/p>\n<p>So what is exactly the effort to implement this functionality?<\/p>\n<ul>\n<li>Configuring SAPConnect and SMTP (standard functionality and likely already configured);<\/li>\n<li>Maintain the new process option 2026 Return to Vendor in the customizing and maintain this option for selected process types and roles according to your organizational needs;<\/li>\n<li>Maintain return reasons;<\/li>\n<li>Maintain the e-mail templates through transaction SO10 (plain and simple&#8230;).<\/li>\n<\/ul>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone\" src=\"https:\/\/compera.vanvlerken.nl\/wp-content\/uploads\/2016\/02\/DP_Dashboard_process_option_to_SO10_example_e-mail1.e0011e277b87d70343d70089d061da0d.png\" width=\"836\" height=\"381\" \/><\/p>\n<p>The vendor email address to be used is normally read from the\u00a0vendor master, though you can override this logic using a user exit, which is a function module that can be maintained as a constant in the customizing.<\/p>\n<p>Perhaps Return\u00a0To\u00a0Vendor\u00a0isn\u2019t the\u00a0fanciest solution, but because of its flexibility it definitely contributes to a more efficient way of processing vendor\u00a0invoices.<\/p>\n<h4>Stop attachment extraction<\/h4>\n<p>Sometimes invoices are followed by excessive attachments, while it is known that nearly all invoices won\u2019t exceed a certain number of pages. In some applications high runtimes and problems may occur regarding invoices with very large attachments if no patch code sheet is used during extraction. With this patch code sheet, also known as a separator sheet, the character recognition and data extraction will be stopped as soon as start of an attachment has been determined.<\/p>\n<p>However it is difficult to apply a separator sheet with, for example, digitally received PDF invoices; If\u00a0you are using third\u00a0party solutions, such as Kofax Express, you could pass this separator sheet within the created document. However it still remains a manual activity.<\/p>\n<p>With the introduction of Invoice Capture Center 7.0 it is now possible to prevent these unnecessary high runtimes and problems during recognition, automatically.<\/p>\n<p>This automatic attachment detection can be easily configured in the customizing of your ICC application. Just activate the &#8220;stop attachment extraction&#8221; check box. ICC then tries to determine whether the invoice has been completed at a preceding page so that the current page already belongs to an attachment. In this case ICC invoice processing is stopped for the remaining pages.<\/p>\n<p>Of course you can combine this setting together with the option after how many pages the character recognition needs to be stopped.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone\" src=\"https:\/\/compera.vanvlerken.nl\/wp-content\/uploads\/2016\/02\/Stop_attachment_extraction.2abaab63ad9bd0b9002588f06a7a3217.png\" width=\"777\" height=\"386\" \/><\/p>\n<p>[\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section]<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I noticed it in my SAP\u00a0career several times and maybe you recognize it too: Sometimes we forget that implementing and\/or activating a small functionality in a system, can result in a major improvement. There are various reasons why these features are not implemented, like time and money or they are just unknown to you. SAP [&hellip;]<\/p>\n","protected":false},"author":7,"featured_media":3013,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"on","_et_pb_old_content":"<p>Ik heb het in mijn SAP\u00a0carri\u00e8re al verschillende keren meegemaakt en misschien herkent u het ook?: Soms vergeten we dat het implementeren of activeren van een kleine setting in een systeem kan resulteren in een wezenlijke verbetering van het proces. Er zijn diverse redenen te noemen waarom dergelijke functionaliteiten niet worden ge\u00efmplementeerd; tijd, geld of wellicht zijn ze simpelweg onbekend\u2026<\/p><p>SAP Invoice Management by OpenText (VIM) en Invoice Capture Center (ICC) hebben functionaliteiten die uw factuurverwerkingsproces optimaliseren zonder noemenswaardige inspanning. Hieronder noem ik twee van deze in VIM 7.0 en ICC 7.0 beschikbare settings waardoor u meer uit uw proces en systeem kunt halen.<\/p><h4>Return to vendor<\/h4><p>Met de recente support pack 4 van VIM 7.0 wordt de Return To Vendor (RTV) functionaliteit ge\u00efntroduceerd. Deze functionaliteit maakt het mogelijk om de leverancier via email te informeren dat de factuur wordt geretourneerd en het be\u00ebindigt ook de Document Processing (DP) workflow. De email naar de leverancier wordt gegenereerd op basis van een template dat de VIM gebruiker selecteert. De email bevat de retourredenen en kan ook additionele opmerkingen bevatten en als attachment de scan van de factuur of andere scans. VIM gebruikers kunnen verschillende retourredenen selecteren die worden onderhouden in de VIM customizing.<\/p><p>Zodra de gebruiker de Return To Vendor optie selecteert in het DP dashboard, wordt een nieuw scherm geopend waar alle RTV gerelateerde informatie moet worden ingevoerd.<\/p><p>Als de RTV transactie correct wordt uitgevoerd, wordt de gegenereerde email via standaard SAP functionaliteit verzonden. Het DP document wordt \u201cobsolete\u201d gezet en de DP workflow wordt be\u00ebindigd. Retourredenen worden opgeslagen samen met de DP step opmerkingen.<\/p><p>En wat is nu precies de inspanning om deze RTV functionaliteit te implementeren?<\/p><ul><li>Configureren van SAPConnect en SMTP (standaardfunctionaliteit en in vaak al aanwezig);<\/li><li>Inrichten van de nieuwe procesoptie 2026 Return To Vendor in de customizing en het onderhouden van deze optie voor de voor uw organisatie van toepassing zijnde procestypen en rollen;<\/li><li>Onderhouden van retourredenen;<\/li><li>Onderhouden van de e-mailtemplates via transactie SO10 (oud en vertrouwd\u2026).<\/li><\/ul><p><img src=\"https:\/\/compera.vanvlerken.nl\/nl\/assets\/components\/phpthumbof\/cache\/DP_Dashboard_process_option_to_SO10_example_e-mail1.e0011e277b87d70343d70089d061da0d.png\" alt=\"\" \/><\/p><p>Het leveranciers e-mailadres dat wordt gebruikt komt standaard uit de leveranciersstam. Dit kan echter worden overschreven door een user exit \/ functiemodule die als een constante kan worden onderhouden in customizing.<\/p><p>Ik besef dat de RTV wellicht niet de meest fancy oplossing is, maar vanwege zijn flexibiliteit draagt het zeker bij aan een meer effici\u00ebnt factuurverwerkingsproces.<\/p><h4>Stop attachment extractie<\/h4><p>Soms worden facturen vergezeld door zeer grote attachments terwijl bekend is dat het gros van de facturen niet boven een bepaald aantal pagina\u2019s uitkomt. In bepaalde applicaties kunnen hoge runtimes en problemen voorkomen met deze facturen en grote attachments als geen zogenaamde patch code sheet wordt gebruikt gedurende de extractie. Met deze patch code sheet (of separator sheet) wordt de karakterherkenning en data-extractie gestopt zodra het begin van een attachment wordt bepaald.<\/p><p>Ofschoon een dergelijke patch code sheet lastig toe te passen is met bijvoorbeeld digitaal ontvangen pdf facturen; Als u third party oplossingen zoals Kofax Express gebruikt dan kunt u deze separator sheet overslaan binnen het gecre\u00eberde document. Maar het blijft een handmatige activiteit.<\/p><p>Met de introductie van Invoice Capture Center 7.0 is het echter mogelijk om deze onnodige hoge runtimes en problemen tijdens de herkenning automatisch te voorkomen. Deze automatische attachment detectie kan gemakkelijk worden geconfigureerd in de customizing van ICC door simpelweg de \u201cstop attachment extraction\u201d checkbox te activeren. ICC probeert dan te bepalen of de factuur eindigt bij de vorige pagina, waardoor de huidige pagina bij de attachment hoort. Als dat het geval is, dan stopt de ICC factuurverwerking voor de rest van de pagina\u2019s.<\/p><p>Deze setting kan overigens ook worden gecombineerd met de optie na hoeveel pagina\u2019s de karakterherkenning moet stoppen.<\/p><p><img src=\"https:\/\/compera.vanvlerken.nl\/nl\/assets\/components\/phpthumbof\/cache\/Stop_attachment_extraction.2abaab63ad9bd0b9002588f06a7a3217.png\" alt=\"\" \/><\/p>","_et_gb_content_width":"","footnotes":""},"categories":[1],"tags":[],"class_list":["post-3378","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/compera.vanvlerken.nl\/en\/wp-json\/wp\/v2\/posts\/3378","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/compera.vanvlerken.nl\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/compera.vanvlerken.nl\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/compera.vanvlerken.nl\/en\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/compera.vanvlerken.nl\/en\/wp-json\/wp\/v2\/comments?post=3378"}],"version-history":[{"count":0,"href":"https:\/\/compera.vanvlerken.nl\/en\/wp-json\/wp\/v2\/posts\/3378\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/compera.vanvlerken.nl\/en\/wp-json\/wp\/v2\/media\/3013"}],"wp:attachment":[{"href":"https:\/\/compera.vanvlerken.nl\/en\/wp-json\/wp\/v2\/media?parent=3378"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/compera.vanvlerken.nl\/en\/wp-json\/wp\/v2\/categories?post=3378"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/compera.vanvlerken.nl\/en\/wp-json\/wp\/v2\/tags?post=3378"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}