Consignment Sales Process in SAP zz

http://www.sap-img.com/sap-sd/consignment-sales-process-in-sap.htm

The consignment process in SAP standard consist of four small processes:

Consignment fillup (send materials to customer consignment).
Here you have a consignment fillup order and a consignment fillup delivery.

Consignment issue (issue materials from customer consignment to the customer).
Here you have a consignment issue order, consignment issue delivery and a consignment issue invoice. (the flow is very similar to a normal OR flow, but the materials are issued from the consignment stock instead of plant stock unrestricted).

Consignment return (return materials from customer ownership to customer consignment).
Here you have a consignment return order, consignment return delivery and a consignment return invoice. (the flow is very similar to a normal RE flow, but the materials are returned to the consignment stock instead of plant stock returns).

Consignment pickup (pickup consignment stock and move it to plant stock).
Here you have a consignment pickup order and a consignment pickup delivery.

Note that in consignment fillup and consignment pickup there are no invoices since there is no change of ownership for the materials.

How to perform a consignment order?

In consignment orders you are allowing the stock to sit in your customer location. Once he informs that he used the stock you will invoice him. If he returns the stock you will accept the stock to take it back.

It is defined in 4 steps.

1. Consignment fill up:
Sales document type is KB
Item category KBN
shedule line category E1

In this step, you are not invoicing the customer. document flow is sales order ---- delivery item category. It will not be relevent for billing and pricing because you are not charging money for these goods in this step.

In schedule line category, you will set movement type 631 & set for availability check and TOR.

2. Consignment Issue.
Once the customer informed you that he used all the goods or partial goods then you will create consignment issue for used goods.

Sales document: KE
Item category: KEN
shedule line category: C0 or C1

Here you are invoicing the customer(because he used the goods). you are assigning the delivery documnt and billing document to the sales document.

In item category, you are setting relevent for billing, pricing, special stock.

In schedule line category, your setting is 633 movement type, relevent for availability check & TOR.

3. Consignment Return:
Customer found that some goods are damaged or he not able to sold the goods he want to send it back. that you are creating this document.

Sales document type: KR
Item category: KRN
Shedule line category: D0

You will assign delivery document and billing to sales document. you will create return order, return delivery, return billing.
Your setting item category relevent for billing, returns, pricing, special stock.
Your setting schedule line item category: 634 movement type, NO availability NO TOR.

4. Consignment Pick up:
Even if you create the consignment return the goods are not come to direct to your plant. For that you need to create consignment pick up. here the owner ship is not changing so you do not need to create billing.
Assign retrun delivery to sales document type.

Sales document: KA
Item category: KAN
schedule line category: F0 & F1

Your setting item category relevent for returns. any shedule line category relevent for 632 movement type, MRP, availability check, delivery.

Now you check your plant stock. Stock will increase. *-- Ugameswara Rao

Customer Complaints Procedures zz

http://sapdocs.info/sd-related-topics/customer-complaints-procedures/

If Customer Returns the Goods:

-VA01: Return Order (Order Type: RE) (Item Category: REN) & enter, Create Return Order with ref to Sales Order No. Give order no & click on Copy (F5) and change the order quantity say from 50 boxes to 20 boxes.
-VL01N: Return Delivery
-VL09: Goods Reversal.

If Customer Wants Refund For the Amount:

-VA01: (Order Type: RE), (Item Category: REN), (with ref to sales order)
-VL01N: Return Delivery
-VL09: Goods Reversal
-VA01: Credit Memo Request (Order Type: G2), (Item Category: G2N), (with ref to Return Order, please remove billing block)
-VF01: Credit memo.
-If the customer wants refund for the amount, enter a credit memo with ref to the return.

If Customer Wants Replacement:

If the customer wants replacement product, enter a free of charge subsequent delivery with ref to the return.
-VA01: (Order Type: RE) with reference to Sales Order.
-VL01N: Return Delivery
-VL09: Goods Reversal
-VA01: Free of charge Subsequent Delivery (Order Type: SDF)
-VL01N: delivery
-LT03: picking
-VL02N: goods issue

The Customer Does Not Send the Goods Back:

-If the customer wants a replacement product, you create a free of charge subsequent delivery with ref to sales order
-If the customer wants a refund, you enter a credit memo request, with ref to the sales order or invoice.
-VA01: credit memo request (G2) or free of charge subsequent delivery (SDF) with ref to sales order. For SDF there will be delivery, picking, goods issue.
-VF01: invoice

For Damaged Replacement:

-VA01: free of charge subsequent delivery (SDF) with ref to sales order
-VL01N
-LT03
-VL02N

Debit Memo Request: (Order Type: L2) & (Item Category: L2N)

A debit memo request is a sales document used in complaints processing to request debit for a customer. You can create a debit memo request if the prices calculated for the customer were to low. Remove the Billing Block.
-VA01: debit memo request with reference to invoice or order
-VF01: debit memo

Invoice Correction Request:

A sales doc used in complaints processing to correct the quantity or price of one or more items in an invoice.
Each invoice correction request that is made in ref to an invoice contains 2 items for each item in the invoice (you cannot create an invoice correction request in ref to a sales or delivery doc type), viz First- credit item & Second Debit item. These contains the same value and quantity. The first item is the copied value & quantity copied from the invoice, this item appears as credit item. The second item is the debit item, which represents the correct quantity &/ or the value.
If you want the system to generate a credit memo for a +ve amount, and a debit memo for a -ve amount, you need to set an additional sales document type in customizing, for e.g., ZRK1 (invoice correction request for debit memos). You can change these settings in customizing under Sales ® Sales Document ® Sales Document Header ® Define Sales Doc Types in the “Sales Catalog Field”.
If the invoice correction request is characterized as a credit memo request, that is, the doc type RK has the characteristic as ‘K’ in the sales doc catalog field & has order related billing assigned to it in the form of G2 or credit memo, the system creates a credit memo for +ve value. For debit memo the characteristic will be ‘L’ & has order related billing assigned to it in the form of L2, the system creates a debit memo for a -ve value.
-You create invoice correction request with ref to an invoice.
-Price 100
o 110: credit memo
o 90: debit memo
-VA01: (Order Type: RK) with ref to invoice
-VF01: automatic credit or debit memo.

Free of Charge Delivery: (Doc Type: CD)

-VA01
-VL01N
-LT03
-VL02N
-When you create a free of charge delivery you must enter a value in the order reason field or the system informs you that the doc is incomplete.

Free of Charge Subsequent Delivery: (Order Type: SDF) (Item Category: KLN)

To create a free of charge subsequent delivery, you have to refer to an existing sales doc, such as: sales orders, contracts, contracts release orders.
You do not have to use create with ref to free of charge subsequent deliveries, if you enter the order type & choose enter, a dialog box will appear where you can enter the no of the order to which you are referring. No invoice is created or necessary, as the items are free.

Returns: (Order Type: RE) (Item Category: REN)

A return is a sales document used in complaints processing for when a customer sends goods back. You can create the return in one of the following ways: without ref to an order, with ref to an invoice, with ref to contracts, contract release orders, billing doc.
It may be worthwhile ensuring the return order reason was entered on the sales doc. Thus, it may be necessary to add this in an incompletion proc.
It is advisable to indicate a shipping cond that is specifically used for returns. This is useful when running del due list.

Credit Memo: (Order Type: G2) (Item Category: G2N)

A credit memo request is a sales doc used in complaints processing to request a credit for a customer.
The credit proc generally follows 2 business procedures; the first being the scenario where the customer returns products previously purchased & requires a credit. The second general form of credit proc is when the customer is credit without ref to a return (goods not returned or customer overcharged).

You can also set a mandatory that the credit memo request can only be created with ref. You can create a credit or debit memo request with ref to an existing order, with ref to an existing order, with ref to an invoice, with ref to contracts, contract release orders, billing doc.
You may not wish to credit for every thing, such as the entire freight charge from one invoice. You can instead have a new pricing proc in the credit memo request that is similar to the standard pricing proc you use, but not have the freight condition type. Thus the standard values are copied over, excluding freight.

Sales Order Type 配置要点详解 zz

　　Sales Document Block：控制这个文件类型是否已经被冻结。有三个选择，如果该字段为空则表明这个文件类型没有被冻结，如果为A，则表明这个订单类型只能被自动创建，例如回扣的处理，如果选择为X，表明这个文件类型已经被冻结而不能再用了。
　
　 　Sales Document Indicator： 只和表TVAK有关No.range int.assign： 确定该文件类型的内部号码段No.gange ext.assign： 确定该文件类型的外部号码段Item no.increment：行项目编号的增加量Sub-item no.increment： 子项目编号增加量。
　
　　Reference mandatory： 强制参考。如果文件类型对这点进行了配置，在创建销售订单时，系统会弹出窗口强制要求输入参考号码，并且指定是参考号码的类型，如参考报价单，参考询价单，参考销售订单等等。
　
　　Check division： 配置检查订单中行项目产品组和抬头产品组不同时的信息类型，如果这个设置为空则没有信息出现，如果为1，则有对话信息出现，如果为2则有错误信息出现，表明该文件类型抬头的产品组要和行项目的一致。
　
　 　Material entry type： 物料输入类型，目前怀疑和限制订单的物料输入有关，如果这个字段为空表明订单一定要输入物料Item division： 决定订单ITEM中的DIVISION的来源。如果这个选项打上勾，则表明ITEM的DIVISION是来自MATERIAL__ master，如果不打上则来自订单的抬头。这一点和CHECK DIVISION构成了cross-division sales的配置点。
　
　 　Probability： 用来确定成为订单的可能性。这一个配置，对于订单来说默认为100%并且不可更改，而对于询价或者报价来说，系统都根据订单类型的category来；默 认了一个可能性，但这个可能性可以更改（在SD DOCUMENT里）。这一个设置也决定了系统如何传递物料的需求。例如一个报价单的类型为QT，在创建报价单时物料A的净价值是100USD并且 Probability为50，而物料B的净价值为200USD并且Probability为25%，因此整个报价单成为订单的可能性为：（100__ * 50% + 200__ * 25%） / （100 + 200） = 50%如果物料A的Probability为50%，则报价中的100个A物料会产生50个需求量在创建报价单时，系统也会把客户主数据中的可能性考虑在 内（见SOLD-TO PARTY客户主数据中的SALES AREA DATA - Order probability of the item）。如果该订单类型的可能性设为50，而客户主数据的为80，则在创建报价单时，行项目的可能性为80 / 2 = 40，表明该报价单有40%的机会成为订单。
　
　　Read info record：如果这个选项选定，则创建订单时会读取customer-material （TCODE：VD51）的数据。
　
　 　Check credit limit：信用检查。用来控制系统是否进行信用检查和对检查结果作出什么样的反应。这里的选项有五个：1/没有进行信用度检查2/进行简单的信用检查并 对超出信用额度显示警告信息3/进行简单的信用检查并且对超过信用额度显示错误信息4/进行简单的信用检查，如果超过信用额度则冻结交货5/如果系统实行 信用管理，则自动执行相应的信用控制自动的信用检查具有不同的检查方法，例如动态信用检查和静态信用检查，或基于最大的订单价值检查。在动态检查和表态检 查中，信用状态是所有open order\\open delivery\\open 的应收款来统计出来的。如果需要执行自动信用控制，则在订单类型里选择D.对于简单的信用检查，系统用信用状态和付款方的信用额度作比较。信用状态是从所 有open item的净价值统计来的。
　
　　Credit group： 信用组。定义该文件类型是属于那个信用组的。这一个配置使你能够根据信用组合并不同的文件类型，从而使得信用管理更加有效。
　
　　Check purch.order no： 检查客户的采购订单是不是已经在其他的订单中存在，如果是则有警告信息出现。
　
　　Enter po nmber：用来配置订单是否需要输入客户采购订单号码。
　
　　Output application： 看起来应该是和文件输出相关，定义这个属于这个文件类型的订单在输出时采用什么格式。
　
　　Commitment date： 作用不明白Screen sequence grp：用来定义该文件类型的屏幕顺序。
　
　　Display range： 定义行项目显示方式。
　
　　Incomplete procedure： 定义当相应的SD文件有些数据没有输入的时候系统的处理办法。这个配置在文件里型里是不能更改的，因为在basic function-log of incomplete item（VUA2）里已经做了配置了。
　
　 　FCode for overv.scn： 设置进入显示凭证界面时的VIEW.如，选择了UBST后，在显示销售订单时，一走入去看到的就是ordering party这个VIEW. Transaction group：定义这个文件类型是那一种业务（报价，询价或销售订单）。例如OR的transaction group是0，属于订单，因此只能用VA01来创建这类型的文件，而QT是属于2的，报价单类型，因而只能用VA21来创建。
　
　　 Quotation message： 配置报价单和销售订单之间数据是如何检查的。有下面几个选择：1/不检查2/在抬头层面进行检查，在创建销售订单时，系统检查报价单，如果发现要抬头信息 相同的报价单出现则会报信息告诉用户有报价单存在。抬头信息是指销售区域、sold-to party， ship-to party， po等。
　
　　3/在行项目层面检查。除了上面抬头信息外，也检查订单中的物料号是否和报价单的相同。
　
　　4/在抬头层面检查，如果发现唯一一个相同的则直接把报价单COPY过来。
　
　　5/在行项目上层面检查，如果发现唯一的则直接把报价单COPY过来6/在抬头层面上检查，如果发现多个则显示一个LIST让用户选择，如果只有一个则和上面第4点一样。
　
　　7/在行项目上检查，如果发现多个报价单则显示一个LIST让用户选择，如果只有一个则和上面第5点一样。
　
　 　Doc.pric. procedure：文件的价格流程。任何一个销售区域都要设定一个定价过程（可以在视图t683v里看到每个销售区域的定价过程）。在创建订单时，如果 系统发现这个地方的配置和t683v不一样，则会报错误信息：No pricing producer could be determined.T683V可以在sales—sales document – contract –define and assign pricing procedure for value contract里配置。
　
　　Outline agreement message： 和Quotation message大致一样。但这两个代表团点要一样，因为系统会把Outline agreement message和Quotation message作为一个combination来看的。
　
　　Add ref. to all contracts partner is authorized to release：用来搜索所有的合同。
　
　　Status Profile：Message mast.contr.：有点类似上面的Quotation message.但应该只和CONTRACT的文件才有用处的。
　
　　Prodatt.message： 是否允许更改product attribute.product attribute是指什么不太明白。
　
　 　Alternative sales document type 1 / Alternative sales document type 2：在文件的处理中可能会会改变一些文件的文件类型。这个配置点这是作为更改文件类型的限制条件。详细的看F1. Incomplete message：当文件的信息不完整时会不会出现信息提示Variant： 设置变式Corr.delevery type： 集合运输类型。不明白其作用。只作用于scheduling agreement Delivery block： 冻结运送。
　
　　 Use：物料的用途，只作用于scheduling agreement. MRP for DelSch Type：Delivery type： 运送类型Immediate delivery： 马上运送。有三个选项：1/订单和运货单分开建立2/订单和运货单同时建立3/订单和运货单同时建立，但前提条件时送货时间是当天Delivery block： 冻结运送Shipping condition：运送条件。在客户主记录里也有这一个字段，一般来说创建的SD文件会取sold-to party的Shipping condition作为默认值，但是如果在相应的文件类型里也设置了这一点，则文件类型的Shipping condition会作为默认值而覆盖从客户主记录里的。如果在文件类型里没有作配置则取客户主记录里的。
　
　　Shipcostinfoprofile： 作用不太明白Dlv-rel billing type：配置和运货相关的发票类型（发票参考运送单）
　
　　Cndtype for line item：Order-rel.bill. type：：和订单相关的发票类型（发票参考销售单）
　
　 　Billing plan type：发票计划类型。分为定期性开票和milestone开票。定期性是指一些租金或者维护收入的发票，而milestone是指一些开票项目，例如 和客户订立年度的销售项目，半年时付40%，结束时付60%. Intercomp.bill.type：公司单发票类型Payment guarantee procedure： 付款程序监督。用来定义用那一个程序来监督付款。和Receivables risk management相关。
　
　　Billing block：冻结开票Payment card plan type：其作用不清楚。但凡是用到付款卡结帐的文件类型，都需要定义这个配置，否则不对用卡结帐。
　
　　Checking group：付款卡检查组。
　
　 　Lead time in dates： 设置request delivery date比现在的天数多几天。例如今天是20060118，如果这个设置为20的话，那么系统会把request delivery date自动默认为20060215. Propose delivery date： 定义系统是否建议一个运送时间request delivery date.如果打上勾则会根据Lead time in dates这个来建议一个时间，否则创建订单时要人手输入运送时间。
　
　　Propose po date：打上勾则系统会默认今天是PO日期Date type： 时间类型Prop.f.pricing date：系统默认一个pricing date，但可以人手在订单里更改。
　
　 　Propose valid-date： 定义该文件生效的日期。有三个选择：1/不建议2/建议今天3/建议下个月第一天PricProcCondHeader：定义CONTRACT的抬头定价 条件PricProcCondItem： 定义CONTRACT的行项目定价条件Contract data allowed：决定CONTRACT HEADER和数据会不会COPY到ITEM上。
　
　　Followup activity： 跟进动作的类别。定义属于这类文件类型的合同其后续动作是什么，例如一个租金合同，后续动作可能是一个销售信件等。Followup activity可以在CAS里进行相应配置。
　
　 　Contract profile： 合同的形式Subseq.order type：后续销售订单类型Billing request：要求的发票类型Check partner auth.： 检查一个PARTNER是否有资格成为一个RELEASED CONTRACT的PARTNER.当你在释放一个合同时，系统会检查这个合同里的PARTNER有没有资格成为一个SOLD-TO PARTY. __update lower level contract：更新低阶合同Group reference procedure：数据从主合同（MASTER CONTRACT）复制到层次较低的合同时的复制程序Business transaction：和APO相关的ATP检查

http://edu.chinaitlab.com/qt/773624.html

销售与分销 zz

http://blog.chinaunix.net/u1/50618/showart_1883117.html

一、R/3销售和分销系统主要特征及系统模型：
　　SAPR/3SD强调销售与分销需用世界一流的方法服务于全世界用户。SD是一种处理过程驱动的应用，全面集成于R/3系统中。

　　1、SD主要特征：
　　*多语种、多货币处理
　　多企业、多 语种、多种货币的销售订单处理功能，使你能用一种语言、输入一个指令便可进行一次国际间的业务。应用R/3SD与其它国家的伙伴进行交易时，可以自动转换 成其它国家语言和货币。通过确定国界，每一个伙伴收到的业务内容是用相应的本地语言和货币来表述的，这将有助于服务全球市场。
　　*微调技术
　　微调技术能使SD适应你企业功能的需要。通过微调订单类型，你可以很快地调整系统以满足你不断变化的业务需求，使你的销售额不会出现大的滑坡。90年代商业过程的不断变化属于正常情况，SD将能使你在不断提高的基础上，而不是在初始运行的基础上重组你的商业过程。
　　*定价灵活性
　 　R/3 SD的定价灵活性和完备性很强，以致于1995年1月由BenchmarkingPartnersofCambridgeMass.对其进行评价时，叙述 这一能力"是世界级的，甚至可以支持最富挑战性的行业"。你可以利用有关规则来定价，并可以存储最复杂的定价情况。R/3SD使你的用户服务代表从复杂的 定价劳苦中解脱出来，使他们更致力于本职工作：销售和服务。随着SD定价的深入，你将在竞争中越来越主动。
　　*订单状况和顾客服务查询
　　订单状况/顾客服务查询使你很方便地从你系统中获得有关订单情况的大量信息。通过系统你甚至可以用图表表示订单的进度。你公司的客户服务人员在客户问询之前便可以回答有关订单状况等问题。

　　*优化的订单输入
　　在日常订单处理中，简单的一屏信息就足够了。输入客户名、产品、数量。其它都由主数据来处理。基于有效性和信贷核对，你只需点击一下鼠标，订单便被登记入库。

　　*按客户产品号码的订单输入
　　R/3订单输入允许你利用客户的产品号码（而非你自己的产号码）进入一个客户订单。一旦你在一个客户材料信息记录中存储了你的产品号码和你客户的产品号码，你可以简单地记录该客户的号码，该系统将参照你的产品号码，使你在订单输入中节省时间和劳力。

　　*大量的订单输入
　　大量的订单输入功能允许你象处理一份简单文件那样记录具有最大的销售订单，与此同时，在那个订单内，你仍可以快速地移到一个客户部件号码或一种专用产品号码的登记中。

　　*项目独立
　　R/3SD可以象处理一份单独的订单那样在一份销售订单中处理每一个项目，因此将使你具有最大的灵活性来处理订单信息和保持客户满意。

　　*折扣处理
　　SD中的折扣处理给了你多样选择，包括基于产品、产品组、客户及购买群体的折扣。该功能主要设计用于客户包装货物行业，一般遵循折扣原则。让SD将你开票中的不便减到最小，使你的员工去做其它更有意义的工作。

　　*EDI
　　EDI是销售中的一个关键部分。你的业务需要应尽可能地 以最快捷的方式进行传递－如电子数据。使用EDI意味着电子传输的数据立即可以为用户所获得，并可以应用于你的R/3SD系统中。SD中的EDI接口将确 保你的销售运作具有最快的速度和集成功能。EDI甚至可以激活一个工作流过程。例如，由于无效的产品号、或者因信用持有、或者因其它判断标准等而激活一个 销售订单的工作流事件。

　　*销售信息系统
　　R/3的销售信息系统允许你收集、合并和使用销售 与分销活动中任何类型的数据。借助研究实时数据并将它与计划值比较，使现场销售活动更趋于及早决断，随后采取行动解决问题或充分利用开发机遇。你可以迅速 从SD大量数据中筛选出最重要的信息，并且准确地加工出你的任务所需要的信息。

　　*相互参照能力
　　系统中相互参照功能允许你基于不同的准则，如客户 的产品号、通用产品代码（UPC）或失效产品等，来确定合适的产品号码。你还可以依照基于包装代码选择原则的清单来确定合适的产品。例如，一个客户可能不 提供将插入到任何产品包装中的随赠产品，那么在系统找到这种替代品之前，这些包装代码将不列在选择的清单中。

　　*可用性检查
　　在完成订单输入之前，可用性检查主要是核对你手边是 否具有足够数量产品以满足新订单需求。如果你手边没有足够产品能很快发货，那么可用性检查将实时确定何时可获得所需的数量。你可以规定是否你的系统基于可 用的约定(ATP)数量来进行检查，或者它是否按照计划来进行检查。系统还考虑补货的提前期。你甚至可以检查多个工厂的可用性。所有这些都有助于你的组织 机构对潜在的交货瓶颈的最新信息，做出销售订单的决策，并且在改善客户满意程度的同时，帮助你按计划完成商业过程。

　　*与物料管理和财务会计的集成
　　与物料管理系统集成后，当你生成一 份销售订单包括第三方项目时，该系统自动在采购功能中生成采购申请。这些采购产品可能被直接送到客户处，或被送到仓库，以便与订单上其它产品一并装运。一 旦你分配销售部门和工厂时，便开始了与财务会计系统（R/3FI）的集成。在一个公司代码内，保留若干个销售部门可能会十分有效，一个单一工厂可以被分配 若干个销售部门。当你进行这些分配时，便生成了R/3系统中自动财务数据的移动和连接。这就是决定了R/3SD具有"世界级"声誉的系统集成。

　　*批量控制
　　SD中的批量控制功能允许你在销售订单上分配单个批量，或者等到在确认批量之前装运处理时。SD将进一步通过检查以确保你的批量细目能满足客户的清单需求。SD还通过检查以确保满足截止日期以及客户的任何其它需求。

　　*服务管理
　　SD中的服务包含一整套客户服务功能，包括呼叫管理、担保管理和服务合同处理等。它还包含出租或采购设备的维护和修理合同，并允许你记录全过程，确保即时的服务响应和准确无误的开票。

　　*退货、信贷和借贷处理
　　SD中的退货、信贷和借贷处理功能主要处理由客户归还的物品。意见收集功能包括不管有无优先销售交易的参考，均免费传送有关退货、信贷和借贷备忘录。该系统将通过处理交货和开票冻结来帮助获得精确、有效的交易过程，以备另一部门需要查阅这些交易过程时使用。

　　*信贷限额检查
　　R/3SD在信贷检查方面赋予你极大的灵活性。你 可以在销售周期中的任何时间内，可以从订单收货到交货，利用信贷限额检查功能。你还可以对集中或分解的运作过程或任何过程之间建立信贷检查。对于一位已知 客户，你可以定义一个总的限额和/或对一个信贷控制范围定义特定限额。你还可以在限额超出时确定系统的响应。

　　*产品结构
　　可配置的产品是另一个具有极大灵活性的领域。当你在销 售订单上输入一个可配置的产品时，R/3SD便自动调用可配置编辑器，你可以很容易地从预定义配置选项中进行选择。你可以定义独立的选项或生成具有多种配 置层次的物料系列。你甚至可以对配置的产品中的关键部件实施可用性检查。

　　*外贸
　　不断变化的外贸规定和关税对任何一个国际性组织都面临着艰 苦的挑战。这些约束将影响你的整个供应链，从原材料到产成品、库存和财务会计。R/3SD的外贸功能可以使你有效地完成这些需求，包括支持EDI接口用于 外贸信息，出口许可证的灵活管理，对当局的自动申报，以及最惠国条约的陈述。R/3SD将确保国境界限不再是你的组织机构发展的障碍。

　　*装运和运输
　　R/3中装运和运输管理使SD与R/3系统中物料管 理和财务会计模块紧密结合在一起。因此，不论你在系统何处，当前装运信息可以控制在你的手中。该装运模块除了对灵活的装运出口提供了综合支持外，还提供了 对外贸处理过程、装运截止日期的监控、装运的灵活处理的综合支持，以及对运送、包装和装卸的综合支持。

　　2、该系统具备的主要功能：
　　*销售支持
　　*询价
　　*报价
　　*订货
　　*销售/交货期管理
　　*运输
　　*发票处理
　　*销售信息系统维护

　　下面分别简要阐述各模块功能的实施:

　　1、销售支持(CAS)
　　R/3销售支持部件可帮助理你的销售和市 场部门在对现有的客户提供支持的同时发展新的业务。销售支持将提供一个环境，使得所有的销售人员，包括现场销售人员和办事处的职员，都能提供和存取有关客 户、潜在客户、竞争对手及其产品、联系人等方面的有价值的信息。销售支持部件的功能是既作为有关销售和分销的各方面信息的源，又作为获取业务的起动力。
　 　使用R/3销售支持中的工具在销售支持环境中，你不但可以创建直接邮寄去发展新的业务，而且能巩固已有的客户群。在已存入系统的销售信息的基础上，你可 以创建有关客户和潜在客户的地址清单，他们是你发动的直接邮寄攻势的目标。有关客户、潜在客户，竞争者以及其产品和销售物料方面的背景信息是作为主数据来 存储的。
　　R/3SD的销售支持要素为客户服务和你的销售及市场人员的商业活动提供了工具和处理手段。SD模块中的这一部分紧密地与SD的销 售、发货和开票功能连接在一起，用以提供日常商业事务的附加的必要手段。销售支持使售前功能得以简化和自动化，使人们摆脱了重要但很繁重的日常工作。
　 　售前支持将帮助提供对现有客户的服务，而这些客户也将有助于新的商业发展。使用SD中的销售支持，结合现场销售人员和其它职员能有助于掌握有价值的信 息；这些信息将涉及客户、销售项目、竞争对手和他们的产品，以及合同。销售支持具有作为SD的信息资源和作为一种获取新的商业动力的功能。
　　销售支持功能将使现场销售人员的工作纳入到组织的信息流中。SD能快速地作出由销售人员收集来的市场信息，这些信息将为销售处的办事人员所用。通过R/3SD可获取的通信媒体包括：
　　*使用笔记本电脑或其他工作站与R/3SD连接
　　*使用移动电话系统和笔记本电脑与R/3SD连接
　　*使用R/3系统的部件R/Mail进行信息传送
　　*通过电信服务实现连接，诸如EDI或传真
　　*打印的文件

　　2、销售信息系统(SIS)
　　SD的最重要工具之一就是销售信息系 统。这个实时数据的共用库能方便地为你提供客户一种更高档次的服务，给你一个竞争的优势。精确的、实时的数据也意味着你的商业活动在效益上将有显著地提 高。在SD中所有的销售、发货和开票处理提供的信息将通过中央R/3SD销售信息系统输入到销售支持中。这将包括销售的一揽表和销售订单的统计资料。
　 　销售信息系统能提供广泛的功能用于制定有关销售信息的报表。这些报表能协助你制定销售和商贸策略以及分析计划的结果。例如，通过销售处和销售组你可以制 定出一个有关收到的订单的详细报表。你还能够为专项客户着手一份有关全部公开销售活动的清单，而且能检查各个销售订单的历史。

　　3、销售
　　R/3SD中销售功能的突出特点为:
　　*SD的订单输入和配置能力被一家独立的咨询公司评为"最佳等级"。
　　*SD的定价能力也被一家独立的咨询公司评为"世界级"。
　　*在最大限度地扩大你成功的机会中，与其它R/3系统模块集成SD销售功能，将使每一销售作业阶段的数据输入工作量减至最少。
　　*先进的信贷管理能力可使你的销售风险减至最小。
　　*精细的定价可以保持你工作的灵活性和竞争性。

　　任何大组织的销售部门都要开展广泛的销售活动，而每一项活动都包含了大量自身的的各种变化因素。这些活动从处理报价申请（RFQS）、报价单和销售订单到定价、信贷和产品可用性。这项工作中任何一步稍有疏忽都可能造成订单的丧失，甚至损害与良好客户的关系。
　 　最好的情形是，上面提到的所有的活动，甚至更多的活动都进展平稳：一个过程和下一个过程可以衔接起来，数据输入减至最少而误差则被消除。在销售中，你可 以通过R/3SD来实现这些过程。在增加更多的SD的能力以前，分析人员们称R/3SD具有"杰出"的订单输入结构和定价功能，现在SD功能齐全，可为你 所用。
　　R/3SD的销售处理可以提供：
　　*询价、报价和销售订单的处理和监控
　　*广泛的拷贝功能可以将在订单输入中的误差和重复劳动减至最少
　　*客户定义的凭证类型用于所有销售订单
　　*可用性检查(ATP)
　　*交货计划
　　*发货点和路线确定
　　*包括本国和外国货币税金确定在内的定价
　　*客户信贷检查
　 　不论你的销售简单还是复杂，SD均能满足你的需求。SD能轻易地支持大多数事务和作业。即使你的需求相当复杂，你也能很容易地将该系统为你所用。 R/3SD与R/3系统的其他部分全面集成，其中包括财务会计，生产计划，服务管理，项目管理，物料管理和质量管理。这使你的SD事务可以实时工作。

　　4、询价及报价
询价和报价文件是作为关键的售前作业的指南性文件，并 且还提供用作业务信息的资料库。当客户需要有关产品和服务的信息时，你可以使用系统中的询价功能。这些文件提供有关未来客户的重要信息。当销售开始时，你 可以快速地从询价或报价文件中取出信息并容易地输入到销售的文件中。同时，SD还包括了许多用于管理和监控这些文件的功能。你可分析销售之前的文件用来衡 量市场的动向，分析丧失销售的原因，以及建立用于计划和战略的基础。
SD提供了用于查阅系统中询价和报价的分析工具。应用选择准则，你可以获得感兴趣的信息。

　　5、订货
　　R/3SD可以帮助你处理不同的销售订单，这主要取决于特殊需求。在一个屏幕上输入带有许多项目的销售订单，或利用一份扩展的订单视图来设置一项复杂的订单时，系统能适应你的需求。
　　R/3SD提供了加速订单输入过程的几种工具：
　　*复制功能
　　*产品建议
　　*面向客户的订单管理

　　6、发货
　　装运是供应链中的基本环节。装运部门的主要任务是确保对用户服务和保障分销资源计划(DRP)。装运成本是后勤成本的主要部分。所以靠SAP提供的灵活装运处理，你可提高总的成本效益且变得更有竞争能力。
　　在SD的装运处理中，有关正常交货过程的所有决策都可用下法事先作出：
　　*跟踪与用户的总协议
　　*跟踪对物料的具体要求
　　*对每一订单规定条件
　　这样做使你将装运过程合理化，使之几乎自动完成。只在需要做出决定的某种环境下才去干预它。
　　装运活动包括：
　　*通过创建交货来开始装运过程
　　*计划并监督装运过程每步工作的工作量
　　*监控产品可用性，处理延期订单
　　*分拣
　　*包装
　　*为运输计划提供目前的准确信息
　　*打印并传递装运凭证
　　*保障外贸要求
　　*货物离开你的场地时更新信息
　　*监督交货过程直到用户收到货物为止

　　7、运输
　　运输是供应链中的一个基本要素。为确保装运按计划准时发 放到客户所在地，有效的运输计划是必需的。运输成本在决定一个产品价格时起相当大的作用。为保持产品的价格有竞争性，使运输成本保持最小非常重要。运输的 有效计划和处理能使这些成本降低。销售、分销系统的新的运输要素的目标是为运输提供基本功能：
　　*运输计划和处理
　　*运费计算
　　*运费结算
　　*客户运费计算
　　*同时开出客户运费发票
　　*服务机构选择功能

　　目前，运输功能在运输计划和处理境内、境外装运领域能够满足你的需求。你可以 控制和监控整个运输处理，这个运输处理是从计划步骤直到从装运点（境外装运）或卖主地点（境内装运）分配货物到他们到达的客户地点（境外装运）或你的工厂 （境内装运）。你也可以根据自己的需要提出完成运费计算和结算的功能,而且可以选择服务机构。

　　8、发票处理
　　出具发票是销售和分销中的最后的活动。它支持以下功能：
　　*发出：
　　-根据货物和服务而发出的发票
　　-根据相应的请求而发出的借项和贷项凭单
　　-形式发票
　　*取消出具发票事务
　　*回扣的发出
　　*传递过帐数据到财务会计(FI)

　　在SAPR/3系统中，以上所列的功能采用关于出具发票凭证执行。这些出具发票凭证覆盖了一般日常业务和特殊情形下的业务两方面的要求。
　　象SAPR/3系统中的销售订单处理的所有部分一样，出具发票集成在机构结构中。因此，出具发票事务可以指派给某一特定的销售机构、分销渠道和产品组。

　　9、信贷管理
　　SAPR/3系统提供了强有力的信贷管理环境。通过集成，来自财务会计（FI）和销售与分销（SD）的最新信息使你能有效减少信贷风险，尽快解决信贷扣留（由于信贷原因而引起的凭证冻结），加快订单处理。信贷管理包括下列特点：
　　根据信贷管理的需要，可规定基于判据多样性的自动化信贷检查。你还可规定在销售和分销循环的那些临界点，应执行这些检查。
　　关键性的信贷状况，可通过内部电子邮件自动通知有关信贷管理人员。
　　信贷代表应处在这样的位置上，他能快速而准确地审查客户的信贷状况，并根据信贷政策决定是否延长信贷。

　　10、可用性检查
　　按时交货对客户是至关重要的，它甚至会影响客户 决定是否购买产品或相关服务。因此，R/3SD在订单输入时能自动地确定交付的进度。交货计划包括所有在货物发出前肯定要发生的活动。交货计划可以确定产 品的可用日期和装载的日期。当你输入客户要求的交货日期时，SD能计算出装运活动的日期。系统可以确定出什么时候产品必须获得，什么时候进行分拣，装载， 以及制定运输的计划，用以满足客户要求的交货日期。
　　运输计划要考虑到运送的时间和用于装运所需的运输提前期，甚至要涉及外国运输机械的情况。R/3SD也考虑了工作日历。例如在确定运输日期时，要考虑到货运代理商和其他的合伙人。
　　就交货和运输计划而言，该系统将确定运输时间，装货时间，分拣和包装的时间，以及运输的提前期。SD将交货处理基于若干交货截止日期而确定的，包括物料的有效日期、运输的计划日期、装载日期、发货日期和交货日期。
　　交货计划和可用性检查是相互依赖的。该系统利用要求的交货日期和客户的地点信息来确定货物在什么时候必须获得。如果货物不能满足所要求的交货日期获得的话，SD就用顺排计划表来寻找最早可以获得货物的日期，并计算出货物能送到客户手里的实际日期。
　　由于在你的组织中，销售、生产和发送状态是在不断地变化，SD在你输入销售订单时便进行一次可用性检查，以确保满足客户的需求。在发货过程中，可用性是自动重复检查的。
　　SD中的可用性检查可以确定是否产品能够获得，并确保按客户要求的交货日期交货。这项功能还提供有关库存水平，识别交货瓶颈，改善即时的业务处理，向MRP转送需求，以及改善客户服务。有两种形式的可用性检查：
　　*基于ATP数量的检查：
　　SD根据仓库的库存量、计划供应量和需求量来计算可用性。
　　*按计划来检查：
　　SD仅基于计划项目来计算可用性，而不是根据订单的数量来计算。
　　SD的可用性检查是灵活性的，而且可以包括许多不同的因素。你可以规定什么样的检查因素可被用于每项事务中。
　　这些因素包括：
　　*安全库存
　　*质量检查中的库存
　　*运输中的库存
　　*采购订单
　　*计划订单
　　*采购申请
　　*生产订单
　　*预留
　　*相关需求
　　*计划需求
　　*销售需求
　　*交货需求

　　SD通过使用你在主数据中所定义的那些时间，基于ATP数量的可用性检查还可考虑补货提前期，这个时间是订单或生产所需产品所要求的时间。
　　SD可用性检查还容许你确定是否在别的工厂中，可获得一些或全部所需产品。

　　在需求的传送中，销售环节将通知物料需求计划有关需要发送的货物数量。你可以 应用R/3SD可用性检查来做这件事。R/3的集成性表明SD、MM和PP的应用能自动地交换实时的需求数据，需求将按单个的或汇总的需求被记录。物料管 理和生产计划功能将应用来自销售的需求信息，以确定是否需要立刻开始生产，或者是否要首先采购零部件。
　　如果因信贷限额超标而使发货的销售订单被冻结时，需求传送也可能被冻结。这种冻结将取决于商业事务的类型。一旦冻结被手工撤消后，需求信息就可以传送。如果后来你作了更改，该系统能自动更新需求的发送。
　　如果交货计划和可用性检查确定货物不能按要求的日期交货时，该系统将能根据客户接受部分交货的方案作出不同程度的反应：
　　*R/3系统确定货物的数量，如果有，将按客户要求的交货日期交货。
　　*系统确定整个交货的最早日期。
　　*系统确定什么货物可以按客户要求的交送日期进行交货和必要的部分交货，直到完成整个订单数量。
　 　由于缺乏货物可用性，订单项目按客户要求的交货日期不能得到确认时，订单项目可以应用延迟订单处理功能来加以更新。该系统可以重复检查可用性并显示目前 的状况。如果所有项目现在都能被交货，你就可以处理销售订单了。你还可以使用更新功能，通过手工调整重新分配短缺产品，以满足你的最紧急的客户订单。

How to create and process Rebate agreement?zz

http://www.saptechies.com/how-to-create-and-process-rebate-agreement/

Following explains how to crete a rebate agreement, test it using a sales order and billing it. Then settling it partially or fully using a rebate credit memo. Please use the basic procedure and tweak your IMG settings according to your unique requirements.

Rebate processing:
1. First requirement is that the rebate processing must be active for
a. the customer ( check in customer master) ,
b. for the billing type ( check in IMG > Billing > rebate processing > active rebate processing > select billing documents for rebate processing. )
c. For the sales organizatin:
( check in IMG > Billing> rebate processing > active rebate processing > Active rebate processing for sales org. )

2. Next create a rebate agreement For this ust T-code VB01. For the rebate agreement type you can choose either 0001
( group rebate ) or 0002 material rebate or 0003 ( customer rebate ) etc
b. Enter your rebate conditions. Dont forget to enter the accrual rate here.

3. Now test your rebate functionality : create a sales order for the particular customer, sales org ( ensure that the billing type used in your sales order is relevant for rebate) . Create outbound delivery, transfer order to do picking and post goods issue.

4. Now go to Tcode VB03 and check your rebate by choosing conditions , selecting the condition line and choosing payment data. You will see that the accruals and business volume are updated when accounting doc is created for billing.

5. Settling your rebates:
Once your rebates have been accrued you need to settle the rebate.
For this first release the rebate for settlement by using Tcode VB02. As a trial basis choose B ( you can choose other settings based on your requirement) and choose Create manual accrual. Now enter the amount to be paid and save the rebate agreement.

6. Next display your rebate agreement using Tcode VB03.
Enter your rebate agreement number . Next choose rebate payments > Rebate documents and select partial settlement. Click on the choose button to note down your credit request number.

7. Use Tcode VA02 and release the billing block for your credit request. ( use item overview tab)

8. Now use VF01 to create a rebate credit memo by entering the credit memo request number and save it

9. Now release the credit memo to accounting using vf02.

ATP zz

常说可用性检查或者ATP（Available-to-Promise），其实他们并不完全等同。可用性检查的方式有两种，

一是ATP Logic，

一是Against planned independent requirements。

前者会全盘考虑各种Issues和Receipts，如计划订单、生产订单、库存、销售订单等，可配置。后者只考虑计划独立需 求（PIR）与销售订单的供求关系，甚至不考虑库存。

ATP Quantity是Receipts减Issues的差值，该数量可供新的销售订单使用。

The quantity available to MRP for new sales orders.

The ATP (Available-to-promise) quantity is calculated according to the following formula: ATP quantity = warehouse stock + planned receipts - planned issues.

http://www.kanterwang.cn/post/47.html Kanter Wang

Availability Check，顾名思义，就是有效性检查，指的是要检查一下此物料是否能满足我的需求。

简单地举个例吧，你 接到一张销售订单（SALES ORDER），客户要求数量为100PC，并且客户要求的出货日期是2009-4-1，此时我们的销售人员肯定会想，在这个愚人节到底能否出货给客人呢？ 那怎么办呢？一个个电话去问生产计划人员，去问厂长，经理？废话，肯定不能这样，要不然花几百万，几千万上SAP做什么对吧，此时在系统中建立此单 时，SAP就会做一个所谓的检查，检查一下我们预先设定的考虑因素，能否满足客户的要求，什么时候可以满足，这就是有效性检查的功能。

但一般人看到此单词就会想到 ATP，实际上系统中并不只是包含这一层意思的，就听俺慢慢道来

有效性检查包含以下两个概念

1就是大名鼎鼎的ATP(全称：Available To Promise)

2.就是Check Against planned independent requirements (意指计划独立需求的相关检查)

ATP (Available To Promise)

有效性承诺，检查承诺物料的相关元素，看是否能满足需求，什么时候能满足。

先看标准解释图片

第一张图表示某物料在某个时间上有生产订单或计划订单，数量及时间如图

第二张图表示如果在某个时间上有销售订单

那我们的生产订单或计划订单能否满足客户的需求呢？就看图三了

当我们在建立S1此销售订单时，因为我们已经有了一张P2的生产订单，并且日期是小于S1的，因此S1是肯定可以满足的，并且是提供满足

S2同S1原理一样，完全就可以由P2去满足

S3可以被P3的一部分满足

S4可以被P3的剩余部分满足

S5被P4部分满足

而P4再剩下的部分数量，就是未来可提供的ATP QTY

当我们在使用ATP时，系统检查的LOGIC如下：

通过 checking group + checking rule 得到Scope of check

再在SCOPE OF CHECK中设定需要检查哪些元素，再把哪些元素加加减减得到剩余的ATP QTY，再用剩余的ATP QTY来与新的需求对比，从而决定是不是能满足到需求，看似简单，整起来还是有点事的，哈。有点说时迟，那时快的感觉。

Setting

Checking group 来自于物料主档，如下图

Checking Rule来自于应用程序，即不同的应用程序有不同的设定，如生产订单有生产订单的设定，销售订单有销售订单的设定等

SPRO->Production->Shop Floor Control->Operations->Availability Check->Define Checking Control

如上图，则是在PP模块中针对不同的PLANT + order type来定义不同的RULE，后面的BUSINESS 1 OR 2表示CREATE OR RELEASE.

看到吧，在这里就可以看到CHECKING RULE是多少

并且component check type是决定用ATP CHECK 还是用 AGAINST CHECK PLANNING INDEPENDENT REQUIREMENT

根据上两副图我们就会得到组合 Checking group + checking rule = 02 + PP

而02+PP又是控制什么呢，来看下面的路径

SPRO->Production->Shop Floor Control->Operations->Availability Check->Define Scope of Check

1 – 13 我想很明白可以看出来，是什么东西，这里我就不详细解释

14： 表示相关预留的选项，与10的区别在于，10是一般是表示我们用MB21建立的，而14是表示由于相关预留，即此预留是来自于其他物料，如生产订单所产生的预留

15：指STOCK TRANSFER ORDER

16：指计划订单

17：指生产订单

18要单独再演示

19 表示是否在库存地点的角度上去分析，如你在仓位：0001的需求是100PC,但是库存如下：0001仓 = 80PC ,0002仓=60PC，那对此物料去做ATP的时候，到底是应该显示缺料20（100-80）还是不缺料呢（80+60-100 > 0）？就是此栏位决定的

20：主要用于WORKFLOW，即在这个区间中，如果存在收货了，则会发邮件到MISSING CONTROLLER

21：用于控制确认的日期能否在过去或未来

演示

来个简单的演示吧。

今天心情不太好，没有用我的KT物料，因此用了标准的100-110此物料

此物料有库存72PC,0001仓22PC，0002仓50PC

但是在2008-12-30有一需求（OrdRes）即相关预留11PC，因此72PC中还有61PC可用，对吧。

如果此时建立一张新的PRODUCTION ORDER，如下图

可以看出第一次确认是为61PC，第二次为50PC（从中就可以看出是把2009-3-20的PchOrd给包含进去了）

在这里可能会有几个疑问：

1是61PC包含0001仓与0002仓

2是为什么61PC是2009-3-11

3是为什么PchOrd也参加了计算

先看看后台设定画面

看我上图中的红色标记可以1与3就可以解答了。

而2的答案是要看此物料的需求日期

如果你把No storage location inspection不选中的话，则ATP结果会如下：

2009-3-11变成了11PC，因为我们的0001仓只有22PC，但已经被第一张用了11PC，因此还剩下了11PC给新的生产订单使用。

如果不包含PURCHASE ORDER（不选中有数字标明图中的第7个及13）,则表现如下

只有11PC了，因为没有考虑PURCHASE ORDER。

好，现在来看看18的功能，之前的测试18项都是选中的

假设即不选中7 AND 13，也不选中18，如下图

注意，变了，大大的变了，多了一个2009-3-23 ，数量为剩余的109 = 120 -11 意思是为从现在去买的话，2009-3-23就会回来的，呵呵。

这个2009-3-23如何来的？就是靠18项控制的，18项的意思是说要不要考虑“补充交货周期”，那这个又是从哪来的呢？

看看这个

如果你是用SALES ORDER来演示的话，就要看看下面

OK? No Problem?

Check Against planned independent requirements

此方法即只是检查相关物料（或相关物料的计划物料）的计划独立需求能否满足需求，如果可以的话，就可以CONFIRM，如果不可以就不行，而不会去看相关物料的库存有没有，生产订单有没有。

在之前一画面我们曾经看过在生产订单中如何设定采用哪种方式，而是销售订单中，即是通过这个LOGIC来的。

1. 物料的STRATEGY GROUP

如果上图都不知道是那个画面的话，我想可能要麻烦你先学学以前的基础学科

2. 此STRATEGY 所对应的Requirement type of customer requirement

SPRO->Production->Production Planning->Demand Management->Planned Independent Requirements->Planning Strategy->Define Strategy Group

默认用第一个，但也可以选择其他几个策略的，这里可以参加PRODUCTION PLANNING COURSE

SPRO->Production->Production Planning->Demand Management->Planned Independent Requirements->Planning Strategy-> Define Strategy

就是上图中红色标记的 Availability check来决定的，如果选中，则在Sales order中是用ATP ，如果不选中，就是用 CHECK AGAINST PIR .

演示

此物料有库存100PC

没有任何的PIR (计划独立需求)

在建立Sales order的时候，不能CONFIRM到任何的数量，就算有库存也不行，并且你会发现这种与正常的ATP有点不同，在上面的工具栏中，并不会有什么SCOPE OF CHECK之类的字眼，可以去留意一下。

再来，如果我建立一个PIR

再建立SALES ORDER , CHECK 如下

看到吗？日期与数量都等于我们的PIR的数量。

注：此种方法跟：SPRO->Production->Shop Floor Control->Operations->Availability Check->Define Scope of Check 没有一点关系。

这个很简单吧。

下班了，要去吃饭了，写了我一上午，真是辛苦啊。

Credit Control

1. check setup for credit control area: 4 levels
OB38 CCA-companycode
OVFL CCA-sales area
XD02 CCA-payer
SE37 user exit

2. sales doc. type--credit limit check OVAK/OVAP
OR-D(automatic credit limit check) 01 (sales credit group)
LF-02-01

3. Define risk cat. for each CCA, will assigned to FD32
001 low risk
002 high risk
100 new customer

4. define credit check for Key fields: OVA8 CCA/risk cat./credit grp
eg: 1000 001 01 -> detail
1) if choose "status/block", the follow-up actions (like confirmation, avalibility check... will stopped)
if not choose, maybe impact, means even exceed credit, still can do ATPcheck...
2)statistic
Dynamic-impact follow acti vity

5. setup master data (credit limit) for payer FD32

6. item cat. level: active credit VOV7

7. pricing: "A" subtotal entered V/08

8. credit update for CCA OB45
000012-update group

9.define detail update for update group S066 OM01

思路：
credit control area setup: 4 ways
define credit group: 01 sales/02 delivery/03 goods issue
assign credit grop to sales doc. or delivery types
define credit limit relavance per item cat.
define scope of credit check (auto): CCA/risk cat./credit group

when credit hold, system can trigger output TRML to relative people

SD订单退货流程

步骤如下：
1）VA01，创建退货单据，单据类型RE。由于 们的产品采用batch管理，所以 们的人为规定 是：所有退货单据必须“参照billing单据创建”；
2）VL01，创建退货交货单，之后以VL02过账收货；
3）退回的货物将回到MRP的库存需求表中（MD04），处于退货库存状态（用MMBE可以看到），检 验批次用QE51可以看到。当然，如果根本就没有实施QM的话，QE51可以省略，但货物仍然处于退 货库存状态；
4）开具贷记备忘凭证（VF01），QM检测的结果记录以QE01完成；
5）退回货物若不需要QM处理，直接移到相应的库存（453移到非限制、459移到冻结），事务代码 MB1B。在QM介入的情况下， 们得用QA11做使用决策，合格品453、不合格品459，代码MB1B。殊 途同归。
6）退回货物的后续处理只有两种情况：要么买主要求 们换货（replace），要么买主要求 们 退款（refund）。前一种情况下，参照return单据创建新的标准订单然后备货发运开票即可；至 于后一种情况，如果提前收了买主的钱则经FI模块退回，要是没有提前收款也必须冲销销售收入 （即所谓的“红字发票”），这样第4）步的贷记备忘凭证就有存在的理由了。

Order-Billing-Delivery process

If want to invoice first, then goods issue.

1. Set up new item cat.: Billing relevance : B order-rel. billing type F1
2. Billing copy control: from order to billing, add this item cat.
3. When create billing document, billing type choose F1, not F2

testing order status change:
1. create order
2. create billing
3. create delivery
4. goods issue

Order			Open
Order			In process
..	Invoice		completed
	…	Accounting	Not cleared
Order			Completed
..	Invoice		completed
	…	Accounting	Not cleared
..	Delivery		In process
Order			Completed
..	Invoice		completed
	…	Accounting	Not cleared
..	Delivery		Completed
	…	GI document	Completed

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

Steps for Variant Configuration and Pricing zz

http://www.sap-basis-abap.com/sd/steps-for-variant-configuration-and-pricing.htm

I want to configer motercycle having differnt types of colour, each colour have varity of standered feature as wall as differnt CC. while want to create slaes order I want motercyle with speciefic colour, Cc feature. which is not possible while creating BOM it will only be configer by materiel Varient Configration.

-------------------------------------
Here are the Steps for Variant Configuration

1.Create a Material of your Motor Cycle using Material type KMAT(MM01).

2.Then create a characteristic called ZColour(SAP has a standard Characteristic for this but it has multiple values-i.e you can select more than one colour for your Bike.If you do not want that create your own)with character format and assign single value radio button on the initial screen.Go to values Tab and give the colours you need.save the characteristic.Similarly repeat for CC(I figure this CC as 100cc & 200cc kind of thing.If you want these as materials then it is a different story-I am taking this as feature as well)

3.Create a class called Zbike with the above 2 characteristics.save the class

4.Create a configuration profile Zbikeprof using Cu41 and assign the Kmat material to Class Zbike,

5.Then create the order and Enter the Kmat material you want in the Order.

John Devraj.

-------------------------------------
In variant configuration I have configured my material properly during sales order creation it is selecting proper characterstics. but my question is pricing should calculate at characterstics level not at header level.

Ugamesh.

-------------------------------------
Pricing in variant Configuration is done at the Header level only.The logic is that you create pricing variant keys for each characteristic Value.This will be done at the Header level using cond type VA00.based on the characteristic chosen the appropriate price according to the pricing variant key will be picked up.

John Devraj.

-------------------------------------
Here my question is with out creating the materials is it possible to get price based on the characterstics.

I am working on variant configuration here my product is 9-100. i have created characterstics for describing colours. this characterstics assigned to class, this class is assigned to 9-100(KMAT type). here i have not created amterial to describe each colour.

Now how I need to setup my system to calculate the price based on colour.

Ugamesh.

-------------------------------------
A cool Question. It will really get us into the thick of things in Variant Configuration.

Here are the steps.

1.Create a Characteristic called ZColour(Standard SAP has a characteristic called colour.I did not use it.)
Give your values.
Say, Red & Blue

2.Now create another characteristic called ZCol_surcharge
Give the description and go directly to Addnl Data Tab.Here in the table name Enter "SDCOM" and in the Field Name Enter "VKOND".The system will pick up the format from the Dictionary.

3.Now go to CT04 and change the Characteristic Zcolour.
Go to values tab and select RED.Goto Extras-> Object Dependencies->Editor and then select Procedure.

In front of 000010 Enter $self.ZCol_surcharge='RED'.
Similarly Select Blue and enter $self.ZCol_surcharge='BLUE'

3.Link both these characteristics to the Class(The class which you have attached the KMAT Material).

4.Go to VK11 and the Enter VA00.Then give the values RED and BLUE and enter the values.

5.Go to your order and Enter your material.

John Devraj.

-------------------------------------
Here are some clarifications required from you.

what is the significance of item category group 0002 and 0004. Apart from these are they any other item category groups are available for configurable materials ?
In BOM header material having components. is it possible to make the component as configurable material.

Ugamesh.

-------------------------------------
The difference b/w 0002 and 0004 is basically that of LUMF & ERLA.
In 0002 the pricing happens at the Header Item Level.
In 0004 the pricing happens at the Sub Item Level.
Check out the Item category Assignments and things will be Clear.

I think these two are the only ones used for Configuration.

Please let me know in which Scenario you would like to have the configurable material Inside a BOM(as it would help me in visualising thh Item Category Assignment).

John Devraj.

-------------------------------------
As you said I setup my system to calculate price based on colour.
ZCOLOUR contains all colours in values tab page.
ZPRICE contains table name and filed name in additional data tab page.

I went to ZCOLOUR characterstics I maintained (extras-object dependicies-editor-action) there I have given $self.ZPRICE = 'RED' for all the values.

when am creating the sales order price is coming only for RED colour not other colours. even price is maintained for all the colours.

Ugamesh.

-------------------------------------
Seems like there is a mistake in the line $self.ZPRICE = 'RED' (You have said you have given this for all the values- If I have not mistaken). This refers only to red colour.

In front of 000010 Enter $self.ZCol_surcharge='RED'.
Similarly Select Blue in the Values Tab and enter $self.ZCol_surcharge='BLUE'

All this is Case Sensitive. So please be careful.

John Devraj.

-------------------------------------
Now its coming any way thank you very much.

Ugamesh.

-------------------------------------
I have been reading your's and ugamesh's mails regarding the same but no where the sales doucments have been discussed as well as material master record and configuration in SPRO.

If you can kindly explain me the same as I was trying to do the same.

Reena

-------------------------------------
There is no need SPRO involvement in Variant Configuration.Everything happens in Easy Access.
As far as Material Master record is concerned you only need to use a KMAT Material type.

There is no need to assign any sales document to this material.

Follow the steps and you will get the result.

John Devraj.

-------------------------------------
I have gone thru the steps and created a sales order, but the pricing procedure is not coming proper. Also do we have to maintain the values for the ZCol_surcharge.
As I have already maintain the rates of the color in VK11 - VA00.

Reena

-------------------------------------
Have you maintained the Object Dependencies for the values in the characteristics class.

John Devraj.

-------------------------------------
Yes !

What I have done is created a customer with KMAT ( Car), without characteristics tab pg. After this I created 3 charateristics viz., zcolor, zengine & zcol_surcharge and assigned them to Class 300 ( Variant).
But I have maintained the dependencies only for Zcol_surcharge : $self.Zcol.surcharge='RED'
Then I assigned all these to a config profile and aslo added the condition VA00 in the pricing procedure, then maintained the same in VK11.
Now my problem is it is not coming in the SO

Reena

-------------------------------------
I think the problem is with the characteristics.
For the characteristics Zcolor and Zengine you must maintain some values in the Values Tab.
Ex:
Zcolor- Red
Blue
Zengine- V6(Right now you can use only one Characteristic for learning)
V8

The characteristic Zcol_surcharge(By name this suggests that it is applicable only to colour-Whereas you can use it for other characteristics as well) does not have any values.

For the values maintained in the Characteristics Zcolor and Zengine you have to go to each value(Go to values tab and select Red) and maintain the object dependency "Action" $self.Zcol_surcharge='RED'. Similarly maintain for Blue,V6,V8 for Example.

Then maintain the condition records for Va00(without any Case mismatch).

Use standard pricing procedure RVAA01.(or a copy- as it has provision for VA00).

This should solve your problem.

John Devraj.

open order & back order

back order process in IDES:
Sales Processing according to ATP logic and Backorders
http://help.sap.com/saphelp_46c/helpdata/en/e6/4a86da9e0311d189b70000e829fbbd/frameset.htm

'open order' is all orders that have not been deliveried or partially deliveried.
if order have not been confirmed or partially confirmed, or have been confirmed, but
up to customer's request delivery date, it have not been deliveried, system also
recognize it as 'back order'.
In a word, 'back order' must be 'open order'.

"Backorder list will include :

1. Sales Order Item which is not fully confirmed
2. Sales Order Item with requested delivery date which can not be kept

This backorder only valid with material which has an individual requirement which is
defined in availability check field (checking group) in material master MRP 3 view.

TCODE V_RA is a manual backorder processing means that all list of incomplete sales
order will be presented for the selected material and plant.

TCODE V.15 is a backorder list which include all sales order which is not fully
confirmed and which is late for delivery. "

SD认证考题分布和复习要点 zz

http://www.cnblogs.com/omygod/archive/2008/01/27/1055228.html

提问领域

l Sales 15题

l Pricing 10题

l Billing 8题

l Shipping 8题

l Master Data 5题

l Special Business Transactions 5题

l Credit Management 4题

l Integration 4题

l Logistic Information System 4题

l SAP Fundamentals 4题

l Company Structure 3题

l mySAP.com 3题

l Transportation 3题

l Business Information Warehouse 2题

l Cross-Functional Customizing 1题

l Implementation Guide 1题

总共80道题

. 销售 (15题)

1. Study how the proposal for the sales documents are determined

2. Where are the possible output types stored ?

3. Study how documents are linked to each other (document flow) and how they are updated.

4. Study the functions you can perform during order entry.

5. What does the document type control?

6. Study the functions of the partner function.

7. Study the output determination in sales.

8. Study the relationship between sales order and quotation.

9. Study the output transmission (output of sales documents).

10. Study the sales document types (functionality) in more details.

11. Study the functionality of contracts in more details (time span, pricing, maintenance of header and item data).

12. Study to which other preceding business transaction a sales document can be linked to.

13. How is the schedule line determined?

II. 定价 (10题)

1. Study the elements which determine the pricing procedure.

2. Study the rebate processing in more details.

3. What do you have to do if would like to create a customer specific discount using a condition supplement.

4. Study the primary functions of the rebate processing.

5. Study the condition table in more details.

6. What are the aims of pricing?

7. Study the fields you can maintain in a condition record.

8. Study the special functions available in pricing (special condition types, cumulative conditions, condition exclusion).

III. 开票 (8题) 1. Study the copy control functions.

2. What is a billing due list? What can you create with a billing due list?

3. Study the functions of the credit/debit memos.

4. Study the link to financial accounting (what can you change if data is transferred from billing to FinAcc. ?)

5. What are the options you have during the process of billing due list?

6. Which accounts are normally involved if you post a billing document?

7. Study the organizational level for processing the billing due list.

IV. 装运 (8题)

1. Study the functions of the delivery item category.

2. Study the creation of delivering documents in relation to mandatory reference requirements.

3. Study the functions of the shipping point (relationship to plants, processing and monitoring).

4. Study the goods issues in relation to quality inspection.

5. Study the functions of goods issues concerning date and whole/partial deliveries in more details.

6. Study the linking of partner systems in shipping.

7. Study the determination of the correct shipping point.

8. Study the function of the partial deliveries in more details.

9. Study the condition records in more details.

10. Study the procedure to create a new condition type.

V. 主数据 (5题)

1. Study the field selection, number assignment, account group functionality in more details.

2. Study the customer master and relevant organizational elements and default values.

3. Study the fields of the customer master for determining the pricing procedure.

4. Study the field selection if you define a specific industry sector.

5. Study the functionality of the material type.

VI. 特殊业务事务 (5题)

1. Which elements are taken into account for the availability check?

2. Which scope (organizational elements) of the availability check is possible?

3. Study the requirements to invoice a sales order on cross company basis?

4. Study the functions of consignment fill up.

VII. 集成 (4题)

1. On which organizational level can you maintain the customer master?

2. Study the possible functionality within the customer order management process.

3. Which processes are standard in SAP?

4. What does the material type specifies?

5. What are the key information flows in an integrated enterprise?

VIII. 后勤信息系统 (4题)

1. How is the statistical data updated? (synchron / asynchron)

2. Study the functionality of the standard analyses.

3. Study the type of information contained in an information structure.

4. Study the relation between document types and update analyses.

IX. 公司结构 (3题)

1. Study the transportation planning point in more details.

2. Study the functions of the sales organization.

3. Study the assignment of shipping point and plants, sales organization, distribution channel, …

X. SAP 基础 (4题)

1. What is a client dependent/independent?

2. What is a purchase requisition?

3. What is a goods receipt?

4. What does the payment processing do in concern to liability?

5. Where can you define the date format?

XI. 运输 (3题)

1. Why is Transport a part of Logistic Execution?

2. When you create delivery document in SD you need to enter a selection date. Can this date be later or equal to the material availability date?

3. A schedule line in the order is always due on material availability date?

4. All items must be picked before goods issue in an outbound delivery can take place.

5. What can you change in the outbound delivery in an order due to delivery?

6. Can you change deadlines in an order due for delivery?

XII. 信用/风险管理 (4题)

Topic credit limits

1. Can credit limits be stored at customer level?

2. Can credit limits be managed for all credit control areas?

3. Can credit limits be managed at client level?

4. Can credit limits be controlled at a particular credit control area which must not exceed the specific limit?

5. Does a credit management master record manage open sales order values and receivables for participating customer in a group of affiliated companies?

6. A credit management master record is a customer account in a credit control area?

7. A credit management master record manages open sales order values and receivables for a customer.

Which of the following statements of Risk category management is correct:

1. Is a risk categ. stored in the credit master of the customer and does it control the scope of the credit limit check?

2. The risk categ is copied from the credit master record as a proposal in the sales order and can not be overwritten.

3. This risk categ is determined in the sales order from the combination of customer credit master, customer material master and document amount.

4. At which stages of the sales order processing can you perform credit limit checks?

XIII. MySAP.COM (3题)

Which benefits with Market place / Work place ?

XIV. IMPLEMENTATION GUIDE (1)

Identify the only one correct statement related to the implementation guide.

XV. 业务信息仓库 (2题)

Tips

What are the components of BW ?

Which of the following XXXX does BW provide ?

XVI. 跨功能定制 (1题)

并不完全