<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Updating printer device attributes using RFC in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/updating-printer-device-attributes-using-rfc/m-p/7885802#M1595292</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sood,&lt;/P&gt;&lt;P&gt;   I hope you are doing an implementation in the customer namespcae . In this case , you could create your own function modules in the Z* namespace and make them RFC enabled and internally call the specified FMs.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Anzy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 12 May 2011 10:56:44 GMT</pubDate>
    <dc:creator>mohammed_anzys</dc:creator>
    <dc:date>2011-05-12T10:56:44Z</dc:date>
    <item>
      <title>Updating printer device attributes using RFC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/updating-printer-device-attributes-using-rfc/m-p/7885801#M1595291</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm a new entrant to the SAP world and still finding my feet. I think the term newbie can be applied freely. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My pilot involves using the NW RFC libraries to update printer attributes. So far I think &lt;STRONG&gt;RSPO_&lt;/STRONG&gt; functions seem to be the appropriate choice for dealing with printing. I can get the list of printers by using either &lt;STRONG&gt;ADS_GET_PRINTER_LIST&lt;/STRONG&gt; or &lt;STRONG&gt;RSPO_ADM_DEVICES_GET&lt;/STRONG&gt;. They both seem to return the same data, though the ADS version has far more detail. I've discovered these APIs mainly by trial/error and searching the forums/google/...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However I cannot seem to find the functions for &lt;EM&gt;updating&lt;/EM&gt; the attributes. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;RSPO_DEVICE_UPDATE&lt;/STRONG&gt; and &lt;STRONG&gt;RSPO_ADM_DEVICE_UPDATE&lt;/STRONG&gt; looked promising, but they cannot be called remotely.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My questions/doubts:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Is what I'm trying to do possible and supported?&lt;/P&gt;&lt;P&gt;2. Are RSPO_ family the correct functions for dealing with device updates, or is there another set of functions?&lt;/P&gt;&lt;P&gt;3. If the DEVICE_UPDATE is indeed the correct function, what are the workarounds for accessing it remotely; so far I can think of using a think ABAP wrapper which is exposed remotely, using the web services SOAP call.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've been trying to find the canonical reference documentation for dealing with printers at an API level, but with no success. Any pointers to docs/references would be much appreciated!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I understand these are very entry level questions, and do beg everyones' pardon. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 May 2011 16:52:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/updating-printer-device-attributes-using-rfc/m-p/7885801#M1595291</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-05-11T16:52:11Z</dc:date>
    </item>
    <item>
      <title>Re: Updating printer device attributes using RFC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/updating-printer-device-attributes-using-rfc/m-p/7885802#M1595292</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sood,&lt;/P&gt;&lt;P&gt;   I hope you are doing an implementation in the customer namespcae . In this case , you could create your own function modules in the Z* namespace and make them RFC enabled and internally call the specified FMs.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Anzy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 12 May 2011 10:56:44 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/updating-printer-device-attributes-using-rfc/m-p/7885802#M1595292</guid>
      <dc:creator>mohammed_anzys</dc:creator>
      <dc:date>2011-05-12T10:56:44Z</dc:date>
    </item>
    <item>
      <title>Re: Updating printer device attributes using RFC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/updating-printer-device-attributes-using-rfc/m-p/7885803#M1595293</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;There seem to be couple of RFCs in this direction. You would have to try testing it :&lt;/P&gt;&lt;P&gt;RSPO_SXOMS_I_UPDATE_PRINTER - Assuming that you want to update printer as in device.And SPCPC_I_BUILD_DEVICE. Although the later didn't talk about update, there is delete and insert type of RFCs in the respective funtion group.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As a thumb rule, you should always try to utilize the available RFCs or BAPIs for your function, updating a table by writing z-RFC could always be risky for a customer anyway.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Additionally If your intention is print the jobs remotely (refer to SP01 transaction that does priniting based on the jobs) , then the related remote APIs are part of funtion group SPRR.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Priti&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 12 May 2011 14:56:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/updating-printer-device-attributes-using-rfc/m-p/7885803#M1595293</guid>
      <dc:creator>Priti_PM</dc:creator>
      <dc:date>2011-05-12T14:56:11Z</dc:date>
    </item>
    <item>
      <title>Re: Updating printer device attributes using RFC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/updating-printer-device-attributes-using-rfc/m-p/7885804#M1595294</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you Anzy and Priti, we're much further ahead now due to your help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Priti, we do want to update the output device attributes. Specifically device type and driver. I cannot find RSPO_SXOMS_I_UPDATE_PRINTER function defined in the customer SAP test instance. I'll post the exact version numbers and configuration tomorrow, once I again have access to the server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anzy, I've started writing a Z_ wrapper over RSPO_ADM_DEVICE_UPDATE for the time being. Thanks for the pointer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It seems that all the RSPO_ RFCs are view and read only. The update/create APIs are non-remote. I wanted to find the design/security documentation for understanding these decisions. Does SAP documentation have a technical/security architecture overview? Or perhaps a specific forum?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once again, thank you both from me and the Idea Device engineers.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 12 May 2011 19:43:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/updating-printer-device-attributes-using-rfc/m-p/7885804#M1595294</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-05-12T19:43:20Z</dc:date>
    </item>
  </channel>
</rss>

