SD从零开始61--可用性检查和需求传递 zz

销售订单中的可用性检查Availability Check in the Sales Order

在物料主数据的销售和分销TAB页你能够：在general/plant页的可用性检查字段中输入，应该在订单处理过程中为该物料执行哪个和/或什么类型的可用性检查；

在配置中还有许多的表，可用性检查也依赖于这些表；

销售订单处理中发生可用性检查的条件：

物料需要库存检查；

在配置中为该事务设置了可用性检查；

物料可用日期检查Material Availability Date Check

物料可用日期从交货排程确定；足够的物料需要在该日期可用以在客户要求的交货日期及时地交货给客户；

系统计算该日期，从客户要求的交货日期向后扑悖?/span>

系统计算捡配，包装，装载和运输货物的时间；

可用性在物料可用日期检查；

工厂检查Plant Check

系统按照下列顺序访问信息以建议标准的交货工厂：

1. 客户-物料信息记录；

2. Ship-to Party客户主记录；

3. 物料主记录；

如果你在订单输入时手工输入交货工厂，你的输入会覆盖默认值；

在客户-物料信息记录中，你可以为一个客户的某一特定物料维护建议的值；

你可以在物料主数据的销售和分销tab页：Sales Org.1的delivering plant字段找到交货工厂；

你可以在客户主数据的shipping tab页找到交货工厂；

可用性检查控制Control of Availability Check

在配置中，依照你正在使用的事务，你可以设定哪些元素包括在一个可用性检查中；这样，你定义哪种类型的库存（例如，安全库存，转移中的库存或者质量检查中的库存），哪种向内的移动（例如，采购或者生产订单）以及哪种向外的移动（例如，销售订单，来自MM的预留）应该包括在检查中；

需求传递Transfer of Requirements

销售和分销与采购之间的交流通过需求来实现；

需求传递的类型能够影响可用性检查；

负责物料计划的员工收到有关系统中的销售订单以及SD需要来交付这些订单的数量的信息；

订单的物料可以来自内部生产或者外部采购；

如果可用的物料不足，可通过物料计划（Material planning）来创建采购订单；

完全和部分交货Complete and Partial Deliveries

你和客户关于交货达成的协议也会影响可用性检查的结果；

依赖于客户销售订单中的部分/完全交货的协议，你可以交付一张订单用一个完整的交货或者几个部分交货；

在一个完全交货中，所有条目的订购数量都被交付了；

对于部分交货你可以将一张订单的条目或者数量分配到几个交货中；

部分交货协议Partial Delivery Agreement

控制完全/部分交货的指示符从客户主记录中带出；条目层的建议来自客户-物料信息记录，如果那里已经维护了客户和物料的协议的话；这些指示符可以在销售订单输入过程中手工修改；

客户可能要求，例如，一个完全交货意味着销售订单中的所有条目应该一起被交付；如果客户同意一个部分交货，该订单可以对应几个交货；

如果你选择“完全交货”，你能够确定整张订单中的所有条目必须一起交货；在条目层次，你也可以决定你是否可以分割交货数量；

存在以下部分交货协议：

_允许部分交货；

A输入一个数量不等于0的交货；

B仅创建一个交货（也含数量=0）；

C只能执行完全交货；

D首选并发交货；

案例1：确认要求的交货日期Case1：Confirmation on Required Delivery Date

系统使用交货排程来检查货物是否在物料可用日期可用；

可用性检查包括：

当前库存；

计划的向内移动（例如采购订单，采购请求，计划订单）；

计划的向外移动（例如存在的销售订单，交货）；

在案例1，关于向内移动的情况如下：存在的向内移动有：

库存：100pc；

存在的采购订单有数量50pc和60pc；

下列未来的向外移动也存在：

存在销售订单有数量100pc，40pc，50pc；

在该向外情况中你输入另外一张10pc的销售订单；系统基于客户要求的交货日期执行交货排程（后向排程）并确定物料可用日期；然后为该日期运行可用性检查；

案例1的结果：确认要求的交货日期Result for Case 1：Confirmation Required Delivery date

可用性检查显示系统可以为要求的交货日期确认这10pc；

案例2：确认一个稍后的日期Case 2：Confirmation for a Later Date

案例2的最初情况和案例1相同；

然而在本案例中，客户要求完全交货；

在向外的情况你输入另外一张20pc的销售订单；系统基于客户要求的交货日期执行计划排程（后向排程）并且确定物料可用日期；然后为该日期运行可用性检查；

案例2的结果：确认一个稍后的日期Result for Case2：Confirmation for a Later Date

在库存不足的事件中，系统使用可用性检查和交货排程来确定下一个可用日期，在该日期可以为客户确认货物；

因为有一个完全交货协议，数量不可以分割；

你需要为稍后的日期确认这20pc；

系统使用基于物料可用日期（前向排程）的交货排程来计算20pc的确认日期；

案例3：部分交货Case 3：Partial Deliveries

如果客户和销售凭证类型允许，要求的销售订单数量也能够被分割到几个部分交货；

案例3的情况与1和2相同：

在案例3，客户要求尽快交货并且允许你必要的话分割交货数量到部分交货中；

案例3的结果：部分交货Result for Case 3：Partial Deliveries

当没有足够的库存，系统使用可用情况和交货排程来确定下一可用日期，在该日期能够确认客户的货物；

“允许部分交货”协议意味着数量能够被分割；

你能够为2个稍后的日期确认这20pc，每个日期10pc；

系统使用物料可用日期和交货排程来计算2个部分交货，每个10pc；

案例4：带补货提前期的检查Case 4：Check With Replenishment Lead Time

你可以考虑所有的向内和向外的移动；推荐的是，你只在补货提前期的末尾执行一个可用性检查；

补货提前期可以为每个物料指定；例如，贸易商品：计划交货时间+收货处理时间；最终产品：内部生产时间；

系统假定物料最晚将会在补货提前期的末尾可用；

可用性检查仅在补货提前期的末尾运行；

如果你在案例4中执行不带补货提前期的可用性检查，结果和案例2一样；客户要求一个完全交货；你不能使20pc可用直到最后那张60pc的采购订单到达（向内移动）的同一天；

然而，如果系统使用补货提前期执行可用性检查，你可以使20pc在50pc的采购订单到达的日期可用；只有在补货提前期内的向内和向外移动才包含在该检查中；

拖欠订单处理Backorder Processing

满足下列条件的订单条目是拖欠订单：

一个订单条目的数量没有完全确认；

订单条目的要求的交货日期不能遵守；

有两种类型的拖欠订单处理：

手工拖欠订单处理：

你可以使用拖欠订单处理来为物料列出销售凭证并且参考确认手动地处理；这意味着ATP数量能够被重新分配并且任何不足会被清除；

通过重新排程

你能够在自动重新排程中使用交货优先级（为销售订单从客户主记录中带出）作为一个排序标准；

控制可用性检查和需求传递Controlling Availability Check and Transfer of Requirements

在需求传递和可用性检查中，系统区分定购时间和交货时间；

对两个时间点，物料的可用性检查组决定是独立的还是全部的记录作为需求传递到MRP，如果需求传递执行的话；对特殊库存的需求记录基本上都是独立需求；

系统为两个时间点确定在可用性检查中货物的哪些向外和向内移动会被考虑；包含特殊库存（寄售，可返回包装，按订单库存）的事务被单独立控制；存在哪些特殊库存通过条目类别确定；在按订单生产的案例中，需求类的科目分配类别E确定实际上包含按订单库存；

你使用需求类来为SD（orders，deliveries）全局地确定是否将为物料传递需求以及是否将会执行一个可用性检查；两个功能都可以通过计划行类别为相应的事务设置为非激活；交货专门由需求类控制；

例子：计划的独立需求-在订单中按订单生产Example：Planned independent Requirements- Make-to Order in the Order

分配给物料类型的策略组将计划作为主要策略；如果销售订单中没有协议别的东西，需求根据该策略传递；计划策略确保物料需求是预先计划的（计划的独立需求类别VSF）；后续的计划的独立需求（KSV）针对计划消耗这些预先计划；

如果为需求类激活了可用性检查，可用数量计算来自库存，计划的收货，向内移动的货物和向外移动的货物；可用性检查规则控制在可用性检查中什么被评价为货物的向内移动和向外移动；

如果在销售的事务处理中设置了计划分配；并且如果可用性检查通过需求类设置为非激活的，则可用性检查针对生产计划执行；如果物料的计划的独立需求不能覆盖订单数量，则计划分配（planning assignment）控制销售订单中屏幕的显示；该屏幕与可用性控制屏幕相同并且相同的规则对采用检查的结果有效（one-time delivery，delivery proposal，full delivery）；

除了计划主策略，策略组还允许你为物料执行按订单生产；为此，你必须到订单的procurement预览屏幕并在相应的条目中替换默认的需求类型KSV为策略（KE）允许的需求类型；

例子：计划的独立需求-按订单生产/报价单Example：Planned indep.Requirements –Make-to Order/Quotation

相应的流程通过计划行类别影响需求传递和可用性检查；这意味着，例如，通过计划行类别来使需求传递和可用性检查无效；

SD从零开始30--捡配（Picking）zz

捡配Picking

捡配是为向客户交货准备货物的流程，同时特别关注

dates，quantity，quality；

你可以为每个delivery item category指定是否relevant for picking；

通常，picking由打印一张picking list开始；SAP推荐你使用WM transfer order功能；为此，你不需要实施整个WM系统，Lean WM就足够了；

使用lean WM代表只使用了R3 WM模块的一小部分功能；

在outbound delivery的output control的帮助下，你也可以将数据传输到为picking流程实施的子系统；

在系统的标准配置中，posting goods issue的前提是所有picking相关的items都已经完成了捡配；这意味着outbound delivery中的delivery quantity和pick quantity必须相同；

使用WM/Lean WM的捡配流程Picking Process Using WM/Lean WM

在picking中使用WM（WM or Lean WM），你要创建一张transfer order（TO）；

TO是一张用来启动和监控一个仓库内部货物移动的凭证，你基于要使用WM捡配的项目创建一张或多张transfer order；

然后你打印出transfer order，该步骤可由系统自动执行；

除了以picking list的形式打印transfer order，你还可以将transfer order的数据传送到外部系统（PDA）或者仓库控制器；

通过确认transfer order，你可以校验从仓库移走的数量；如果你有confirmation requirement，你必须单独地执行这一步骤；如果没有confirmation requirement，则在你创建transfer order时系统自动确认数量；

最后，你可以post goods issue，这样就完成了shipping流程；

转移订单The transfer order

Transfer order是一张在仓库中将物料从源storage bin移动到目标storage bin的说明；

Transfer order包括以下信息：

Material number；

Quantity to be moved；

Source and destination storage bin；

当你创建了transfer order，系统自动地复制outbound delivery中的delivery quantiry到transfer order中作为picking quantity；

当你创建transfer order时，outbound delivery中的picking quantity自动地输入，在Lean WM中，picking quantity最初和delivery quantity相同；

WM和Lean WM对比WM versus Lean WM

如果你使用随机存储的仓库（warehouse with random storage），你需要使用全功能的WM系统；因为一个物料可以存储在不同的storage bin或者同时存储在几个storage bin，storage bin层次的精确库存管理是必须的；

Lean WM不需要storage bin层次的库存管理因此更适合于固定库位的仓库（fixed bin warehouse），在固定仓库储存区域，物料总是在同一个存储库位；

要在picking document中打印storage bin，你必须在物料主记录的view“Storage1”

上维护各自的数据；维护更多的仓库数据和Warehouse Management view不是必须的；

不包含在Lean WM中的WM功能列示如下：

库存分区Storage section；

预留库位Reserve storage bin；

入库和捡配策略Strategies for putaway and picking；

库存补充Replenishment；

Inventory at storage-bin level；

这些相当地减少了实施的工作量；

Lean WM中仓库结构建模Modeling the Warehouse Structure in Lean WM

如果使用Lean WM，SAP系统中可能的warehouse structure of a fixed bin的描述为：

对于Lean WM，你需要至少一个warehouse number以及至少一个picking from的storage type和一个goods store的storage type（例如，picking atorage type作为source storage type，shipping zone作为destination storage type）；

在picking storage area，你可以从库存减少的角度将storage bin组合在一起（例如，平均地分配工作量）；Picking areas可以为每个仓库号码和storage type定义；

除了picking area，仓库中还有其他的组织单元；包括staging areas和doores，它们在outbound delivery中定义或者由系统决定并且也可以在picking documents中打印出来；

你可以在配置中在仓库号码层次上激活Lean WM；

建立和打印转移订单Creating and Printing transfer orders

有几种创建transfer order的方式，它们的区别仅在于自动化的程度；

在个别的案例，transfer order作为delivery的follow-on function创建是可能的；

你也可以单独地创建transfer order，要这样做，可以参考一张特定的outbound delivery创建transfer order，或者使用delivery monitor来同时为几张deliveries创建transfer orders；

如果你想transfer order自动地从每张outbound delivery创建，不需要手动的作业，则程序“automatic/direct TO”是非常合适的；

使用collective processing procedure，为了创建transfer orders的目的，你可以将几张deliveries组合到一起；

在WM，使用打印代码你有如下的打印选项：

单个打印：一个TO item一页（例如，item-by-item processing in the warehouse）；

组合打印：整个transfer order一张列表（也叫做“combined list”）；

捡配列表：在集中处理中创建的几张transfer order一张列表；

自动/直接创建转移订单Automatic/Direct creation of Transfer Orders

如果你不希望在一张picking list上发布几张outbound delivery的items，我们推荐自动或直接转移订单创建；

你通过outbound delivery的output control启动该处理类型；通过条件技术，你可以使系统在创建delivery时在outbound delivery的header层次决定output type WMTA；前提是outbound delivery的items至少有一个与WM相关；标准系统中关键字组合“Delivery type / Shipping point”(1st access) or“Delivery type”(2nd access)负责决定output；

输出类型WMTA的处理启动transfer order的创建；

依赖于输出类型WMTA的发送时间，你可以有不同的处理类型：

自动订单创建：时间1-3（processing later）

在这种情况下，output可通过后台的一个选择程序或者手动地使用事务“Output from deliveries”处理，这也可以定义后台计划；在自动转移订单 创建过程中，output process独立于outbound delivery creation；

直接转移订单创建：时间4（processing immediately）

这里，outbound delivery创建后立即启动处理；

在外向交货单监控使用集中处理Collective Processing in the Outbound Delivery Monitor

为了优化picking流程，你也可以为几张deliveries创建一张picking list；然后该list可以排序，例如，按照storage bin或material，依赖于配置中的设置；这样在相当程度上简化了在仓库中搜索picker的实际工作；

创建picking list的前提是transfer order尚未独立地创建；

使用集中处理程序来创建这些picking list：

http://blog.csdn.net/paulun/archive/2009/03/03/3953744.aspx
*********************************************************************

SAP Customizing Picking Output

From Release 4.5A, the system does no longer display the actions for SD picking in the implementation guide.

If you want to use the picking list according to the "old" procedure, you can maintain the list as follows:

o Carry out Transaction V/38 to maintain the output types ek00.

o Carry out Transaction OVLT to assign the picking list types to the
shipping points.

o Carry out Transaction V/53 to assign the picking lists to own
forms and programs.

http://www.sap-img.com/sd012.htm
***********************************************************************

RePrint a Pick List - EK00

e Output Type EK00 allows you to automatically default the PICKED Qty on a delivery to equal the delivery Qty. [For details on how to do this see OSS Note: 145136

We always had a problem with the EK00 output because you cannot Preview it nor RePrint it (using the normal Output functions).

However, (According to OSS NOTE: 132401) "If picking quantities are updated in the delivery document, you have the option of removing the picking quantities manually from the delivery, to save the document and therefore to start a determination and processing of picking output again."

What this means is: If you remove the Picked Qty and save the Delivery - it Reprints!!

*********************************************************************************

Individual Picking List SAP SD Picking Without Warehouse Management

May 2nd, 2008

You can print out an individual picking list to carry out picking for a particular delivery. This list forms the basis of picking in the following cases: The Warehouse Management System (MM-WM) is not used in your company. For further information, refer to Individual Picking List Without Use of MM-WM. MM-WM is installed in your company and picking from fixed bins is set. For further information, refer to Individual Picking List Without Use of MM-WM. Data in the Picking List The picking list includes the following data: Delivery number Printing date Shipping point Route Shipping point Delivering plant and storage location Picking and loading date Number and address of the ship-to party Gross weight and volume of the entire delivery Storage bin, material number, material short text and delivery quantity in the base unit of measure for all delivery items The delivery items are sorted according to which storage bin is specified for them. If there are different plants, storage locations and material availability dates in a delivery, a new page is started in each case. Storage Bin The storage bin specified depends on whether you are using WM: MM-WM not Installed The storage bin description is copied from the material master record into the list. WM in Operation With Fixed Bin Picking The storage bin, the warehouse number and the storage type that the Warehouse Management system determined for the product are copied into the list. Storage Bin Description The storage bin description is stored in the material master record. You will find the specification on the storage screen for a material in the field Storage bin. The description can be a combination of up to 10 characters. It specifies the physical location of a product in the warehouse. The storage bin description is displayed in the delivery on the first item details screen Item. All Data Displayed To call up this screen, select the item whose status you want to display on a delivery overview screen. Then choose Item ® Item details. You will find the storage bin description in the Storage Bin field. Printing the Picking List There are three ways in which you can start printing the picking list: Directly during delivery processing Using the Output menu option in the Shipping screen Through the worklist (see also the section Working with the Delivery Monitor). You can find general information on print control and initiation in the section Output Control. During Delivery Processing When and how the picking list is printed depends on the printing parameters that are defined in Customizing. It can be printed when you save the delivery document or automatically during the next output selection run. For this purpose, the criteria for print control must be maintained accordingly in Customizing. You can print out an individual picking list to carry out picking for a particular delivery. For this purpose, choose in a delivery processing screen Outbound delivery ® Save and subseq.func ® Output ® Picking output. This takes you to the Output from Picking screen. Here you can initiate the printing of the picking list. When Processing Shipping Output You can print the picking lists for one or more deliveries by explicitly calling up output print. To do this, choose from the shipping menu Output ® Picking. This takes you to the Output from Picking screen. Here, you can specify a delivery or a range of deliveries. To begin printing, choose Program ® Execute. You are also able to limit picking by the start date for picking. Only deliveries due for delivery are included in the picking list. The picking date is in the delivery header. It is the earliest picking date of all the delivery items. Print Control A picking list is always created at the shipping point responsible for picking. Therefore, printing is controlled for each shipping point. Control parameters can be defined in Customizing. These include whether, when, and in which language the picking list should be printed. Configure the settings for print control in Customizing.

http://education.feedfury.com/content/15594456-individual_picking_list_sap_sd_picking_without_warehouse_management.html
*******************************************************************************

请教下如果没WM，PICKING 功能能使用上吗？

---

1、delivery item category中要设置picking relevance；
2、必须要有WM或lean WM，并启用
3、设置storage type
*****************************************************************************

Sales BOM

A bill of material (BOM) describes the different components that together create a product. A BOM for a bicycle, for example, consists of all the parts that make up the bicycle: the frame, the saddle, wheels, and so on.

Process Flow
When you enter the material number of a bill of materials that is relevant for sales order processing, the system displays the material that describes the whole bill of materials as a main item. The individual components are displayed as lower-level items.

There are two ways to process a bill of materials in Sales. Once you have entered a bill of material in a sales order, the system runs pricing, inventory control, and delivery processing at:

- Main item level if the material is assembled, or
- Component level if the material is not assembled

The type of processing used by the system is determined by the item category group that you enter in the material master record for relevant materials.

Processing at Main Item Level
If you want the system to carry out pricing, inventory control, and delivery processing at main item level, enter ERLA in the Item category group field of the Sales: sales org. 2 screen in the material master record of the finished product. This means that the components only function as text items and are not relevant for delivery. The following graphic shows how a bill of material is processed at main item level.

Processing at Component Level
If you want the system to carry out pricing, inventory control, and delivery processing at the component level, enter LUMF in the Item category group field of the Sales: sales org. 2 screen in the material master record of the finished product. In this case, only the components are relevant for delivery. During processing the system automatically creates a delivery group. The latest delivery date among all the components becomes the delivery date for the entire delivery group.

http://www.sap-img.com/sap-sd/sales-bom-implementation.htm

What Is BOM Referring to SAP SD

By: Mike

BILL OF MATERIALS

We need to maintain Material master records for the BOM Item and for the components also.

The item category group of the BOM items is ‘ERLA/LUMF’ and the item category is ‘NORM’.

Creating BOM item:
- Logistics
- Sales and distribution
- Master data
- Products
- Bills of material
- Material BOM
CS01 create

Specify the data for the following fields.

Material: Specify the material for which components are to be maintained.

Plant: Specify the plant of BOM item.
BOM usage: Specify the application in which BOM is maintained (5 for SD).

Alternative BOM: Specifies the sequence of a BOM within a group of BOMs.
(L = stock item N = Non-stock item)

In the overview screen specify the components which makes the main item and the corresponding quantities and save it.
Note: During sales document processing if we enter the BOM item the system automatically determines corresponding components.

1) For the BOM to be exploded in the sales document the following customizing setting is required.

A) If the item category group is ERLA the item category of the BOM is TAQ, in the definition of which we have to specify the value A (Explode single level BOM) in the structure scope.
B) If the item category group is LUMF the item category of the BOM item is TAP in the definition of which we have to specify the value A in the field structure scope.

2) If the item category group is LUMF the system shows price for the components but not for the BOM item. For this the following customizing setting is required.

A) The item category of the BOM item is TAP which is not relevant for pricing, so the BOM item is not Priced.
B) The item category of the components is TAN which is relevant for pricing, so the components are priced

3) If the item category group is ERLA the system shows price for the BOM item but not for components. For this following customizing setting is required.

A) The item category of BOM item is TAQ, which is relevant for pricing, so the BOM is priced.
B) The item category of components is TAE which is not relevant for pricing, so the components are not priced.

While creating sales document to get the list of alternative BOMs in the definition item category of BOM item we have to check the field “Manual Alternative”

24-07-2007

ITEM CATEGORY DETERMINATION FOR BOM ITEM

SD type ITCaGr Usg HLItCa DftItCa

OR ERLA TAQ
OR NORM TAQ TAE
OR LUMF TAP
OR NORM TAP TAN
OR NORM TAN
OR NORM TAE TAE
OR NORM TAN TAE

NOTE: A – Explode single level BOM item
B – Explode multi level BOM item
CS01 – Transaction code for creating BOM Item

Statistical value ‘x’ or ‘y’
Make TAP relevant for pricing but values for statistical only.

http://www.sap-img.com/sap-sd/what-is-bom-referring-to-sap-sd.htm

Pricing Customization For Sales BOM

What are the steps of customization to pricing for header level or item level then?

By: John

You can create a sales bom, and price it at header level or sub level.

If you want to assemble the products and depending upon the assemblies you want to price. For eg. if the customer asks for a certain combinationa of Material A, B and C respectively, then you create a Material Master record Material D with item category group as LUMF. While the Materials A, B and C are created with standared item category groups NORM only.

Then create a sales BOM using Tcode CS01 and enter the following details:
Material : Material D
Plant : Plant in which you created the material.
BOM Usage : 5 (Sales and Distribution)
then give the Materials A, B, and C and give their respective quantities.

Before you have to create pricing condition records for Materials A, B, and C.
Then configure the item categories ( T - code : VOV4).
When processing the sales order, just give the Material D and the system will pick up the corresponding assemblies for that material and populate in the order.
The item category for the header item will be TAP and the item cateory for the items will be TAN.

In this cas the Material D is called as the higher level Item , and all the assemblies are called as the sub items. Here the subitems are relevant for pricing and delivery where as the header item is not relevant for neither pricing nor delivery. It just acts as a text item.

This type of configaration of BOM is known as pricing at item level. This is used when you dont know what quantities of assemblies the customer is going to order and if the price of the assembly keeps varies.

There is another way of configaring BOM which is pricing at header level. The difference is that the Material Master D has to be confugured using the item category group ERLA.

Creation of BOM is same.
But you need to maintain the pricing condition record for the header item.

The item categories in this case would be
Header item : TAQ
Sub item TAE;
Where the header item is relevant for pricing and delivery. and subitems are not relevant for neither the pricing nor the delivery. Depending upon your requirement you configure accordingly.

In Summary:

-->Befor going to create sales BOM you need to create:
Master data for that Header Material and Components in the MM01 transaction.

-->If you want Header price you create Header Materil with ERLA Itemcategory group.

-->If you want pricing at item level you create header material with LUMF Itemcategory group.

-->To create Sales BOM go to the transaction CS01 there you give enter the data

Header Material which you have created in the MM01 transaction.

Delivering Plant.

BOM Usage as '5' (Sales and Distribution)

***Then proceed with enter system will take you the BOM detail screen here you maintain the details of the components (How many components you need to make a Header material)

-->Check the item category determinetion settings in the transaction VOV4.

-->Maintain the Pricing procedure according to that.

-->Now you can create sales order with the BOM material

http://www.sap-img.com/sap-sd/pricing-customization-for-sales-bom.htm

How to Know that Sales BOM is working or not?

I have set up a sales BOM. How do I know or test that is is working or not?

Once you enter a material (for whch you have created a BOM thru CS01) in the sales doc another material pops under the main material line item as a sub-item (s). If it doesn't then your BOM isn't working.

In my experience BOMs work if all maintenance has been done properly.

A number of things to check is:

1. The bom hasn't been defined for the plant used, or you haven't defined the plant in SO.

2. Main item category - has BOM application SD01 been assigned to it?

3. Item categories for main items and sub-items have not been mainteined properly.

4. Sales items maintenance - You should assign item categories for BOM header items and sub-items to a specific sales doc.

5. Has the BOM itself been configured properly (i.e. right plant, BOM usage '5')?

6. Are you trying it out on an order created after all BOM maintenance was done?

7. Also , what's the 'Structure scope' set as? Anything except C may be useful here? We have that set to A, since our BOMs are all single-level. You could set it to B if BOM are configured multi-level.

Those are probably main reasons why BOM shouldn't work. Apart from that, just re-check your whole config - the truth is out there somwhere.

http://www.sap-img.com/sap-sd/how-to-know-that-sales-bom-is-working-or-not.htm

ITPUB

“

訂單BOM: 是實際生產時用的BOM, 在標準BOM和銷售BOM基礎上增減物料的BOM
銷售BOM: 是為特定客戶設定的BOM, 在主檔數據層次上的BOM, 在生產時是帶到訂單BOM中去的.
標準BOM: 是公司為標準生產的BOM, 在主檔數據層次上的BOM, 在生產時是帶到訂單BOM中去的.

訂單BOM >= 銷售BOM >= 標準BOM

一般使用中:
訂單BOM是在銷售BOM的基礎或標準BOM基礎上添加部分物料或減少或修改實際需求數量,
銷售BOM是在標準BOM基礎上增加特定客戶需要的BOM, 例如顏色,
標準BOM是公司在標準生產中使用的BOM, 通常由工程設計BOM產出再進行修正, 在SAP的標準成本計算是需要用到的.
工程設計BOM(應該很少公司用)是工程設計的BOM, 即將工程師畫的爆炸圖進行系統化.
SAP還有幾種BOM.

標準BOM維護: CS01/CS02/CS03, 查詢CS12
銷售BOM維護: CS61/CS62/CS63, 查詢CSK2
訂單BOM維護: CO01/CO02/CO03


銷售BOM使用前提是產品必須是MAKE TO ORDER, 否則系統在展開BOM時只會拿標準BOM, 不會拿銷售BOM的數據.

標準BOM的表: MAST
銷售BOM的表: KDST
訂單BOM的表: 沒有, 我的理解就是RESB中工單需求清單”

“KMAT 可配置物料的销售BOM问题

物料A超级BOM的顶层物料，A包含B,C; B 包含D，E； D包含G,F。现在SO里输入物料A，系统只能带出第一层物料B,C，孙层以下物料不能带出。CS03.MM02均察看， 包括SO VIEW和MRP VIEW，均无误。请高手指教问题可能出现在哪里？”

--

BOMs的例子：

所有你想要在销售凭证中控制的BOM items都必须标记为‘relevant for sales’；

当使用BOM usage 5创建的BOM中的所有项目会自动标记为销售相关；

在销售凭证的Item category中作了适当的设置之后，你只需要输入BOM的料号就可以将BOM中的所有组件COPY到销售订单中；

BOM以main and sub-items 的形式出现在销售凭证中，系统自动展开BOM为组件生成子项目；

在销售凭证中展开BOM：

在销售凭证中，Item Categorys控制BOM的行为，配置时，你为销售凭证中的BOM的main和sub-item定义和分配item category；

在main item的物料主记录中定义的item category group定义了哪种item category分配给了main item；

为了判定销售凭证中BOM要展开到什么程度，需要为main item定义item category结构的广度extent；

--

__________________

--item cat


Order BOMs for Variant Configuration
http://help.sap.com/erp2005_ehp_04/helpdata/EN/41/c18342350411d3b460006094b9d648/frameset.htm

pro forma invoices

Definition

An invoice that is created on paper for exported goods to provide the customs authorities with evidence of the cost of the goods.

Use

When you deal in export, you may need to print pro forma invoices. They are used to give the importer or the responsible authorities in the import country details about forthcoming shipments.

Structure

A pro forma invoice appears exactly the same as a customer invoice. The difference is that this invoice does not need to be paid. Therefore, the system does not forward data to Financial Accounting (FI). No statistical data is created on the basis of pro forma invoices.

You can create pro forma invoices on the basis of sales orders or deliveries (see the following figure).

The following billing types are available for pro forma invoices in the standard version of the SAP R/3 system:

Billing Document Type	Reference document
F5	Sales order
F8	delivery

Processing pro forma invoice differs from processing normal invoices in the following ways:

• Goods issue is not required before you create a delivery-related pro forma invoice.
• You can create as many pro forma invoices as you like for a sales order or a delivery because the billing status in the sales order or delivery is not updated.
• Data from the pro forma invoice is not passed on to financial accounting.

http://help.sap.com/saphelp_45b/helpdata/en/dd/5610c9545a11d1a7020000e829fd11/frameset.htm