First you should leave the original stylesheet files like they are and copy them with a new filename. If you got your sytlesheet files from the service market place then you need to remove the ‘TML_’ part of the filename.<\/p>\n
In the XSL stylesheet you will find a lot of references which uses a location like ‘SAPR3-WR-…’. You could now change these references to point to your CSS or image files but then you would need to reverse this when you want to implement your new XSL file.<\/p>\n
A better way is to rename all XSL, CSS, JS\u00a0and image files by adding the prefix ”SAPR3-WR-‘. This way the stylesheet will be able to load all your resources and you can easily upload the XSL to ERP later.<\/p>\n
The last step is to include a small coding part into your data XML file(s) between the XML start statement and the DOCUMENT tag:<\/p>\n
\n<?xml version=\"1.0\" encoding=\"utf-8\"?>\r\n<?xml-stylesheet type=\"text\/xsl\" href=\"SAPR3-WR-PMC_STY_EDEFAULTXIE6.XSL\" ?>\r\n<\/span><DOCUMENT ...<\/pre>\n<\/blockquote>\nOf course you need to specify the filename of\u00a0your XSL stylesheet in that section.<\/p>\n
Now all you have to do is double-click your XML file and look at your PI Sheet!<\/p>\n
Limitations<\/h1>\n
Of course you cannot expect that everything will work like in the real PI Sheet. Here are some things that will not work:<\/p>\n
\n- SAP text symbols that are used to specify some standard texts like ‘Phase’, ‘Table’ or ‘Instruction’.
\nIn the stylesheet these look like ‘<!– #text-007(SAPLPOC_MAIN)# –>’. You could of course change thos in the XSL manually but then again you’ll have to revert that back when you want to upload the XSL again to ERP.<\/li>\n - Dropdown lists
\nThere the entries are stored in the XML like ‘<!–#char-PPPI_FINAL_ISSUE:value(X)#–>’ . The actual value is taken during runtime from the ERP backend<\/li>\n - Buttons (function calls)<\/li>\n
- Calculations<\/li>\n<\/ul>\n
Most probably I did not catch all. But the bottom line is that you will be able to easily and quickly check how your changes in the XSL will look like.<\/p>\n","protected":false},"excerpt":{"rendered":"
Once you have decided to enhance your PI Sheet with additional functionality using XSL\/CSS you will find out that it is not so easy and quick to test your result using the ERP system itself (Downloading, uploading, maybe changing MIME types,…) It would be so much easier\u00a0to try your changes on a local filesystem and […]<\/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,72],"tags":[55,40,54],"_links":{"self":[{"href":"https:\/\/websha.de\/xstepcafe\/wp-json\/wp\/v2\/posts\/409"}],"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=409"}],"version-history":[{"count":20,"href":"https:\/\/websha.de\/xstepcafe\/wp-json\/wp\/v2\/posts\/409\/revisions"}],"predecessor-version":[{"id":878,"href":"https:\/\/websha.de\/xstepcafe\/wp-json\/wp\/v2\/posts\/409\/revisions\/878"}],"wp:attachment":[{"href":"https:\/\/websha.de\/xstepcafe\/wp-json\/wp\/v2\/media?parent=409"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/websha.de\/xstepcafe\/wp-json\/wp\/v2\/categories?post=409"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/websha.de\/xstepcafe\/wp-json\/wp\/v2\/tags?post=409"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}