<?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>Question Re: Data extension Form for Digitally Signed Billing Docu... in Technology Q&amp;A</title>
    <link>https://community.sap.com/t5/technology-q-a/data-extension-form-for-digitally-signed-billing-documents-portugal/qaa-p/13779468#M4839367</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;did you checked the entity BillingDocumentItem of the data model for&amp;nbsp;&lt;SPAN&gt;FDP_V3_BD_STANDARD_GLO_PT for property ReferenceSDDocument? This property contains the document number of the predecessor document of the invoice and in case the invoice was created out of an outbound delivery, the number of the delivery will be stored there. To ensure ReferenceSDDocument is an outbound delivery you can double check the property ReferenceSDDocumentCategory for value 'J' = Outbound Delivery.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 01 Aug 2024 07:41:27 GMT</pubDate>
    <dc:creator>MD33_SAP</dc:creator>
    <dc:date>2024-08-01T07:41:27Z</dc:date>
    <item>
      <title>Data extension Form for Digitally Signed Billing Documents (Portugal)</title>
      <link>https://community.sap.com/t5/technology-q-a/data-extension-form-for-digitally-signed-billing-documents-portugal/qaq-p/13703897</link>
      <description>&lt;P&gt;I need to extend the data source&amp;nbsp;FDP_V3_BD_STANDARD_GLO_PT_SRV in order to add the outbound delivery number.&lt;/P&gt;&lt;P&gt;I have already tried to use the custom fields app, I tried to find this data source in the data source extension tab but I wasn't able to find it. I then tried to create a custom field (then i would apply a custom logic to it) under the&amp;nbsp;&lt;SPAN&gt;Sales: Billing Document (SD_BILLINGDOC) business context but I was not able to find usage for the billing form templates.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Can you please help me find a way to solve this?&lt;/P&gt;&lt;P&gt;Thank you in advance&lt;/P&gt;</description>
      <pubDate>Thu, 16 May 2024 17:01:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/data-extension-form-for-digitally-signed-billing-documents-portugal/qaq-p/13703897</guid>
      <dc:creator>rubensantos</dc:creator>
      <dc:date>2024-05-16T17:01:23Z</dc:date>
    </item>
    <item>
      <title>Re: Data extension Form for Digitally Signed Billing Documents (Portugal)</title>
      <link>https://community.sap.com/t5/technology-q-a/data-extension-form-for-digitally-signed-billing-documents-portugal/qaa-p/13750857#M4835567</link>
      <description>Added Sales tag, please remove other tags.</description>
      <pubDate>Thu, 04 Jul 2024 04:54:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/data-extension-form-for-digitally-signed-billing-documents-portugal/qaa-p/13750857#M4835567</guid>
      <dc:creator>OwenLiu</dc:creator>
      <dc:date>2024-07-04T04:54:11Z</dc:date>
    </item>
    <item>
      <title>Re: Data extension Form for Digitally Signed Billing Docu...</title>
      <link>https://community.sap.com/t5/technology-q-a/data-extension-form-for-digitally-signed-billing-documents-portugal/qaa-p/13779468#M4839367</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;did you checked the entity BillingDocumentItem of the data model for&amp;nbsp;&lt;SPAN&gt;FDP_V3_BD_STANDARD_GLO_PT for property ReferenceSDDocument? This property contains the document number of the predecessor document of the invoice and in case the invoice was created out of an outbound delivery, the number of the delivery will be stored there. To ensure ReferenceSDDocument is an outbound delivery you can double check the property ReferenceSDDocumentCategory for value 'J' = Outbound Delivery.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Aug 2024 07:41:27 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/data-extension-form-for-digitally-signed-billing-documents-portugal/qaa-p/13779468#M4839367</guid>
      <dc:creator>MD33_SAP</dc:creator>
      <dc:date>2024-08-01T07:41:27Z</dc:date>
    </item>
    <item>
      <title>Re: Data extension Form for Digitally Signed Billing Docu...</title>
      <link>https://community.sap.com/t5/technology-q-a/data-extension-form-for-digitally-signed-billing-documents-portugal/qaa-p/13959385#M4895564</link>
      <description>&lt;P&gt;Did you find a solution to this? I need to update the invoice with 3 extra fields that are not available in the Data Model&amp;nbsp;&lt;SPAN&gt;FDP_V3_BD_STANDARD_GLO_PT.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 09 Dec 2024 18:56:41 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/data-extension-form-for-digitally-signed-billing-documents-portugal/qaa-p/13959385#M4895564</guid>
      <dc:creator>CarlosMoreira</dc:creator>
      <dc:date>2024-12-09T18:56:41Z</dc:date>
    </item>
    <item>
      <title>Re: Data extension Form for Digitally Signed Billing Docu...</title>
      <link>https://community.sap.com/t5/technology-q-a/data-extension-form-for-digitally-signed-billing-documents-portugal/qaa-p/13960046#M4895654</link>
      <description>Hi, did you already checked our business documentation: &lt;A href="https://help.sap.com/docs/SAP_S4HANA_CLOUD/a376cd9ea00d476b96f18dea1247e6a5/688e84d13bce41808aed7af255924a94.html?locale=en-US&amp;amp;version=2408.500" target="_blank"&gt;https://help.sap.com/docs/SAP_S4HANA_CLOUD/a376cd9ea00d476b96f18dea1247e6a5/688e84d13bce41808aed7af255924a94.html?locale=en-US&amp;amp;version=2408.500&lt;/A&gt;</description>
      <pubDate>Tue, 10 Dec 2024 12:15:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/data-extension-form-for-digitally-signed-billing-documents-portugal/qaa-p/13960046#M4895654</guid>
      <dc:creator>MD33_SAP</dc:creator>
      <dc:date>2024-12-10T12:15:39Z</dc:date>
    </item>
  </channel>
</rss>

