<?xml version="1.0" encoding="UTF-8"?>        <rss version="2.0"
             xmlns:atom="http://www.w3.org/2005/Atom"
             xmlns:dc="http://purl.org/dc/elements/1.1/"
             xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
             xmlns:admin="http://webns.net/mvcb/"
             xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
             xmlns:content="http://purl.org/rss/1.0/modules/content/">
        <channel>
            <title>
									Financials - Nội dung diễn đàn				            </title>
            <link>https://forum.sapb1.vn/community/financials/</link>
            <description>Chuyên trang về hệ thống ERP SAP Business One</description>
            <language>en-US</language>
            <lastBuildDate>Sun, 22 Nov 2026 22:53:43 +0000</lastBuildDate>
            <generator>wpForo</generator>
            <ttl>60</ttl>
							                    <item>
                        <title>3349699 - New Posting Period Cannot Be Created or Existing Posting Period Cannot Be Changed or Removed</title>
                        <link>https://forum.sapb1.vn/community/financials/3349699-new-posting-period-cannot-be-created-or-existing-posting-period-cannot-be-changed-or-removed/</link>
                        <pubDate>Fri, 26 Dec 2025 23:41:37 +0000</pubDate>
                        <description><![CDATA[Symptom
You find that at least one of the following actions cannot be performed in the database:


Creating a new posting period
Making changes to an existing posting period
Removing a...]]></description>
                        <content:encoded><![CDATA[<h3 id="Symptom" class="section" data-toc-skip="">Symptom</h3>
<p id="__html26">You find that at least one of the following actions cannot be performed in the database:</p>
<div class="longtext">
<ul>
<li>Creating a new posting period</li>
<li>Making changes to an existing posting period</li>
<li>Removing an existing posting period</li>
</ul>
</div>
<p><strong>Scenario:</strong></p>
<p>You are adding, updating or removing a posting period.</p>
<p><strong>Expected behavior:</strong></p>
<p>Operation is completed successfully.</p>
<p><strong>Actual behavior:</strong></p>
<p>You receive one or more error messages similar to these:</p>
<ul>
<li><em>You cannot remove this item; its transactions are linked to an object '20XX-XX' </em></li>
<li><em>Field cannot be updated (ODBC – 1029) </em></li>
<li><em>This entry already exists in the following tables 'Posting Period' (OFPR) (ODBC-2035) </em></li>
</ul>
<h3 id="Cause" class="section" data-toc-skip="">Cause</h3>
<p>This is correct system behavior. SAP Business One does not allow creating a new period if the posting date range defined in Administration → System Initialization → Posting Periods overlaps with the posting date range of a previous period for which you entered transactions.</p>
<p>Reasoning:</p>
<ol>
<li>When you create a new posting period in Administration → System Initialization → Posting Periods → New Period, the system fills in the default values in the <em>Posting Date From</em> and<em> Posting Date To</em> fields for all the periods and sub-periods according to the calendar year, that is, from 01/01/20xx to 31/12/20xx.</li>
<li>Before you post any document in the period/sub-period, the <em>Posting Date From</em> and <em>Posting Date </em><em>To</em> fields are editable. To accommodate the posting periods to the requirements of various country/regions and business practices, the fiscal year can start, for example, in March rather than in January.</li>
<li>When editing the <em>Posting Date From</em> and <em>Posting Date T</em><em>o</em> of the posting period or sub-period, be aware that:
<ol>
<li>All documents you post up to the <em>Posting Date To</em> value will be included in the period-end closing, financial, accounting and tax reports of the posting period.</li>
<li>You cannot create a new posting period with a start posting date before an existing period.</li>
</ol>
</li>
</ol>
<h3 id="Resolution" class="section" data-toc-skip="">Resolution</h3>
<p>If you created a posting period incorrectly and already added postings, your only option is to apply the following solution:</p>
<ol>
<li>Restore a backup of the database that does not contain any document with posting date after the start date of the new posting period that you want to create.</li>
<li>Set back the <em>Posting Date From</em> and<span> </span><em>Posting Date To</em> values to the correct or natural values and create the new posting period.</li>
<li>Import all the documents with posting date after the start date mentioned in step 1.</li>
</ol>
<p><strong>Note:</strong> If documents exist for periods that are in between the target period (period you want to create) and the original period (existing one), then SAP Business One will not allow the creation of the target period. For example, there are no transactions in the target posting period (April 2017) or in the original posting period (April 2016); however, the system will verify if there are transactions between May 2016 and March 2017. If there are such transactions, the system will not allow the creation of the target posting period.</p>
<p>If the period to be added is, actually, not listed in the <em>Posting Periods</em> window (in the OFPR table), all the existing periods for the previous years look correct, and the error you receive is the following:</p>
<p><em>This entry already exists in the following tables 'Posting Period' (OFPR) (ODBC-2035) </em></p>
<p>Then the situation is most likely caused by unsupported customizations and you should proceed as follows:</p>
<ol>
<li>Test the solution first in a copy of the database.</li>
<li>Remove all customizations as per SAP Note <a class="sapMLnk sapMLnkWrapping sapMLnkMaxWidth" href="https://me.sap.com/notes/2079411" target="_blank" rel="noopener">2079411</a>.</li>
<li>Go to Help → Support Desk → Restore → Restore Numbering File and choose <em>Yes</em> to the system message <em>Restore Numbering File?</em></li>
<li>When applying the solution in the productive database, ensure that all the users have logged off the database and that you have taken a full backup.</li>
</ol>
<p><strong>Recommendation:</strong></p>
<p>We recommend that the system administrator restricts full access to the setup of posting periods. You can control access under Administration → System Initialization → General Authorizations.</p>]]></content:encoded>
						                            <category domain="https://forum.sapb1.vn/community/financials/">Financials</category>                        <dc:creator>admin</dc:creator>
                        <guid isPermaLink="true">https://forum.sapb1.vn/community/financials/3349699-new-posting-period-cannot-be-created-or-existing-posting-period-cannot-be-changed-or-removed/</guid>
                    </item>
				                    <item>
                        <title>3040377 - Troubleshooting - Advanced G/L Account Determination</title>
                        <link>https://forum.sapb1.vn/community/financials/3040377-troubleshooting-advanced-g-l-account-determination/</link>
                        <pubDate>Sun, 25 May 2025 14:45:56 +0000</pubDate>
                        <description><![CDATA[Symptom
You may encounter issues related to the Advanced G/L Account Determination function under Administration → System Initialization → Company Details → Basic Initialization tab.
Solut...]]></description>
                        <content:encoded><![CDATA[<p><strong>Symptom</strong></p>
<p>You may encounter issues related to the Advanced G/L Account Determination function under <em>Administration → System Initialization → Company Details → Basic Initialization</em> tab.</p>
<p><strong>Solution</strong></p>
<p><strong>Consider the following information when dealing with an issue related to <em>Advanced G/L Account Determination</em> in SAP Business One:</strong></p>
<p>If you are working in a company database where the<em> Enable Advanced G/L Account Determination </em>option is not selected, then the scenarios described in this SAP Note may not be suitable for you.</p>
<p><strong>Prerequisites:</strong></p>
<p><strong>Consider and verify all of the following information when dealing with an issue related to <em>Advanced G/L Account Determination </em>in SAP Business One:</strong></p>
<ol>
<li>Conduct all testing in a test database obtained from the productive environment.</li>
<li>Obtain the approval from the company's accountant before defining or updating any information in the productive environment.</li>
<li>Check whether there is any of the following defined/present, which might have an impact, especially in case of <u>seemingly</u> <strong>"random" issues</strong>:
<ul>
<li><strong>User-Defined Fields</strong> (UDF) and <strong>Formatted searches</strong> (FMS) in SAP Business One or modifications in the <strong>Transaction Notification</strong> code of the database, which are a common root cause of unexpected behavior (with or without any error displayed), and the latter of which is out of our support scope. Consult SAP Note <strong><a href="https://me.sap.com/notes/2079411">2079411</a></strong> for the details to be verified and on how to remove them.</li>
<li><strong>Data Ownership</strong> for any of the relevant non-superusers. To rule out its impact, from the SAP Business One <em>Main Menu</em>, choose <em>Administration</em> → <em>System Initialization</em> → <em>General Settings</em>, and on the <em>BP</em> tab, deselect the <em>Enable Data Ownership</em> checkbox for the non-superusers. Note that this setting is not relevant for superusers. Check the defined G/L accounts in <em>Administration </em>→ <em>Setup</em> → <em>General</em> → <em>User Defaults</em>.</li>
</ul>
</li>
<li>Test if the issue is present when using professional user license with full authorizations.</li>
<li>For further information, refer to the referenced SAP Notes.</li>
<li>Contact SAP Business One Support regarding database inconsistencies that are not perfectly resolved after having followed the instructions provided in this SAP Note.</li>
</ol>
<p><strong>Ensure that you provide the following information when submitting a support incident regarding <em>Advanced G/L Account Determination</em>:</strong></p>
<ol>
<li>The SAP Business One version, localization, and patch level or feature package in which the issue has occurred.</li>
<li>If the issue is reproducible in a standard SAP Business One demo database.
<ul>
<li>Check whether the same issue can be reproduced by adding the document anew in the latest patch of the current version.</li>
<li>In your testing, try to rule out the impact of UDF's, as mentioned in the previous section. If they do seem to have an impact, first consult all the dedicated sections of this SAP Note.</li>
</ul>
</li>
<li>A screenshot of a sample marketing document with the unexpected G/L account and its journal entry, the error message displayed (if any), and all the details that may be necessary to define the advanced rule (such as item group, item code, warehouse code, business partner (BP) group, BP code, BP type, ship-to country/region, UDF fields in use etc. that are relevant as per advanced criteria).</li>
<li>Details of the steps needed to reproduce the issue, including screenshots of the following setup windows, whichever are relevant:
<ul>
<li><em>Administration → Setup → Financials → G/L Account Determination → G/L Account Determination → Sales/Purchasing/General/Inventory</em> tab and the <em>General/Tax</em> subtab for the relevant <em>Period Selection</em> where the relevant G/L accounts can be seen.</li>
<li><em>Administration → Setup → Financials → G/L Account Determination → Advanced</em> button for the relevant <em>Period</em> where the rules settings can be seen: all advanced criteria and G/L accounts.</li>
<li><em>Item Master Data → General tab → Advanced Rule Type</em> setting for the involved item(s).</li>
</ul>
</li>
<li>Details of the Expected and the Actual results/behavior.</li>
<li>Results of any query that might have been run.</li>
</ol>
<p>For detail: <a href="https://me.sap.com/notes/3040377#If2_R2">3040377 - Troubleshooting - Advanced G/L Account Determination - SAP for Me</a></p>]]></content:encoded>
						                            <category domain="https://forum.sapb1.vn/community/financials/">Financials</category>                        <dc:creator>admin</dc:creator>
                        <guid isPermaLink="true">https://forum.sapb1.vn/community/financials/3040377-troubleshooting-advanced-g-l-account-determination/</guid>
                    </item>
				                    <item>
                        <title>Old Memo Text Appearing on Top of All Journal Entries - SAP B1 Bug?</title>
                        <link>https://forum.sapb1.vn/community/financials/old-memo-text-appearing-on-top-of-all-journal-entries-sap-b1-bug/</link>
                        <pubDate>Thu, 24 Apr 2025 15:28:25 +0000</pubDate>
                        <description><![CDATA[Hi experts, 
I&#039;m experiencing a strange issue in SAP Business One.In journal entries, a specific memo line from a previous entry (for example: ZİRAAT 15002 NOLU YATIRIM KREDISI 49/108 TKST ...]]></description>
                        <content:encoded><![CDATA[<p>Hi experts, </p>
<p class=""><strong>I'm experiencing a strange issue in SAP Business One.</strong><br />In journal entries, a specific memo line from a previous entry (for example:<span> </span><em>ZİRAAT 15002 NOLU YATIRIM KREDISI 49/108 TKST ÖDEMESİ</em>) appears<span> </span><strong>above</strong><span> </span>the actual memo of the current journal entry (for example:<span> </span><em>ZİRAAT 15002 NOLU YATIRIM KREDISI 56/108 TKST ÖDEMESİ</em>), and this happens in<span> </span><strong>every</strong><span> </span>journal entry.<br />Even though the actual memo for each entry is correct, this old memo is constantly displayed at the top of the screen for every journal entry.</p>
<p class="">It seems like some kind of system bug.<br />How can I fix this?<br />For example;</p>
237
<p class=""> </p>]]></content:encoded>
						                            <category domain="https://forum.sapb1.vn/community/financials/">Financials</category>                        <dc:creator>Yusuf</dc:creator>
                        <guid isPermaLink="true">https://forum.sapb1.vn/community/financials/old-memo-text-appearing-on-top-of-all-journal-entries-sap-b1-bug/</guid>
                    </item>
				                    <item>
                        <title>Payment Term Enhancement - cải tiến chức năng tính toán Due Date</title>
                        <link>https://forum.sapb1.vn/community/financials/payment-term-enhancement-cai-tien-chuc-nang-tinh-toan-due-date/</link>
                        <pubDate>Thu, 06 Mar 2025 02:26:35 +0000</pubDate>
                        <description><![CDATA[Kể từ phiên bản SAP B1 version 10 FP 2502, SAP đã nâng cấp chức năng tính toán cho ngày đến hạn (Due Date).
Cải tiến này bổ sung thêm trường End On cho các trường Start From, Month và Days ...]]></description>
                        <content:encoded><![CDATA[<p>Kể từ phiên bản SAP B1 version 10 FP 2502, SAP đã nâng cấp chức năng tính toán cho ngày đến hạn (Due Date).</p>
<p>Cải tiến này bổ sung thêm trường <strong>End On</strong> cho các trường <strong><span class="ph uicontrol">Start From</span></strong>,<span> </span><strong><span class="ph uicontrol">Month</span></strong><span> và</span><span> </span><strong><span class="ph uicontrol">Days</span></strong> hiện có, các trường này sẽ tiếp tục hoạt động như hiện tại. Bạn có thể sử dụng một số hoặc tất cả các trường cùng nhau để tính toán cho ngày đến hạn (Due Date)</p>
201
<p><br /><br /></p>]]></content:encoded>
						                            <category domain="https://forum.sapb1.vn/community/financials/">Financials</category>                        <dc:creator>admin</dc:creator>
                        <guid isPermaLink="true">https://forum.sapb1.vn/community/financials/payment-term-enhancement-cai-tien-chuc-nang-tinh-toan-due-date/</guid>
                    </item>
				                    <item>
                        <title>Hướng dẫn hủy giải trừ (Cancel Reconciliation)</title>
                        <link>https://forum.sapb1.vn/community/financials/huong-dan-huy-giai-tru-cancel-reconciliation/</link>
                        <pubDate>Wed, 25 Sep 2024 00:42:51 +0000</pubDate>
                        <description><![CDATA[Khi phát hiện sai sót trong quá trình giải trừ, người dùng có thể hủy kết quả giải trừ và tiến hành lại.
Lưu ý: thao tác hủy chỉ có hiệu lực đối với loại giải trừ Manual. Trường hợp giải tr...]]></description>
                        <content:encoded><![CDATA[<p>Khi phát hiện sai sót trong quá trình giải trừ, người dùng có thể hủy kết quả giải trừ và tiến hành lại.</p>
<p>Lưu ý: thao tác hủy chỉ có hiệu lực đối với loại giải trừ Manual. Trường hợp giải trừ thuộc loại Payment thì người dùng phải thực hiện hủy ở chứng từ Payment.</p>
<p>Xem video hướng dẫn cách hủy giải trừ</p>
<p>https://youtu.be/bDGLl4-dVgE</p>]]></content:encoded>
						                            <category domain="https://forum.sapb1.vn/community/financials/">Financials</category>                        <dc:creator>admin</dc:creator>
                        <guid isPermaLink="true">https://forum.sapb1.vn/community/financials/huong-dan-huy-giai-tru-cancel-reconciliation/</guid>
                    </item>
				                    <item>
                        <title>Hướng dẫn giải trừ tạm ứng kèm thu hồi tiền thừa (Advance Payment Settlement)</title>
                        <link>https://forum.sapb1.vn/community/financials/huong-dan-giai-tru-tam-ung-kem-thu-hoi-tien-thua-advance-payment-settlement/</link>
                        <pubDate>Tue, 24 Sep 2024 01:14:24 +0000</pubDate>
                        <description><![CDATA[Quyết toán tạm ứng là bước reconcile giữa phần tạm ứng và các hóa đơn có liên quan. Phần chênh lệch sẽ được thu lại/chi thêm.
Xem hướng dẫn cho trường hợp thu lại tiền tạm ứng còn thừa.]]></description>
                        <content:encoded><![CDATA[<p>Quyết toán tạm ứng là bước reconcile giữa phần tạm ứng và các hóa đơn có liên quan. Phần chênh lệch sẽ được thu lại/chi thêm.</p>
<p>Xem hướng dẫn cho trường hợp thu lại tiền tạm ứng còn thừa.</p>
<p>https://youtu.be/szd_Twu18Fw</p>]]></content:encoded>
						                            <category domain="https://forum.sapb1.vn/community/financials/">Financials</category>                        <dc:creator>admin</dc:creator>
                        <guid isPermaLink="true">https://forum.sapb1.vn/community/financials/huong-dan-giai-tru-tam-ung-kem-thu-hoi-tien-thua-advance-payment-settlement/</guid>
                    </item>
				                    <item>
                        <title>Hướng dẫn giải trừ công nợ cho nhiều đối tác (Multiple Business Partner Reconciliation)</title>
                        <link>https://forum.sapb1.vn/community/financials/huong-dan-giai-tru-cong-no-cho-nhieu-doi-tac-multiple-business-partner-reconciliation/</link>
                        <pubDate>Mon, 23 Sep 2024 03:34:55 +0000</pubDate>
                        <description><![CDATA[Tình huống cần giải trừ:các hóa đơn của đối tác vừa là khách hàng (Customer) vừa là nhà cung cấp (Vendor)
Xem video hướng dẫn cách giải trừ]]></description>
                        <content:encoded><![CDATA[<p>Tình huống cần giải trừ:các hóa đơn của đối tác vừa là khách hàng (Customer) vừa là nhà cung cấp (Vendor)</p>
<p>Xem video hướng dẫn cách giải trừ</p>
<p>https://youtu.be/A4vOe8mkmrw</p>]]></content:encoded>
						                            <category domain="https://forum.sapb1.vn/community/financials/">Financials</category>                        <dc:creator>admin</dc:creator>
                        <guid isPermaLink="true">https://forum.sapb1.vn/community/financials/huong-dan-giai-tru-cong-no-cho-nhieu-doi-tac-multiple-business-partner-reconciliation/</guid>
                    </item>
				                    <item>
                        <title>Hướng dẫn giải trừ công nợ đối tác (Business Partner Internal Reconciliation)</title>
                        <link>https://forum.sapb1.vn/community/financials/huong-dan-giai-tru-cong-no-doi-tac-business-partner-internal-reconciliation/</link>
                        <pubDate>Sat, 21 Sep 2024 03:25:12 +0000</pubDate>
                        <description><![CDATA[Giải trừ công nợ là phần việc quan trọng của kế toán trong việc xác định chính xác khách hàng (Customer) nợ mình ở những hóa đơn cụ thể nào hoặc mình nợ nhà cung cấp (vendor) liên quan đến h...]]></description>
                        <content:encoded><![CDATA[<p>Giải trừ công nợ là phần việc quan trọng của kế toán trong việc xác định chính xác khách hàng (Customer) nợ mình ở những hóa đơn cụ thể nào hoặc mình nợ nhà cung cấp (vendor) liên quan đến hóa đơn nào.</p>
<p>Không những vậy, việc giải trừ giúp còn giúp theo dõi các khoản nợ trên báo cáo tuổi nợ (Aging report) trở nên dễ dàng và thuận lợi hơn.</p>
<p>Chi tiết thao tác thực hiện giải trừ công nợ</p>
<p>https://youtu.be/DMtayNSlHyc</p>]]></content:encoded>
						                            <category domain="https://forum.sapb1.vn/community/financials/">Financials</category>                        <dc:creator>admin</dc:creator>
                        <guid isPermaLink="true">https://forum.sapb1.vn/community/financials/huong-dan-giai-tru-cong-no-doi-tac-business-partner-internal-reconciliation/</guid>
                    </item>
				                    <item>
                        <title>Hướng dẫn kết chuyển năm tài chính cho TSCĐ (Fiscal Year Change)</title>
                        <link>https://forum.sapb1.vn/community/financials/huong-dan-ket-chuyen-nam-tai-chinh-cho-tscd-fiscal-year-change/</link>
                        <pubDate>Thu, 19 Sep 2024 03:58:58 +0000</pubDate>
                        <description><![CDATA[Sau khi đã hoàn thành kết chuyển và khóa sổ năm tài chính cho các tài khoản kế toán, cần thao tác để kết chuyển đối với TSCĐ (Fixed Asset), người dùng sử dụng chức năng Fiscal Year Change.
...]]></description>
                        <content:encoded><![CDATA[<p>Sau khi đã hoàn thành kết chuyển và khóa sổ năm tài chính cho các tài khoản kế toán, cần thao tác để kết chuyển đối với TSCĐ (Fixed Asset), người dùng sử dụng chức năng Fiscal Year Change.</p>
<p>Tham khảo Video hướng dẫn</p>
<p>https://youtu.be/XjxFRjWsxig</p>]]></content:encoded>
						                            <category domain="https://forum.sapb1.vn/community/financials/">Financials</category>                        <dc:creator>admin</dc:creator>
                        <guid isPermaLink="true">https://forum.sapb1.vn/community/financials/huong-dan-ket-chuyen-nam-tai-chinh-cho-tscd-fiscal-year-change/</guid>
                    </item>
				                    <item>
                        <title>Hướng dẫn chạy khấu hao hàng tháng (Depreciation Run)</title>
                        <link>https://forum.sapb1.vn/community/financials/huong-dan-chay-khau-hao-hang-thang-depreciation-run/</link>
                        <pubDate>Wed, 18 Sep 2024 03:25:50 +0000</pubDate>
                        <description><![CDATA[Khấu hao hàng tháng phụ thuộc vào nguyên giá (Acquisition and Production Cost, APC), thời gian khấu hao (Useful Life), loại khấu hao (Depreciation Type). 
Xem thêm Video hướng dẫn]]></description>
                        <content:encoded><![CDATA[<p>Khấu hao hàng tháng phụ thuộc vào nguyên giá (Acquisition and Production Cost, APC), thời gian khấu hao (Useful Life), loại khấu hao (Depreciation Type). </p>
<p>Xem thêm Video hướng dẫn</p>
<p>https://youtu.be/kz96LmnQ4Io</p>]]></content:encoded>
						                            <category domain="https://forum.sapb1.vn/community/financials/">Financials</category>                        <dc:creator>admin</dc:creator>
                        <guid isPermaLink="true">https://forum.sapb1.vn/community/financials/huong-dan-chay-khau-hao-hang-thang-depreciation-run/</guid>
                    </item>
							        </channel>
        </rss>
		