{"action":"opened","issue":{"url":"https://api.github.com/repos/i042416/KnowlegeRepository/issues/847","repository_url":"https://api.github.com/repos/i042416/KnowlegeRepository","labels_url":"https://api.github.com/repos/i042416/KnowlegeRepository/issues/847/labels{/name}","comments_url":"https://api.github.com/repos/i042416/KnowlegeRepository/issues/847/comments","events_url":"https://api.github.com/repos/i042416/KnowlegeRepository/issues/847/events","html_url":"https://github.com/i042416/KnowlegeRepository/issues/847","id":269597224,"number":847,"title":"Form print tool","user":{"login":"i042416","id":5669954,"avatar_url":"https://avatars3.githubusercontent.com/u/5669954?v=4","gravatar_id":"","url":"https://api.github.com/users/i042416","html_url":"https://github.com/i042416","followers_url":"https://api.github.com/users/i042416/followers","following_url":"https://api.github.com/users/i042416/following{/other_user}","gists_url":"https://api.github.com/users/i042416/gists{/gist_id}","starred_url":"https://api.github.com/users/i042416/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/i042416/subscriptions","organizations_url":"https://api.github.com/users/i042416/orgs","repos_url":"https://api.github.com/users/i042416/repos","events_url":"https://api.github.com/users/i042416/events{/privacy}","received_events_url":"https://api.github.com/users/i042416/received_events","type":"User","site_admin":false},"labels":[{"id":629010610,"url":"https://api.github.com/repos/i042416/KnowlegeRepository/labels/C4C","name":"C4C","color":"fbca04","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-10-30T13:22:02Z","updated_at":"2017-10-30T13:22:02Z","closed_at":null,"author_association":"OWNER","body":"# Sent: Thursday, October 30, 2008 8:05 PM\r\nBy using the test tool, we can:\r\n\r\n1. directly trigger the form printing without doing lengthy steps in portal work center or in ESI_BO_TEST_TOOL. Save a lot of time in badi debugging.\r\n2. download the PDF and XML data file locally, without getting them from debugging.\r\n3. if there is something wrong with form output, tool can report the exact error location. If we do output in the portal and something goes wrong, we get nothing but 500 error.\r\n# How to use the tool\r\nSE38, run report Z_FORM_PRINT, Select BO proxy name, BO_ID,printer code , template code and template group code, and select the PDF and XML data file folder. In this example I want to print DeliveryNote 1.\r\nThen just click F8, and the real printing will be triggered.\r\n\r\n![clipboard1](https://user-images.githubusercontent.com/5669954/32172943-50bd72ac-bdb8-11e7-8a6d-af4107ba1607.png)\r\n\r\nYou can get the pdf and xml file stored in your local laptop, and the form is printed by the printer.\r\n\r\n![clipboard2](https://user-images.githubusercontent.com/5669954/32172957-597489da-bdb8-11e7-9c92-cb017147911a.png)\r\n\r\nIf you are interesting in the tool implementation, you can refer to followings:\r\n* FORM_TOOL~GET_OUTPUT_CONTROL_REQUEST:\r\nimplementation: association from hosting BO to CNTL_OUTPUT_REQUEST, then the ControlledOutputRequest.Root will be generated by BOPF automatically.\r\n* FORM_TOOL=>GET_OUTPUT_PRINT_ITEM:\r\nimplementation: execute action REFRESH_DEF_OR, which will trigger output parameter service to retrieve the output parametersets, which in turn will trigger PAF, message is assembled in this step.\r\n* FORM_TOOL=>SET_PRINTER:\r\nimplementation: change printer settings in ControlledOutputRequest.Item\r\n* FORM_TOOL=>PRINT\r\nimplementation: trigger real print action.\r\n> 这个tool是我经过以前一段时间阅读OM和AP的代码之后用业余时间写的,能够自动触发整个process agent framework 和form output的操作,因此能够触发我们badi里的断点,把生成的PDF和XML保存到本地,同时在SPOOL里面能看见output ID,在打印机处拿到打出来的form. 主要的logic都跑通了,如果觉得确实有些价值的话,我可以把它改成支持所有的form output,effort也不大.最初写的目的主要还是练习ABAP和进一步熟悉OM 代码."}}
{"actor":{"display_login":"i042416"}}