Windows LiveWindows Live™
 
 
個人檔案home相片部落格清單更多 工具 說明

部落格
    2009/8/14

    Types of Info Records

    Info record Serves as a source of information for Purchasing. It contains data such as the vendor’s current price for specific material. The prices and other data stored in the info record are used as default values in documents such as PO. The info record allows buyers to quickly determine:
    • Which materials have been previously offered or supplied by a specific vendor.
    • Which vendors have offered or supplied a specific material.
    You can create purchasing info records for different procurement types as follows: Standard, Subcontracting, Pipeline, Consignment
    To create an info record, T-code: ME11. Then maintain information on a vendor and a material as master data at purchasing organization or plant level. 
     
    Standard
    A standard info record contains information for standard purchase orders. It can be created for materials and services with and without master records.
    Subcontracting
    A subcontractor info record contains ordering information for subcontract orders. For example, if you subcontract the assembly of a component, the subcontractor info record would include the vendor's (subcontractor's) price for assembling the component.
    Pipeline
    A pipeline info record contains information on a vendor's commodity that is supplied through a pipeline or pipes (oil or water) or by similar means (electricity through the mains). It contains the vendor's price for the consumption of such commodities by the buyer ("pipeline withdrawals"). You can store withdrawal/usage prices for different validity periods.
    Consignment
    A consignment info record contains information on a material that vendors keep available at their own cost on the orderer's premises. 
    It provides vendor's price for withdrawals by the orderer from consignment stock. As in the case of the pipeline info record, you can store prices for different validity periods.
    上午 11:42 | 新增回應 | 永久連結 | 發佈至您的部落格 | Working&Learning
    2009/6/22

    [Memo] credit memo&debit memo

    经常要反复去确认这两个documents,正好搜到一个解释很清楚的，记下，呵呵。
     
    [http://sap.javaeye.com/blog/145620]
    credit memo和debit memo是对企业向顾客已经交付的货物的价值进行调整的单据类型。举个例，如果您已经就所交付的货物向买主开具了100元的发票，可是由于货物质量的瑕疵，买主主张“货接受但必须削价10元”，如果您接受了这个主张，那您就得开具10元的credit memo (即实际业务中的所谓“红字发票”）。
    总之，与原始invoice的价值相比，增价用debit memo，降价用credit memo，两者都是billing document type。

    credit memo request 和debit memo request都是sales document type，其原理与一般的销售订单类型并无质的区别。
    只是，两个memo request的下游transaction都是直接参照订单创建billing document，而不需要有delivery。
    credit memo request --> credit memo, debit memo request --> debit memo，这就是它们的流程。

    同是销售单据，memo request与Standard order/return的数量的字段属性是不一样的：前者的数量，系统中的文本是target quantity，技术属性为VBAP-ZMENG；后者的数
    量，系统中的文本是order quantity，技术属性为VBEP-WMENG。二者的Processing data归结在不同的表结构中。
    账务票据，memo的数量来自于credit/memo request，invoice来自于order（当然return的后续billing是credit memo），这已经在copy control中定义清楚了，所以它们的数量同样应该归结在不同的表结构中。
    下午 04:31 | 新增回應 | 讀取回應 (1) | 永久連結 | 發佈至您的部落格 | Working&Learning
    2009/6/19

    mm 发票校验

    Invoice Variance Type: Qty--发票上的数量与收货的数量不一致; Price--发票上的价格跟收货的价格不一致； Price Qty--发票上的数量价格与收货（采购订单）数量价格不一致; Date--收发票时间与收货时间的差异；
    When GR: Goods Receipt:    借：原材料;    贷：GR/IR清算科目； When IR: Invoice Receipt:   借：GR/IR清算科目;    贷：供应商
    几个tolerance setting：

    DQ: Exceed amount: quantity variance（数量变化）
    If a goods receipt has been defined for an order item and a goods receipt has already been posted, the system multiplies the net order price by (quantity invoiced - (total quantity delivered - total quantity invoiced)).

     

    PP: Price variance（采购订单行项目价格容差）
    The system determines by how much each invoice item varies from the product of quantity invoiced * order price. It then compares the variance with the upper and lower limits defined (absolute limits and percentage limits).
    When posting a subsequent debit/credit, the system first checks if a price check has been defined for subsequent debits/credits. If so, the system calculates the difference between (value of subsequent debit/credit + value invoiced so far) / quantity invoiced so far * quantity to be debited/credited and the product of the quantity to be debited/credited * order price and compares this with the upper and lower tolerance limits (absolute limits and percentage limits).

    BD: Form small differences automatically（小额差异，自动调整）
    The system checks the balance of the invoice against the absolute upper limit defined. If the upper limit is not exceeded, the system automatically creates a posting line called Expense/Income from Small Differences, making the balance zero and allowing the system to post the document.

     

    关于移动平均价在发票差异中的差价计算，google+baidu一番，对于account movement算是清楚了些：

    下午 10:57 | 新增回應 | 永久連結 | 發佈至您的部落格 | Working&Learning