Rebalance Customer Balances Utility的使用

用户不管是打开A/R Posted Transactions Detail还是A/R Posted Transactions Summary 窗口,均显示如下一个警示:

打开Currency Codes窗口,检查decimal显示格式,均已经设为最大长度,说明与此无关。

后来,找到一个Utility,Modules >> Customer >> General >> Utilities >> Rebalance Customer Balances:

Rebalance Customer Balances

Use the Rebalance Customer Balances utility to ensure the On Order Balance and Posted Balance fields on the Customers record are correct.

NOTE: If you use an external financial system to handle Accounts Receivable (the Use External A/R System field is selected on the External Financial Interface Parameters form), this utility skips the recalculating of the posted balance.

What Happens During Rebalancing

When you click Rebalance Customers, the system does the following:

  1. Sets the On Order and Posted Balance fields for each selected customer to zero.
  2. Adds the total price (quantity ordered * price) of each ordered line/release into the On Order Balance field.

NOTE: The system includes only customer orders with a header status of "Ordered" or "Stopped."

  1. Adds the total of all open items into the Posted Balance field.
  2. Displays a message indicating the process is complete.
  3. Displays a list of all customers with balances over their credit limits. This list includes the customer number, name, on order balance, posted balance, and credit limit.

NOTE: Balances for corporate customers in the specified range also account for all of the corporate customer‘s "child" customers - even if the child customer numbers are not in the specified range. This is necessary to provide accurate balances for the corporate customer.

时间: 2024-10-24 17:29:13

Rebalance Customer Balances Utility的使用的相关文章

[Oracle AR]Territory Flexfield

You can use the Territory Flexfield for recording and customized reporting on your territory information. Territory Flexfields are also displayed in the Transaction Detail and Customer Detail reports in Receivables. Receivables provides a default str

重要Transaction Code

与客户相关  VD01 建立客户 Create customerVD02 更改客户 Change customerVD03 显示客户 Display customerVK11 创建条件 Create ConditionVK12 修改条件 Change ConditionVK13 显示条件 Display ConditionVA21 创建报价 Create QuotationVA22 更改报价 Change QuotationVA23 显示报价 Display QuotationVA01 创建销售

Understanding the Settlement Mechanism in Microsoft Dynamics AX

see more at http://blog.mohamedaamer.com/microsoft-dynamics/understanding-the-settlement-mechanism-in-microsoft-dynamics-ax/ Settlement is an accounting transaction that occurs on accounts payable, accounts receivables, and general ledger. This trans

Customer Care Accelerator演示示例

回顾CRM 4.0,微软Dynamics CRM 2011闪亮的新东西让我们忘乎所以的高兴.特别是Customer Care Accelerator (CCA),如果你正寻求一个呼叫中心的框架,但是你不知道CCA可以做什么,于是我们提供一个DemoMate演示记录工具 三种格式的示例,这是一个零售银行业务场景中,可供客户关怀加速器为微软Dynamics CRM 4.0,可用于不同的目的: Installable:示例适合分配销售团队合作, 使用他们自己的电脑让他们安装,使用. Auto-Run:

介绍Customer Care Accelerator (CCA)

几个月前,我们发布了一个CRM4.0的附属插件:Customer Care Accelerator (CCA). 自2005年以来CCA已经存在,我们这些新手在CRM的世界里, Customer Care Framework (CCF)最初是为解决大型呼叫中心的需求, 由微软开发的咨询服务.通过提供操作的改进如电话减少处理时间,改善first-call,解决利率和降低员工培训成本.通过它的各种版本,CCF & CCA已经部署在BT等大型电信公司和西班牙电信,以及许多大银行和医疗机构. CCA实际

ASP.NET Aries JSAPI 文档说明:AR.Utility

AR.Utility 文档 1:方法: 名称 说明 queryString function (key) *模拟.NET的Request对象 stringFormat function (str, args) *模拟.NET的String.Format函数,调用方式String.Format("a={0}",'a') guid 生成随机guid数 Cookie对象 名称 说明 get function (name) set function (key, value, expireday

Customer.java

package EPON; import java.util.LinkedList; import java.util.Queue; import java.util.Random; import java.io.File; import java.io.FileNotFoundException; import java.io.PrintWriter; public class Customer implements Runnable { private static final int Tm

【转载】Think as Customer 以客户为中心的测试理念

纵观各大公司的核心理念,往往都有一条类似“以客户为中心”的价值观.华为公司更是把“以客户为中心”放在其核心价值观的第一条,以显示它的重要性.从我 们入职培训开始,公司就反复强调并引导大家深入讨论,希望使这一理念深入人心.那对于我们从事软件测试的工程师来讲,如何真正践行“以客户为中心”的理 念,如何把这一理念融入日常的测试工作呢? 在回答这些问题之前先来看一个故事: 都说中国人喜欢搞运动,喜欢搞活动,老外就不这样.那是不是呢?讲述一个我经历的IBM举办的“以客户为中心(Think as Custo

Kafka 0.11版本新功能介绍 —— 空消费组延时rebalance

在0.11之前的版本中,多个consumer实例加入到一个空消费组将导致多次的rebalance,这是由于每个consumer instance启动的时间不可控,很有可能超出coordinator确定的rebalance timeout(即max.poll.interval.ms),而每次rebalance的代价又相当地大,因为很多状态都需要在rebalance前被持久化,而在rebalance后被重新初始化.曾经有个国外用户,他有100个consumer,每次rebalance的时间甚至要1个