{"id":1664,"date":"2014-08-20T10:14:40","date_gmt":"2014-08-20T08:14:40","guid":{"rendered":"http:\/\/websha.de\/xstepcafe\/?p=1664"},"modified":"2018-06-01T06:45:16","modified_gmt":"2018-06-01T04:45:16","slug":"search-the-xstep-repository","status":"publish","type":"post","link":"https:\/\/websha.de\/xstepcafe\/2014\/08\/20\/search-the-xstep-repository\/","title":{"rendered":"Search the XStep Repository"},"content":{"rendered":"<p>I recently found the question on the Google+ forum about how to find Standard XSteps which match a certain condition. In that particular case all XSteps need to be found which have an input field with validation and the \u201aNever accept\u2018 error handling.<\/p>\n<p><!--more--><\/p>\n<p>One option would be to export the entire tree and search in the xml document for the characteristic\u00a0PPPI_ACCEPT_INVALID_INPUT and the value 02 which corresponds to the \u201aNever Accept\u2018 option (these values can also be looked up in characteristic maintenance &#8211; use either transaction code CT04 or O27C). In the xml file an entry would look like this:<\/p>\n<blockquote><p>&lt;cmx:FIELD DOMAIN=&#8221;PPPI_ACCEPT_INVALID_INPUT&#8221;&gt;&lt;cmx:VALUE&gt;02&lt;\/cmx:VALUE&gt;&lt;\/cmx:FIELD&gt;<\/p><\/blockquote>\n<p>The downside of this is that it is very hard to find the context of such a line in the xml file and the corresponding Standard XStep. Therefore the much more elegant way is simply the standard search function in the SAP GUI window:<\/p>\n<p><img loading=\"lazy\" style=\"display: block; margin-left: auto; margin-right: auto;\" title=\"NewImage.png\" src=\"http:\/\/websha.de\/xstepcafe\/wp-content\/uploads\/2014\/08\/NewImage.png\" alt=\"NewImage\" width=\"600\" height=\"98\" border=\"0\" \/><\/p>\n<p>First you select a folder or any other node in the XStep repository and then press the find button. Unlike in most other areas in the SAP system you are then presented with a very extensive search popup which contains a lot of search options. For the described search problem you need to select the tab \u201aProcess Instruct.\u2018 and then fill in the values described above which is DOMAIN=PPPI_ACCEPT_INVALID_INPUT and VALUE=02:<\/p>\n<p><img loading=\"lazy\" style=\"display: block; margin-left: auto; margin-right: auto;\" title=\"NewImage.png\" src=\"http:\/\/websha.de\/xstepcafe\/wp-content\/uploads\/2014\/08\/NewImage1.png\" alt=\"NewImage\" width=\"600\" height=\"510\" border=\"0\" \/><\/p>\n<p>After executing this search you should see the resulting processed instructions in the lower part of your screen. <del>However during my tests I did not get any results when I provided the value 02. A similar search for a numeric characteristics (e.g. DEFAULT_VALUE) or long\/short text characteristic (e.g. PPPI_FRAGMENT_HTML or PPPI_OUTPUT_TEXT) did work so I assume there might be an issue using other types of characteristics. Try it out on your system and if it does not work create a support message.<\/del><br \/>\nA search for the domain only (PPPI_ACCEPT_INVALID_INPUT) gets this result:<\/p>\n<p><img loading=\"lazy\" style=\"display: block; margin-left: auto; margin-right: auto;\" title=\"NewImage.png\" src=\"http:\/\/websha.de\/xstepcafe\/wp-content\/uploads\/2014\/08\/NewImage2.png\" alt=\"NewImage\" width=\"374\" height=\"126\" border=\"0\" \/><\/p>\n<p>You can double-click on each entry in the search result area which adjusts the main view an presents you the corresponding process instruction in the XStep repository. There you can make your necessary adjustments.<\/p>\n<p><strong>Additional Comment (September 10 2014):<\/strong><\/p>\n<p>During the September web session Sue Rochon pointed out that you can use something like &#8220;N*&#8221; in the value filed instead of &#8220;02&#8221; and this will find the instructions. Thanks Sue for the tip!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I recently found the question on the Google+ forum about how to find Standard XSteps which match a certain condition. In that particular case all XSteps need to be found which have an input field with validation and the \u201aNever accept\u2018 error handling.<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_links_to":"","_links_to_target":""},"categories":[52],"tags":[69],"_links":{"self":[{"href":"https:\/\/websha.de\/xstepcafe\/wp-json\/wp\/v2\/posts\/1664"}],"collection":[{"href":"https:\/\/websha.de\/xstepcafe\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/websha.de\/xstepcafe\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/websha.de\/xstepcafe\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/websha.de\/xstepcafe\/wp-json\/wp\/v2\/comments?post=1664"}],"version-history":[{"count":4,"href":"https:\/\/websha.de\/xstepcafe\/wp-json\/wp\/v2\/posts\/1664\/revisions"}],"predecessor-version":[{"id":1714,"href":"https:\/\/websha.de\/xstepcafe\/wp-json\/wp\/v2\/posts\/1664\/revisions\/1714"}],"wp:attachment":[{"href":"https:\/\/websha.de\/xstepcafe\/wp-json\/wp\/v2\/media?parent=1664"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/websha.de\/xstepcafe\/wp-json\/wp\/v2\/categories?post=1664"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/websha.de\/xstepcafe\/wp-json\/wp\/v2\/tags?post=1664"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}