<?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: BOPF Problem inside  associations/determinations in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/bopf-problem-inside-associations-determinations/m-p/12454768#M1999842</link>
    <description>&lt;P&gt;Hi Matthias,&lt;/P&gt;&lt;P&gt;transient data is filled by determinations. BOPF usually runs determinations only at the end of a service manager call. You can enforce the execution of pending determinations by executing `io_modify-&amp;gt;end_modify(… iv_process_immediately = abap_true …)`. I guess you are talking about an implementation of `/bobf/if_frw_association~resolve`. In this case, you are in bad luck because the signature of this method does not offer the io_modify parameter. Therefore, using the service manager is a valid solution for you.&lt;/P&gt;&lt;P&gt;On the other hand, we are talking about BO-internal logic, both for the transient fields, and for the association. So, you could consider directly calling the code which fills the transient fields from within your implemented association, without violating "information hiding" principles or "separation of concerns".&lt;/P&gt;&lt;P&gt;Kind Regards,&lt;/P&gt;</description>
    <pubDate>Wed, 28 Jul 2021 14:02:39 GMT</pubDate>
    <dc:creator>ivo_vollrath</dc:creator>
    <dc:date>2021-07-28T14:02:39Z</dc:date>
    <item>
      <title>BOPF Problem inside  associations/determinations</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bopf-problem-inside-associations-determinations/m-p/12454767#M1999841</link>
      <description>&lt;P&gt;Situation:&lt;/P&gt;
  &lt;P&gt;Inside the determination of a subnode instance B1 of node A1 the data of another instance A2 is retrieved. In this retrieve the transient data of instance A2 is missing if it is retrieved by io_read. If it is retrieved by an new service manager the transient data of A2 is ok -&amp;gt; see image.&lt;/P&gt;
  &lt;P&gt;Question&lt;/P&gt;
  &lt;P&gt;- why is this happening&lt;/P&gt;
  &lt;P&gt;- what are the consequences of using another service manager inside the service manager ?&lt;/P&gt;
  &lt;P&gt;- what is the correct way of doing this&lt;/P&gt;
  &lt;P&gt;Thanks Matthias&lt;/P&gt;
  &lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/1952742-bopf-problem.jpg" /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 13 Jul 2021 11:28:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bopf-problem-inside-associations-determinations/m-p/12454767#M1999841</guid>
      <dc:creator>matthias_flury</dc:creator>
      <dc:date>2021-07-13T11:28:10Z</dc:date>
    </item>
    <item>
      <title>Re: BOPF Problem inside  associations/determinations</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bopf-problem-inside-associations-determinations/m-p/12454768#M1999842</link>
      <description>&lt;P&gt;Hi Matthias,&lt;/P&gt;&lt;P&gt;transient data is filled by determinations. BOPF usually runs determinations only at the end of a service manager call. You can enforce the execution of pending determinations by executing `io_modify-&amp;gt;end_modify(… iv_process_immediately = abap_true …)`. I guess you are talking about an implementation of `/bobf/if_frw_association~resolve`. In this case, you are in bad luck because the signature of this method does not offer the io_modify parameter. Therefore, using the service manager is a valid solution for you.&lt;/P&gt;&lt;P&gt;On the other hand, we are talking about BO-internal logic, both for the transient fields, and for the association. So, you could consider directly calling the code which fills the transient fields from within your implemented association, without violating "information hiding" principles or "separation of concerns".&lt;/P&gt;&lt;P&gt;Kind Regards,&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jul 2021 14:02:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bopf-problem-inside-associations-determinations/m-p/12454768#M1999842</guid>
      <dc:creator>ivo_vollrath</dc:creator>
      <dc:date>2021-07-28T14:02:39Z</dc:date>
    </item>
  </channel>
</rss>

