博客园_SAP & ASP.NET

Condition Types

2012-05-17T07:27:00Z

图二-[1]:表示PB00的获取是按一定的顺序策略从相应的条件表中取得维护的条件记录.Access sequence比较复杂，它能决定什么时候Condition 会出现。可以仔细对比下PB00和PBXX，前者会在建立P-info点Condition设置（其它Condition Type如果设置这个东东也能达到这种效果）；后者不会。

图二-[2]:表示PB00是价格条件类,表示是基于什么计算的.（例：如果你的价格是基于重量的,物料基本数据是PC,你选D,如果你这样做可能在开K类PO时会有点小问题,你可能需要重写requirement）

图二-[3][8]:如果你看Condt. Type: FRA1(FRA2)-FRC1(FRC2),这块是B,表示delivery cost,同时和图二-[8]应计连在一起(选上)表示该condition是运输费类条件类型,并且需要设置Account key(会计科目OBYC->你定义或SAP已存在之T/E Key).

你根据实际需求参考copy出所需要的delivery cost或其它类condition,如果需要在PO能default带出,你可能需要建立条件表和自定义的存取顺序,你还可决定是否需要为该condition建立对应会计科目(通常是应计类科目,请看定义T/E Key).

*如果你使用B类delivery cost condition在计税方案未设置account key在PO中会有错误

提示. 同时在MIRO时你可专门对planned delivery cost进行发票校验.

图二-[5]:设置Condt. Type 的输入方式（如PB00采购价格condition的Manual entries设成D不能手工输入,同时在PO屏幕设置将item的price也设置成display,这样采购价格就只能从info Record带出）

图二-[7]:item级的condition,同时允许你在PO item的condition list删除它,不勾就表示不可删除.通常采购价格condition比如PB00在计价方案会设置是强制必输.

图二-[8][9]:表示PB00是采用数量类等级价格,比如vendor规定1-100个某料1.00USD/PC,101-500个0.95 USD/PC诸如此类的等级价格,另外一个比较实际的例子是采用日期型的等级价格,不同的时间(可是周月旬)给你不同的价格,如果需要你可以自定义等级价格的公式.

你可以从表 KONM中读到这些数据,关于condition table关系请看接下来的实例.

图二-[10]:SAP的帮助举了一个实例,物料A,B同属一个material group 01,Material A 100个,Material B 150个,假设vendor给定1个1%折扣,100个开始给2%折扣这样一个价格等级,A+B =250个,享受2%折扣,如果它不work,不要紧,后面不是有个Groupcond routine吗?

图二-[11]:你可使用Rererence condition type,在SD定价中设置了ZPR1的reference condition type是ZPR0,这样VK11只要维护ZPR0就行,K,跳到SD干啥呢?我的意思MM定价和SD定价原理基本完全大概都一样.

图9-[12]: PricingProc：定义对于condition type是main condition的(一般用于PB00)，有哪些supplementary condition可以用，这也是定义在一个calculation schema中的如果有必要。例如你可以将折扣附加费海关运费和PB00使用同一个附加计价方案,SAP default的RM0002,这样在维护PB00时,你可同时在此维护这些condition,如图10,FRA(B)1-FRA(B)3是无access sequence的,这样做的好处是这些condition不用使用access sequence而在开PO时间也能自动随PB00带出(捆绑在一起同一info record number嘛).

非常遗憾的是,这样做可能不到好,因为info record的PB00通常是针对某物料某vendor某pur.

Org而且某plant的,而通常运输费海关费是只根据国家代码运输Route制定计划价格,所以通

常还是建立access sequence然后MEK1维护计划价格

本文链接

Batch Management

2012-05-16T01:22:00Z

Agenda

1. The purpose Batch Management

2. The different terminologies in Batch management

3. Batch Management in different modules

4. Traceability with Batch

5. Notes

1. The purpose Batch Management

Product produced according to the Recipe and in one homogenous mixture which can not be reproduced

It is mainly used in

Food product manufacturing
Chemical manufacturing
Process Industries.

2. The different terminologies in Batch management

Batch characteristics

It is the property of the batch which has to be attached to the batch.

Batch class

Class is the carrier of characteristics.

Class will be attached with the material master.

Production Date:-

Date when the product was produced.

Expiry Date:-

Date beyond when the product can no longer be used

Shelf life period:-

It is the duration of any product when product can be used.

Recurring inspection:-

Inspecting the product at periodic interval to check its shelf life.

Batch Status:-

Condition of the Batch usability will be known from the batch status.

Batch Search Strategy:-

While issuing the goods for process order or production order, batch number of components can be searched through Batch search strategy.

Condition Technique – (Condition Table):-

System searches the batch through predefine tables in a sequence which are known as condition table and Access sequence.

Condition Technique – (Access Sequence):-

System searches the batch through predefine tables in a sequence which are known as condition table and Access sequence.

3. Batch Management in different modules

Configuration

3.1 Batch Management can be activated in three levels. They are

Client Level
Plant Level
Material Level

MENU PATH:-

IMG: Logistics General --> Batch Management --> Specify Batch Level and Activate Status Management

3.1.1 工厂级别

同一物料，同一批次可以在多个工厂中使用，但是在不同工厂中的特性值可以不同

3.1.2物料级别

同一物料，同一批次，在所有工厂中的特性值必须相同

3.1.3集团级别

一个批次号在整个集团是唯一的，只能分配一次，不能同时分配给其他物料

3.2 批次管理状态

3.2.1 Batch Activation in Material Master

Provision to activate batch management in material master is available in purchasing view and in work scheduling view.

3.2.2 激活批次状态管理：限制和非限制状态

3.2.3 可以通过MSC2N 将批次限制，未来该批次就不可以使用

3.4 . 批次号码有生成方式：

3.4.1 . 批次号码可以手动输入：MSC1N

3.4.2. 可以系统自动分配：例如扣帐系自动分配

3.4.2.1激活自动分配号码（如果需要内部给号，需要进行激活）

3.4.2.2、系统移动时会自动产生批次，针对异动类型可以定义是否需要检查，以避免错误

（如下是设置画面，为了方便查看，贴图为中英文两个版本）

3.4.2.3 Define initial creation of Data for Batch master Transaction

可以针对Mat. Type设置Batch创建规则，这样就能实现成品101入库自动生成batch，而PO 101收料手动生成的效果

It should not be possible to assign a batch manually for finished products. The batch numbers should always be determined automatically by the system. To ensure they are determined automatically, choose the option “C - automatic/ No manual creation” for the material type

FERT.

3.5. Batch Valuation

Below is the Standard characteristics defined by SAP.

LOBM_VFDAT expiration date, shelf life

LOBM_VERAB availability date

LOBM_LFDAT delivery date

LOBM_RLZ required remaining shelf life of batch

LOBM_MENGE sortable quantity

LOBM_ZUSTD status of batches

LOBM_LVORM deletion flag

LOBM_BWTAR valuation type

LOBM_LGORT storage location

LOBM_QNDAT next batch check date

3.6 Batch 相关操作

3.6.1 Batch Class&Characteristics

3.6.1.1 Create characteristic -- CT04

3.6.1.2 Create Class （将特性归结到一起）-- CL02

Class type 分为两种：

023 批次层在物料层

022 批次层在工厂层

3.6.2 将Class（分类）指派给物料（物料用到批次时，不一定需要分类）

两种方式进行指派：

3.6.2.1 :建立料号时指派分类

如果分类中class type不是自己想要的，可以通过这种方式进行修改

放入类别名称：

3.6.2.2 ：CL20N

可以新增或者修改

指派之后，在物料异动时，如果扣帐时没有提供特性值，会跳出特性值画面，如果特性值在扣帐时提供，系统会自动创建批次，批次会带出特性值

扣帐时已经找到特性值供应商，批次可以建立起来

当然也可以对某些关键特性设置必输项，并Error提示

CT04---

Customization:

查看库存时可以看到批次的详细信息

MSC3N 也可以看到详细的信息

3.6.3 . 物料主数据中限定的特性值，会限制未来物料异动的输入(异动时输入的值必须在物料主数据限定的范围)

3.7. 批次整合性

--货物移动都需要批次

--可以进行限制库存于非限制库存转移

3.8. 剩余货架寿命

进料日期与有效期到期日所差的时间最短为最小剩余货架寿命才能扣帐

3.8.1 Master Data 维护

使用生命周期的情况下，最好使用批次，否则无法得知这批料何时到期

Max. storage period：主要是用做参考（This function helps you to monitor from disposal processing whether the maximum storage periods for wastes are being kept to.）

Time unit

Min. Rem. Shelf Life：最小剩余货架寿命（就是说仓库操作需要的最少时间）

Total shelf life :总寿命

Period Ind. for SLED：货架寿命单位

Rounding rule SLED

Storage percentage

A 生产日期+总寿命-过账日期

B 剩余货架寿命

A >= B OK

3.8.2 检查到期日(OMJJ)

可以使用MCHA中的到期日或者收料日做先进先出的处理

3. 9、Batch Determination and Batch Check

每个模块又相应的配置,配置起来比较复杂，原理跟Price Condition类似

不同的配置路径如下：

通过应用程序application得到查找程序search procedure

3.9.1 MM 移动类型

3.9.2. Search(上图Z0001)设定: Batch Search Procedure Definition

3.9.3 CTyp--Condition Type(上图ZMM2)设定: 找到策略类型（按顺序找，如果前面的策略类型没有再找后面的）

3.9.3.1 .Access Seq.--Z001，即路径：/Access Sequences,SAP通过Access Seq.找到Condition Table及字段

通过存取顺序得到表（多条）如果能读取到记录，就表示可以得到批次，如果读不到，就不会自动得到批次.

如何在Condition Table维护资料？ -- MBC1

在操作MBC1时“Selection Criteria”务必要维护，否则Selection中即使放了Class系统也无法找到，因此就无法自动Select相应的batch

3.9.3.2 Selection -- 相当于filter，就是对找到的Batch筛选

3.9.3.3 Sorting

存取顺序(上图Sort Sequence)设定

3.9.3.4 Batch split

多个Batch对应一个Item(如Deli. Item)时所用

SELECT <Condition Filed> FROM <Condition Table> WHERE <Selection> SORT BY <Sorting>

3.9.3.5 领料操作 MB1A

发料输入*让系统自动找到批次

可以根据如下界面输入选择标准，在无法查找信息时进行策略分析

(通过选择标准按钮进入选择条件界面,Key 入选择条件则系统会带出符合条件的item供选择,策略分析可以看到是否正确batch determination找到对的item)

将排序顺序维护至策略类型（如果table之前维护时排序顺序没有维护，后续需要修改排序顺序）

5.Notes:

Activities in Batch Management

Transaction	Activity
CT04	建立特性
CL02	创建类别
CL20N	指派给物料
MB56	批次跟踪报表
MSC3N	Display Batch
MSC4N	Display Changes
MM75	Display Archive
BMAA	Overview of Archiving Runs
MBC3	Display Batch Search Strategy for Inventory Management
COB3	Display Batch Search Strategy for Production Order
COB3	Display Batch Search Strategy for Process Order
VCH3	Display Batch Search Strategy for Sales and Distribution
LS53	Display Batch Search Strategy for Warehouse Management
CT03	Display Characteristic
BMC3	Display Selection Class
CU72	Display Sort Rule
MB5C	Pick-Up List
MB56	Display Batch Where-Used List
MB57	Compile Batch Where-Used File
BMBC	Batch Information Cockpit
BMCC	Integrity Check for Batch Classification
MB5M	SLED List
QA07	Periodic Checks of Batches in QM
COEBR	Batch Record
CO09	Availability Overview
MM03	Display Units of Measure for Material
MWB3	Display Standard Price
MWBC	Consistency Check for Batch-Specific UoM

本文链接

ABAP “FOR ALL ENTRIES IN” 使用指南

2012-05-03T07:27:00Z

(from http://scnblogs.techweb.com.cn/mangmang/archives/35.html)

在ABAP开发中，对于不能使用join的聚集表或者需要使用SELECT 的内表，我们一般使用for all entries in 语句将该表与内表串联，查询出需要的数据，例如： BSEG聚集表为例，如下：
SELECT bseg~kunnr

bseg~lifnr

bseg~belnr

INTO TABLE itab_bseg

FROM bseg

FOR ALL ENTRIES IN itab_main

WHERE bukrs in _bukrs

and ( belnr = itab_main-belnr

AND hkont = itab_main-hkont ).
由于BSEG不能和BSIS做inner join所以先将BSIS内容放到itab_main 中，然后用 FOR ALL ENTRIES IN来串联。

1-WHERE子句中的 bukrs in _bukrs是指bseg-bukrs存在于_bukrs这个select-options中，_bukrs不是itab_main的field所以这部分不包括在括号中.

当然会增加内存使用了。
原本一个条件，数次（驱动表的纪录条数）向对DB操作，
使用了FOR ALL ENTRIES后，
相当于把驱动表里的条件字段的所有值用OR 连起来，
一次对DB操作，
条件语句增大，势必使内存占用增多。

1．SELECT CARRID

CONNID

PRICE

FROM SFLIGHT

INTO TABLE IT_PRICE

FOR ALL ENTRIES IN IT_SFLIGHT

WHERE CARRID = IT_SFLIGHT-CARRID

AND CONNID = IT_SFLIGHT-CONNID’.

在 WHERE 条件中，IT_SFLIGHT-CARRID和IT_SFLIGHT-CONNID这些列将用作占位符。该 SELECT 语句的结果集是 SELECT 语句的所有结果集的联合，这些结果集是用内部表 IT_SFLIGHT 中的相应值在每一行上替换占位符的结果。实际上该WHERE子句的特殊变式就是下面WHERE基本语句的简略写法。
SELECT DISTINCT CARRID

CONNID

PRICE

FROM SFLIGHT

INTO TABLE IT_PRICE

WHERE ( CARRID = ‘LH’ AND

CONNID = ‘2415′ ) OR

( CARRID = ‘SQ’ AND

CONNID = ‘0026′ ) OR

( CARRID = ‘LH’ AND

CONNID = ‘0400′ ) .

2．使用该语句，对于最后得出的结果集系统会自动删除重复行。因此如果你要保留重复行记录时，记得在SELECT语句中添加足够键值项目（有必要时，增加全部键值项目），以保证结果集中所需重复项目不会被删除。（例如选取支付金额时，支付事件可能不同，但金额可能相同，此时一定要注意，以避免错误删除结果记录。）

3．FOR ALL ENTRIES IN后面使用的内部表itab如果为空，系统将视为无条件选取，将当前CLIENT下所有记录选出。因此为避免无意义的全件检索，在使用该语句前一定要判断内部表itab是否为空，为空时不执行包含该语句的数据库检索处理。

4．由于itab-f实际上是作为占位符被替换，所以内部表itab中不要包含HEADER行（项目标识名称行），以免造成混淆，检索出错。

5．内部表itab中作为条件替换用项目的类型和长度，一定要和检索数据库中对应的项目相同，否则编译不能通过。

6．对于内部表itab中作为条件替换用项目，不能使用LIKE,BETWEEN,IN比较操作符。因为这些比较操作符都是不确定比较操作符（将选择条件设定在一个范围内），而FOR ALL ENTRIES IN语句的作用相当于将选择条件块全部并列开来，用OR连接，如果每个OR分支中又是不确定的范围，那么系统性能将大大降低，因此R/3系统在使用该语句时禁止使用不确定比较操作符。

7．使用该语句时，ORDER BY语句和HAVING语句将不能使用。

8．使用该语句时，除 COUNT( * )以外的所有合计函数（MAX,MIN,AVG,SUM）都不能使用。

//判断内表是否为空

使用语句： DESCRIBE TABLE ITAB LINES VARIABLE.判断系统变量sy-subrc是否为0，如果为0就表示不空，反之为空！
DESCRIBE TABLE ITAB LINES VARIABLE

IF NOT P_VARIANT IS INITIAL.
WX_VARIANT-VARIANT = P_VARIANT.
ENDIF.

本文链接

MM-Document Release Strategy

2012-04-12T00:43:00Z

用于MM-Document(PO, contract, scheduling agreement, request for quotation (RFQ)等)在一定条件下需要审批流程的情况

关键术语：

Release Characteristics: Classification characteristics constitute the criteria for a release condition. 就是说签核过程中要用到的栏位。

也可以用CT04定义审批条件的要素，比如采购组或者总价值，我们可以在表CEKKO中找到所有可以被利用的字段，如果不能满足需求，就需要enhancement M06E0004

Release Class：

Class: In a class, you group the characteristics that are to constitute a release condition for a release strategy.

You must assign the same class to all release groups with the same type of release (item-wise or overall).

就是说一堆Characteristics的组合。

这里要说的是Class是个相对公用的东西，很多地方都会用到，那PR/PO Release 这块儿就用Class Type=032

也可以直接用CL02定义class

Release Group：用来连接Release strategy各元素的桥梁，同一个release group具有相同的审批level,它用来决定一个Strategy可以使用的数据。

一个Group可以对应多个Strategies

比如001采购组大于5K的金额需要审批，而002采购组大于10K的金额需要审批，这就需要连个不同的审批组，而如果另一个C部门，但是依然用采购组001和大于5K的policy，那么它可以与第一组共享审批组。

Example:Release group 01 is defined for purchase requisitions and release group 02 for purchase orders. You can define release strategy S3 for both purchase requisitions and purchase orders.

Release Code:我们可以理解为现实中与整个审批流程相关的人，每个审批者都会审批相应的release code。如果配置了workflow，可以将他们与workflow结合起来用，审批自动到达他们的task中。

Release prerequisite：某Release Code可以签核的前提条件

Release indictor：定义审批中的各种状态和在此状态时系统的反应。

比如我们这里有2个状态，在审批流程中都会是状态1，也就是没有release，可以更改PO并且不会触发新的审批流程，或者是在触发新的审批流程的值状态时进行新的审批等。后面的value change字段限制了字段更改的最大范围，超过了一定百分比系统会产生错误信息。

再比如某个Release Code签核之前一直要处于blocked状态。

Release strategy ：定义审批流程。Release codes我们看到最多输入8个，我们按照审批顺序输入。

Classification相当于定义这个审批策略被触发的条件。

Athorization：

整个审批的授权可以通过分配authorization object M_EINK_FRG给相应用户进行Release Group和Release code分配

流程概述：

PR:

通过设置PR 审批策略针对符合Classification中条件的PR生成签核流程。

对于PR的审批可以在item级别也可以再total级别，并且有带classification和不带classification两种，不过不带classification的只能在total级别审批。

PO:

PR release T-code：

ME54N：单笔release

ME55：批量release

PO release t-code

- ME2K

- ME2C

- ME2N

- ME2W

- ME80FN

- ME81N

GR/IR Account maintenance

2011-12-10T07:59:00Z

一、业务背景

一般情况下GR/IR Account是要平衡的，但是有些特殊情况会造成GR/IR Account不平，因此就需要对GR/IR Account进行调整

第一种情况：“GR小于IR”，是说下系统会期待进一步的GR或者通过Credit Memo来平衡GR/IR Account，但跟Vendor确认后得知的确不会再有GR或者Credit Memo

第二种情况，“GR大于IR”系统期待进一步IR或者通过Return业务来平衡GR/IR Account，但跟Vendor确认后得知的确不会再有IR而且也不需要Return

二、处理流程

GR/IR Account maintenance一般是在一个周期执行一次，而且执行前要务必确保相关的PO不会在有后续动作

1. 通过此方式处理的差异系统会产生一个Account maintenance doc.

2. 根据PO或材料属性的不同，清GR/IR的帐会post到不同的科目

if moving price, post to stock account

if standard price, post to price diff. account

if account assignment, post to consumption account

3. Operation

3.1 t-code:MR11

Processing最好选Prepare List，看清楚再决定是否处理

本文链接

Releasing Blocked Invoices

2011-12-09T06:03:00Z

一、Blocking Invoices

An invoice is blocked for one of the following reasons:

1. Automatically due to variances in an item

2. By entering a payment block manually

3. By stochastic blocking

二、 Releasing Blocked Invoices

1. 实际界面中move cash discount date就是Change Baseline Date for payment（是否用当前时间更新baseline date

2. 可以选择Release Manually，或者选Release Automatically然后排JOB Run

本文链接

Park Invoice

2011-12-09T05:41:00Z

When you park an invoice, the R/3 System saves the data that you enter. It assigns a number to the document, but no postings are made.

You can change a parked document as often as you like.

The R/3 System only makes the actual checks within the Post parked document function.

Account postings are made when you post a parked document.

Parked documents are listed in the purchase order history.

You can define release strategies for Preliminary Posting. These strategies define how parked documents must be approved for posting. You use Workflow to support the processing of parked documents. (This function corresponds to Document Parking in Financial Accounting.)

When you are working in Invoice Verification, you can branch directly from the document overview to Preliminary Posting.

You can delete a parked document. The R/3 System does not re-issue the number of the deleted document. When you delete a document, the document header remains in the R/3 System as evidence of what the document number was issued for. The line items are deleted from the database.

有点儿像Hold或者暂存，先生成个号码占着，然后审核过后在post

本文链接

Evaluated Receipt Settlement(ERS)

2011-12-09T05:30:00Z

Definition

Evaluated receipt settlement (ERS) is an automated system used by businesses for the receipt and payment of goods. It is used by many companies including General Motors.

简单来说就是不用每次都在SAP里做发票校验，而是用约定的方式线外确认发票。SAP自动生成Invoice。
在系统中可以维护ERS事物的日志，作为日后付钱给供应商的凭证

评估收货结算功能只能用于已经在采购订单中订购的货物。只有知道了采购订单，才能使用 ERS 结算发货时的准确价格。如果发出的采购订单没有准确价格，则必须继续手动结算。所以，建立PO前提必须遵循以下条件：

1.维护VENDOR的时候标记ERS

2.信息记录中的无ERS不能勾选

3.PO项目细节IV下ERS勾选

最后，创建了采购订单，登记了收货，评估收货结算 (ERS) 将结算没有在后台接收到供应商发票的收货

可以通过事物代码MRRL查看ERS的结算结果是否正确。

Process

When a company receives goods from a vendor, the ERS program pays the bill without the vendor sending one to the company. The charged prices are typically based on a catalog or other means of previously agreed-upon prices. When a company orders goods, the supplier electronically sends an advance shipping notice (ASN). The buyer compares it to the actual goods received, verifies the ASN and approves it. Payments are automatically generated by the ERS when they are due.

一、要想实现ERS先要按照上图设置

1. Vendor Master

2. P-info 此处是要求不能勾，当然没info的话就相当于不勾了
3. P-info 中Tax Code的设置是为了能够带到PO中，这个不是必须的，后续在PO中输入也成

二、Maintain ERS in PO Data

1. Account Assingment

2. ERS

3. 下图两个选项，只能同时选上，或者同时不选

4. T-Code：MRRL查看ERS的结算结果是否正确

三、 The Invoice Planning
The Operation

The Settings of Invoice Planning

Features

An ERS system establishes terms of payment, prepares an invoice, posts it and pays it. It also has the capability of producing credit memos for returned or damaged goods. For this system to work, the supplier and buyer must have an ERS system.

Benefits
An ERS system eliminates the need for vendors to issue bills to buyers. It saves both companies time by eliminating paperwork. Accounts payable and accounts receivable workers are relieved of accepting, entering and paying or billing invoices. It also offers consistency to the buyer. They always know exactly what they are charged for goods prior to shipment.

allows you to settle goods receipts without receiving an invoice.

以下摘自：ＳＡＰ屠夫:

http://community.kingdee.com/pages/sapguru/blog/archive/2009/03/23/350546.aspx

5. 集团内部发票校验

I．是否基于收货进行发票校验

通常,从控制角度,材料采购的发票校验确定应付必须有供应商送货单、供应商发票和企业仓管部门的收货单等进行匹配才能确定应付;对于服务采购和费用采购也需走采购流程。

但是，集团公司间的采购业务，如果也必须基于收货进行发票校验，则可能有如下后果：

1. 销售方在发货后Billing确定应收,如使用使用EDI传送发票,由于采购方尚未收货,将无法同步自动发票校验过帐应付。

2. 销售方已确定应收但采购方未及时确定应付，货物在途如果跨月不但影响采购方的MRP而且造成集团报表合并无对应内部应付出现抵消差异。

因此，可以将内部供应商不设置“基于收货进行发票校验”。

II. 评估收货结算ERS

有些集团内部应收通常禁止计提坏帐准备,所以，为了减少MM模块采购的收货和发票校验,可以使用ERS功能,ERS(Evaluated Receipt Settlement)顾名思义表示基于收货评估的结算,

设想一下,集团内部购销业务,采购方一建立采购单自动触发销售方的销售单;销售方采用MTO方式,自动触发产品的生产工单建立和MRP跑出下层原料需求;采购方收货后自动根据收货建立发票校验,一定程度上可以减少不少发票校验工作量。

ERS功能启动很简单，步骤如下，参考下图：

(1).维护供应商采购视图的ERS标志,见上图-[2]的”自动评估GR结算交货”和” 自动评GR

结算保留”标志,需要使用ERS和发票计划请选择该俩标志。

*发票计划可应用于比如大型项目或服务采购按完工百分比进行收付款的业务中。

(2).如果使用采购信息记录,信息记录中的无ERS不应选择。

(3).建立采购单时ERS标志自动从供应商主数据带出,如上图-[4]可以看见”ERS”标志被选上。

(4).MIGO采购收货。

(5). MRRL查看和运行ERS的结算，默认需要配置一消息类型，比如销售方发货1000,采购方只接收999个,1个途损,可设置一消息比如发送邮件给销售方确定,如果不设置消息类型,系统默认是错误消息号 “M8 446”, 如不需要消息,Tcode OMRM关闭M8 446,运行MRRL就可自动产生发票校验。

通过上面步骤，整个ERS功能启用还是十分简单。ERS可以发票校验减少工作量和方便购销方Idoc/ALE自动过帐,但最好有以下业务前提：

. 采购数量和发票数量最好无差异,无量差。

. 采购价格和实际发票价最好一致，无差价。

否则，MR11或后续调整？

III. 后续结算

还有一个后续结算,所谓后续结算是根据采购方与供应商双方达成的条件在协议期末对到期金额进行的计算和结算,这个过程可以是一次性的或阶段性的,后续结算功能包括:

中期结算

部分结算

最终结算

Tcode: MEBI

零售企业通常使用,实际上不使用后勤的自动后续结算,手工财务处理也是可以的。

本文链接

Delivery costs in MM

2011-12-07T05:28:00Z

Definition

Delivery costs are costs that are invoiced for a delivery over and above the value of the delivery itself. This includes freight charges, customs duty, or other costs.

Delivery costs分两种情况：

Planned delivery costs 计划费用，为开立PO时知道要花费的费用，如Freight 运费；

Customs 报关费用等。已知费用

Unplanned delivery costs 非计划费用，为开立PO时不知道要花费的费用。未知费用

1. Planned delivery costs

Planned delivery costs are agreed upon with the vendor, a carrier, or a customs office before the purchase order is created. You enter them in the purchase order.

Planned delivery costs can be differentiated as follows:

Origin of Costs
- Freight charges
- Customs charges

Calculation of Costs
- Fixed amount, irrespective of delivered quantity
- Quantity-dependent amount
- Percentage of value of the goods

2. Unplanned delivery costs

Unplanned delivery costs were not agreed on in the purchase order and are not entered until the invoice is received.

You can enter the unplanned delivery costs in the invoice document alongside the costs incurred. You can post unplanned delivery costs as follows:

● Distribute them proportionally to calculated invoice items

● Distribute them proportionally to calculated invoice items, inclusive of planned delivery costs

● Post them to separate G/L accounts

You can use the Business Add-In MRM_UDC_DISTRIBUTE to define your own rules for distributing unplanned delivery costs. For more information, see the documentation for the Business Add-In.

The Process

1. Planned delivery

购买料件后为了把买来的料件送入仓库这个过程中产生的费用为 Delivery costs 收料费用，可以按照购买料件的种类把这部分费用分摊，计划费用在做GR时会抛入不同的G/L account, 而非计划费用则是在做IR时手动加入，按照设置的不同放入stock account, G/L account。

如下图：

1.1. 通过Price Condition 实现

Purchasing--> Conditions -->Define Price Determination Process -->Define Condition Types

1.2. 对于运费如果要放特别的科目需要在Condition Schema里面关联，Accruals，然后在OMWB里设置科目

1.3. 做IR的时候是否要显示Planned delivery条目，需要在下图选项中选择下。

2. Unplanned delivery costs

只在IR的时候才发现供货商有额外的运费发生，输入在发票里。GR中只会按照正常的计入GR/IR Clearing acct.。在IR时将额外的运费直接计入stock account中（moving price）或是Standard price就会抛到small diff. account里---根据配置

2.1 在IR时在details tab中输入Unplanned delivery costs

2.2 可以通过系统配置，来指定unplanned delivery cost在IR时，是自动分配到各个明细项中还是计入一个特定科目。此处我们自动分配到明细项中。

Configure How Unplanned Delivery Costs Are Posted --- Prerequisite

设置Unplanned posting方式

IMG:MM-->LIV-->incoming invoice-->Configure How Unplanned Delivery Costs Are Posted

设置Unplanned费用要计在那个地方，如果是SPACE则会将运费分配到各明细项，如果是2则抛入固定的科目UPF/Unplanned delivery costs

2.3 科目设置

本文链接

Subsequent debit/credit & Credit Memo

2011-12-07T05:24:00Z

credit memo和debit memo是对企业向顾客已经交付的货物的价值进行调整的单据类型。

举个例，如果您已经就所交付的货物向买主开具了100元的发票，可是由于货物质量的瑕疵，买主主张“货接受但必须削价10元”，如果您接受了这个主张，那您就得开具10元的credit memo（即实际业务中的所谓“红字发票”）。总之，与原始invoice的价值相比，增价用debit memo，降价用credit memo，两者都是billing document type。

在做IR时操作上相对比较简单，只要选择不同的选项。

subsequent credit和credit memo的区别是，前者只能对发票或者PO的总价值进行减少，而后者可以减少数量来相应的减少价值。credit memo的另一个情况就是发票开完之后发现一个物品坏了，要求供应商退款。

A subsequent debit/credit arises if a transaction has already been settled, and a further invoice or credit memo is received afterwards.

A subsequent debit/credit changes the total invoice value of a purchase order item; the total invoice quantity remains unchanged. Therefore, only a value-based update of the purchasing transaction takes place. There is no quantity-based

update.

1. Subsequent Debit :-You must enter an invoice as a subsequent debit if a purchase order item has already been invoiced and further costs are now incurred. (Example: A vendor has inadvertently invoiced you at too low a price and then sends a

second invoice for the difference.)

2. Subsequent Credit :- You must enter a credit memo as a subsequent credit if a purchase order item was invoiced at too high a price and you have now received a credit memo. (Example: A vendor has inadvertently invoiced you at too high a price and then sends a credit memo for the difference.)

If you enter a subsequent debit/credit, the system suggests the entire invoiced quantity, but no value. The maximum quantity that you can subsequently debit or credit is the quantity that has already been invoiced. You can only enter a subsequent debit/credit for a purchase order item if an invoice has already been posted for this item.

A subsequent debit/credit cannot refer to a particular invoice.

Subsequent debits and credits are listed separately in the PO history.

3. Credit Memo :- You usually receive a credit memo from a vendor if you were overcharged. As is the case for invoices, credit memos refer to purchase orders or goods receipts.

You post a credit memo if too large an amount has been invoiced. When you post the credit memo, the total invoiced quantity in the PO history is reduced by the credit memo quantity. The maximum quantity you can make a credit for is the quantity that has already been invoiced.

In the same way as the corresponding goods receipt is expected or posted for the invoice, in the case of a credit memo, the system assumes that the credit memo belongs to a return delivery or reversal of the goods receipt. This means that the credit memo is settled using the GR/IR clearing account.

Valuation & Stock Account Updates

When a material is valuated at Moving Average Price, based on the quantity specified, while entering a subsequent debit/credit, the system checks for availability of quantity in the stock, if sufficient stock is available then subsequent debit/credit is posted to stock account and if sufficient coverage does not exist for this quantity, only the portion for the available stock is posted to the stock account. The rest is posted to a price difference account. This way, the posting does cause a change in value in the material master record to the tune of amount posted to stock account.

When a material is valuated at a standard price, the subsequent debit/credit is posted to a price difference account. This way, the posting does not cause a change in value in the material master record.

Valuation & Stock Account Updates