http://sap.ittoolbox.com/groups/technical-functional/sap-log-sd/printing-delivery-note-automatically-after-goods-issue-351055
1.
V/34 - I'm assuming you already have the output type set up ?
Ensure that the 'send time' on the output type is '4 - immediately
with update'
Include an access in the output type of appropriate data . If a
suitable one doesn't already exist create it in V/50.
Check the output type is fully configured in V/36, V/49, V/G9
就是設定message的呼叫PROGRAM and routine
V/50 - Whatever access sequence you chose, set a requirement '1 - Delivery
GI posted' to make the output automatic when and only when the GI is
posted. Good idea to make it exclusive as well.
VV22 - Create condition records for the access
VP01SHP - Assign the printers and ensure that the 'Print Immediately'
checkbox is set here.
This man is too old to remember everything in his brain. Right now, he needs a place to write down what he has studied.
標籤
4GL
(1)
人才發展
(10)
人物
(3)
太陽能
(4)
心理
(3)
心靈
(10)
文學
(31)
生活常識
(14)
光學
(1)
名句
(10)
即時通訊軟體
(2)
奇狐
(2)
爬蟲
(1)
音樂
(2)
產業
(5)
郭語錄
(3)
無聊
(3)
統計
(4)
新聞
(1)
經濟學
(1)
經營管理
(42)
解析度
(1)
遊戲
(5)
電學
(1)
網管
(10)
廣告
(1)
數學
(1)
機率
(1)
雜趣
(1)
證券
(4)
證券期貨
(1)
ABAP
(15)
AD
(1)
agentflow
(4)
AJAX
(1)
Android
(1)
AnyChart
(1)
Apache
(14)
BASIS
(4)
BDL
(1)
C#
(1)
Church
(1)
CIE
(1)
CO
(38)
Converter
(1)
cron
(1)
CSS
(23)
DMS
(1)
DVD
(1)
Eclipse
(1)
English
(1)
excel
(5)
Exchange
(4)
Failover
(1)
Fedora
(1)
FI
(57)
File Transfer
(1)
Firefox
(3)
FM
(2)
fourjs
(1)
Genero
(1)
gladiatus
(1)
google
(1)
Google Maps API
(2)
grep
(1)
Grub
(1)
HR
(2)
html
(23)
HTS
(8)
IE
(1)
IE 8
(1)
IIS
(1)
IMAP
(3)
Internet Explorer
(1)
java
(4)
JavaScript
(22)
jQuery
(6)
JSON
(1)
K3b
(1)
ldd
(1)
LED
(3)
Linux
(120)
Linux Mint
(4)
Load Balance
(1)
Microsoft
(2)
MIS
(2)
MM
(51)
MSSQL
(1)
MySQL
(27)
Network
(1)
NFS
(1)
Office
(1)
OpenSSL
(1)
Oracle
(131)
Outlook
(3)
PDF
(6)
Perl
(60)
PHP
(33)
PL/SQL
(1)
PL/SQL Developer
(1)
PM
(3)
Postfix
(2)
postfwd
(1)
PostgreSQL
(1)
PP
(50)
python
(5)
QM
(1)
Red Hat
(4)
Reporting Service
(28)
ruby
(11)
SAP
(234)
scp
(1)
SD
(16)
sed
(1)
Selenium
(3)
Selenium-WebDriver
(5)
shell
(5)
SQL
(4)
SQL server
(8)
sqlplus
(1)
SQuirreL SQL Client
(1)
SSH
(3)
SWOT
(3)
Symantec
(2)
T-SQL
(7)
Tera Term
(2)
tip
(1)
tiptop
(24)
Tomcat
(6)
Trouble Shooting
(1)
Tuning
(5)
Ubuntu
(37)
ufw
(1)
utf-8
(1)
VIM
(11)
Virtual Machine
(2)
VirtualBox
(1)
vnc
(3)
Web Service
(2)
wget
(1)
Windows
(19)
Windows
(1)
WM
(6)
Xvfb
(2)
youtube
(1)
yum
(2)
2014年3月26日 星期三
2013年5月21日 星期二
Maintain Terms of Payment
http://www.cnblogs.com/etat/archive/2012/12/10/2810970.html
Maintain Terms of Payment
In this step, we will define rules with which the system can determine the required terms of payment automatically. The rules are stored under a four-character key. Assign the terms of payment specified to the customers in the master record via the key. The key and the terms determined with it are proposed when entering a document to the customer account.In this article , We will study the standard course and how to calculation the baseline date & net due date .
1、Standard Course Study
一般情况下只要有与SAP的财务相关的都会用到这一部份 – 收付款条件,
包括供应商的,客户的以及其它发票类的都会用到,这些收付款条件决定着收付款的日期。
在阐述收付款条件之前先来了解几个名词:
- Baseline date – 基准日,基本可以理解成结算日,即每个公司每个月都有自己的结算的那天,叫Baseline date ;
- Net due date – 到期日;
- Document date - 发票输入日期;
- Posting date – 过账日期,即过账到FI的日期;
- Entry date – 输入日期,这个可能大家会和Document date理解成一样,其实不然,Document date ,这个是发票日期,可以是前一天,也可以是后一天或者当前日期,但Entry date 是当前日期,所以这两个还是有点区别的;
Payment terms 会用在FI/SD/MM中,SD/MM最后汇总到FI都将直接影响到他的payment date。
SD 定义路径:
SAP -> Logistics -> Sales and Distribution -> Master Data -> Others -> OBB8 – Terms of Payment .
SAP -> IMG -> Sales and Distribution -> Master Data -> Business Partners -> Customer -> Billing Document -> Define Terms of Payment – OVSE.
FI 定义路径:
SAP -> IMG -> Financial Accounting -> Accounts Receivable and Accounts Payable -> Business Transactions -> Incoming Invoices/Credit Memos -> Maintain Terms of Payment – OBB8.
SAP -> IMG -> Financial Accounting -> Accounts Receivable and Accounts Payable -> Business Transactions -> Outgoing Invoices/Credit Memos -> Maintain Terms of Payment – OBB8.
MM定义路径:
SAP -> IMG -> Materials Management -> Purchasing -> Vendor Master -> Define Terms of Payment – OME2.
总之,这些定义的都是直接或者间接的调用OBB8去维护收付款条件。
- 去参考一些Invoice的payment terms 来确定新Invoice 的payment terms .
- 到期的payment terms结算日失效 ,到变成有效的payment terms .
一个新的payment terms 包含的基本数据:
- Day Limit – SAP标准的解释是: Day of the month up until which the corresponding terms are valid.其实就是当前日期的是否附件该会议条件的使用,如果是就会自动计算Baseline date ,否则需要手动去输入。
- Description – 每一个payment terms的描述。
- Account type - Account type 是指这个Payment terms 将适用于供应商还是客户。
- Block key - Default value for the payment blocking key.这个就是说明如果是这个值将会默认为这些payment 将要block,也就是锁住这些Doc.。
- Payment method - The payment method determines how payments are to be made,e.g. by check, bank transfer or bill of exchange.也就是说,这个Payment 同时确定收付款方式。
Payment terms 每一个是都可以去默认一个Baseline date 或者通过计算得到一个baseline date;
Baseline date 可以是:
- No default
- Document date
- Posting date
- Entry date
- 默认日期的 01 号,也叫第一天;
- 默认日期的月份 + 1的日期;
如果在Fixed day = 28,那基准日期就是当月的28日,eg. 你的开始基准日期是2010.01.12.则此时的Baselie date 是 2010.01.28;如果你设置的Fixed day 为31时,则到二月份的时候,系统会自动的计算2月份的月底是几号,比如你的开始Baseline date 为2010.02.01,Fixed day = 31时,系统自动自动算成2010.02.28为最终Baseline date;因为28日是2月份的月底,所以希望大家对这一点能够很好的分辩和区别出来。
折让有两种,如下图:
- 在期间内的折让;其Days是升序的,也就是说天数只能是下面的数字大于上面的数字;
- 在某个特定日期的折让;Fixed date + Additional months 连用,也是升序;
Payment terms 里面有个Day Limits 的用法:很多时间我们并不会在意这些,都不会去区别这部份的值的日期;其实在SAP的标准功能中是有作区分的;
Payment terms 的主键是 payment terms + day limits 也就是说只有这两个才可以确定最终的Baseline date,也是两个不同的payment terms,如何区别,这就用到了Day Limits。
举个例子说明一下吧:
e.g. 有一个payment terms – 0001, 设置了两个不同的Day Limits 一个是Day Limits = 15;另外一个 Day Limits = 21;Baseline date = Posting date 的时候;这个时候就产生了两个payment terms : 0001 + 15 和 0001 + 21 两个;如果Posting date = 0 ~ 15,则会使用 0001 + 15 的 payment terms;如果posting date = 16 ~ 21 ,则会使用 0001 + 21 的payment terms ,来进行计算出最终的Baseline date;如果超出21;系统会提示Specify payment period baseline date,则这个时候则需要手动去输入Baseline date;
分期付款的部份,需要体符合两个条件:
- Day Limits = 0;
- 勾选 R Installment payment ;
OBB9 PATH:SAP -> IMG -> Financial Accounting -> Accounts Receivable and Accounts Payable -> Business Transactions -> Define Terms of Payment for Installment Payments – OBB9.
Samples for terms of payment
如何建立一个payment terms。
建立路径在上面的文章中已经说明,就不再重复,只要记住一个TX:OBB8.
单击New Entries 去建立一个新的Payment terms。
一个Payment terms 主要是分几个部份:
第一部份是Payment terms + Day Limit,前面讲述过,这里就不再重复;
第二部份是Account Type 这个说明,这个Payment terms 将会应用到供应商还是客户那里,还是两个都可以;
第三部份就是Baseline date 的计算;Fixed day 理解成结算日(已经在前面的几个名词中解释过);Additional months 这个是指结算日是否需要增加月份;
第四部份就是一个Default值,前面已经说到就不再重复;
第五部份是Default Baseline date;其实我们最后看到的都是经过计算的Baseline date;一般情况下会将默认的Baseline date 定义为Posting date,但也有可能定义在Document date上,就业务逻辑而言,两者都有各自的理论依据;根据各公司的要求不同,各默认的Baseline date 也不尽不同;
第六部份是Percentage 通过单词也能理解,这个就是折让的百分比;
第七部份就 No.of days或者Fixed date + Additional Months,两者不能同时使用,只能二选一;
同样方法我定义了三个Payment terms如下所示:
- Z00 + 0 ,Default Baseline date = Posting date;
- Z00 + 18,Default Baseline date = Posting date;
- Z00 + 30,Default Baseline date = Posting date;
将这个Payment terms 来分配给Customer C9999;
测试一下系统会不会自动去检测用那一个Payment terms ;
为什么会这样?不是说根据日期时间来自动选择Payment 的吗?Posting date = 2010-01-20,就应该选择Z00 + 30 的payment terms,其实不然,由于Z00+0 是在到期时立即收付款,所以不管你怎么去改,SAP始终拿的是 Z00 + 0 的收款方式。所以现在把Z00 + 0 的payment terms 删除掉来看看Z00会选择那个Day Limits。
由于Posting date = 2010.01.23所以,系统会自动选取 Z00 + 30的payment terms,而Z00 + 30 的payment terms的Calculation baseline date = Fixed day + additional months,也就是说是下一个月的1号,当前Posting date = 2010.01.23所以下一个月的一号应该是2010.02.01,来看一下Z00 + 30 的设置。
再来做一张Posting date 在18号的看看。
系统就自动选取了 Z00 + 18的payment terms,
看看Z00 + 18的payment terms。
等等,其实像Installment payment,No. of days ,Fixed date + Additional months 的分期收付款以及折让的就不再一一详述,大家可以自己去测试,去作一些相关的Demo,相信可以找到你想要的;在前面也有提到其实最终的Baseline date = Default baseline date + Calculation baseline date 。Default baseline date 又可以在 No default,Posting date,Document date,Entry date 中任一选择。
Net due date 又是如何计算的呢,给大家一个例子一看就明白了。
就看刚才的这张Document ,我们就FBL5N去看一下。
大家可能会发现,为什么1800001450~1800001452的Baseline date = Net due date,而只有1800001453的Net due date = 2010.03.06,为什么,且听我慢慢道来;
由于 1800001450~1800001452 这几个用的payment terms都用的是Z00 + 30,而Z00 + 30 是没有设置Net duedate的,也就是多少天之内或者期间内付款会到期,过了这个日期,就只能叫Overdue。
而1800001453 用到的Payment terms 是 Z00 + 18,这个有折让的部份,且是45天净到期,它的Baseline date = 2010.01.20 + 45 天 = 2010.03.06,所以如果这样的话,就不难解答这个问题;
分两种情况:
- 如果有Net due date的部份,则其折让的最后的Net due date = Baseline date + No. of days(最大的值)或者 Net due date = Baseline date + Fixed date + Additional months.
- 如果没有Net due date的部份,直接是Net due date = Baseline date .
SAP -> SE37 -> Function : NET_DUE_DATE_GET.
2013年4月26日 星期五
Configuration of configurable material
http://arthur_ong.tripod.com/xpp006.htm
Configuration of configurable material
In a Window manufacturing: It is totally a customer specific(configurable) item and each customer will have its own requirement of different sizes of windows and doors for buildings.
For example, customer wants following :-
As soon as sales order created for configurable material he should be able to know the planned cost,availability of BOM items, resources etc.
In configurable products you need:
1.- Define as KMAT material.(嗯,一定要用KMAT的material type嗎?)
2.- Define classes and characteristics.
3.- Create a configurable profile and asign it to Kmat.
4.- You need a SuperBom and Super routing for this material.
5.- Define global and local dependencies to control this materials and operations.
When you enter to VA01 for a Sales requirement the characteristics will be displyed and you'll be able to configure the product.
If you have created KMAT, class, characteristics, dependency but is still not able to see the characteristics values for configuration in transacton VA01.
You are not getting any error message in sale order creation. Even configurable tab is not appearing in the screen of sale order. Make sure you have made a configurable profile (CU41) and assigned to KMAT? In this you link the classes and the characteristics with Kmat material. You have to check the class category is 300.
Which item category group did You put on the sales view on the material master and did that lead to an item cat. in the sales order which initiates the configuration ?
Is the "Configurable material" box checked on the material master?
Please check wheather you have assigned variant class 300 to the kmat (Configurable material) in the material master. I presume that you have selected classification view while creating material master for this KMAT.
Ensure that you have done the following for configurable material :-
Material master:
You have created material of material type "configurable material"(KMAT).
In basic data 2 check box for configurable material is selected.
Material is assigned to class type "300" in the classification view.
In sales org 2 view General item category group is "0002"(Configurable).
In MRP3 view strategy group "25" (Make to order for configurable material) is given in the field.
Classification:
You have created a class of class type 300.
Characteristics and its values are created and assigned to above class.
Configuration Profile:
Configuration profile for object type "material" is created for the material KMAT.
This profile is assigned to class type 300 and released.
Profile is assigned to class.
Please, check the requirement type on your sales order. It should be related to Configurable material as KEK (make-to-order configurable material), KEKT (order + comsumption of variant) or KEKS (order + consumption of charracteristics planning).
If you don´t use any or this, the system doesn´t display configuration table and the sales order seems normal.
You now be able to configure material in sale order on the basis of characteristic and values.
Now, how can you trigger BOM items and quantities in PP order from configured sale order.
After you save the sales order you can create a production order to a sales order in transaction CO08. Or, if you have several levels on your product you can run an MRP (if your material is planned using MRP type "PD" or other previsional MRP type) and convert the planned order. The system create an specific BOM and Routing for this sales order configuration. You can check this specific configuration in production order header -> configuration.
Configuration of configurable material
In a Window manufacturing: It is totally a customer specific(configurable) item and each customer will have its own requirement of different sizes of windows and doors for buildings.
For example, customer wants following :-
As soon as sales order created for configurable material he should be able to know the planned cost,availability of BOM items, resources etc.
In configurable products you need:
1.- Define as KMAT material.(嗯,一定要用KMAT的material type嗎?)
2.- Define classes and characteristics.
3.- Create a configurable profile and asign it to Kmat.
4.- You need a SuperBom and Super routing for this material.
5.- Define global and local dependencies to control this materials and operations.
When you enter to VA01 for a Sales requirement the characteristics will be displyed and you'll be able to configure the product.
If you have created KMAT, class, characteristics, dependency but is still not able to see the characteristics values for configuration in transacton VA01.
You are not getting any error message in sale order creation. Even configurable tab is not appearing in the screen of sale order. Make sure you have made a configurable profile (CU41) and assigned to KMAT? In this you link the classes and the characteristics with Kmat material. You have to check the class category is 300.
Which item category group did You put on the sales view on the material master and did that lead to an item cat. in the sales order which initiates the configuration ?
Is the "Configurable material" box checked on the material master?
Please check wheather you have assigned variant class 300 to the kmat (Configurable material) in the material master. I presume that you have selected classification view while creating material master for this KMAT.
Ensure that you have done the following for configurable material :-
Material master:
You have created material of material type "configurable material"(KMAT).
In basic data 2 check box for configurable material is selected.
Material is assigned to class type "300" in the classification view.
In sales org 2 view General item category group is "0002"(Configurable).
In MRP3 view strategy group "25" (Make to order for configurable material) is given in the field.
Classification:
You have created a class of class type 300.
Characteristics and its values are created and assigned to above class.
Configuration Profile:
Configuration profile for object type "material" is created for the material KMAT.
This profile is assigned to class type 300 and released.
Profile is assigned to class.
Please, check the requirement type on your sales order. It should be related to Configurable material as KEK (make-to-order configurable material), KEKT (order + comsumption of variant) or KEKS (order + consumption of charracteristics planning).
If you don´t use any or this, the system doesn´t display configuration table and the sales order seems normal.
You now be able to configure material in sale order on the basis of characteristic and values.
Now, how can you trigger BOM items and quantities in PP order from configured sale order.
After you save the sales order you can create a production order to a sales order in transaction CO08. Or, if you have several levels on your product you can run an MRP (if your material is planned using MRP type "PD" or other previsional MRP type) and convert the planned order. The system create an specific BOM and Routing for this sales order configuration. You can check this specific configuration in production order header -> configuration.
2013年4月23日 星期二
Cost Estimation of Configurable material
http://scn.sap.com/thread/1895312
其實,我用Material Variant去生產就好,不要用Configurable Material生產,對生產單位而言比較簡單。而且成本也可以使用標準成本。
Cost Estimation of Configurable material
-------------------------------------------------------------------------------------------------------------------------
其實,我用Material Variant去生產就好,不要用Configurable Material生產,對生產單位而言比較簡單。而且成本也可以使用標準成本。
Cost Estimation of Configurable material
-------------------------------------------------------------------------------------------------------------------------
Dear All,
Its
implied that configurable material will not have its BOM and Routing
howeve it will select the material as per requirment. Can any help me
out how to do take cost estimation of confugurable material?
Thanks,
sneha
-------------------------------------------------------------------------------------------------------------------------
sneha
-------------------------------------------------------------------------------------------------------------------------
Hi
Based on the Chars you select while creating a sales order, the Sales Order BOM is selected..
With this BOM, the sales order cost estimate is created...
The
settings to create a sales order cost estimate upon saving of sales
order are to be done in Requirement class (IMG>CO>Prod Costing
> Cost Obj Contr > Product Cost By Sales Order > Control of
....)
Br, Ajay M
-------------------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------------------------
Dear Ajay,
Thanks
for your inputs!!! However, we are doing not Sales order cost
estimation but taking the cost rollup at Material. Please suggest how
to perform cost estimation at material level for configurable material.
thanks,
Sneha
-------------------------------------------------------------------------------------------------------------------------Sneha
Hi
Cost
estimate from CK11N for config material does not make sense... and
neither it is possible for BOM does not exist for the same in CS01...
You need to have Sales order cost estimate...
If you do from Ck11N, it will include components for all the chars and your cost estimate value would touch the sky
Imagine
a Car - It has components for red paint, black paint, blue paint etc...
If you do from Ck11N, it will include all the paints in the cost, which
is wrong..
Sales order cost estimate will include only the color desired by customer
Br, Ajay M
-------------------------------------------------------------------------------------------------------------------------
hi sneha..
I think you may follow the steps :
1. Creat SO in ref. of Customer PO VA01
2. Through MRP run Plan order will be created with ref. to SO MD50/MD04
3. Convert Plan Order to Prod. Order MD04
4. Goods issue to Prod Ord. MB1A/MIGO
5. Confirmation of Prod Ord. CO15
6. GR against Prod. Ord. MB31/MIGO
7. Order Settlement for Prod. Ord. KO88
8. Delivery to finished goods VA01N
kkumar
-------------------------------------------------------------------------------------------------------------------------
Hi Sneha,
a configurable material always needs a configuration - otherwise it cannot be costed.
This configuration can be provided
- in a sales document or
- in a configured material or
- in the simulation environment of t-code CU50
Configured materials can be costed by t-code CK11N.
In CU50 you can create and display cost estimates, but you cannot save them.
Best regards,
Johannes
-------------------------------------------------------------------------------------------------------------------------This configuration can be provided
- in a sales document or
- in a configured material or
- in the simulation environment of t-code CU50
In CU50 you can create and display cost estimates, but you cannot save them.
Johannes
2013年4月22日 星期一
Super BOM(Configurable material BOM)的应用-SAP屠夫
Super BOM(Configurable material BOM)的应用-SAP屠夫
熟悉make-to order之前,先说一下什么是Super BOM,因为一般make-to order和这该死的Super BOM,变式(配置)BOM通常总鬼混在一起.
降低材料成本(11%-40%)、提高生产率(6%-45%)、加快资金周转(8%-3
5%)、提高用户服务水平(10%-27%)?要是让我吹,干脆就一口咬定俺家SAP不但能滋阴壮阳关还能延年益寿得啦.
一 Classification System(分类系统)简介

[1]Define Default Settings
状态 1 (released)被预定义给所有的特征(characteristics),除非你有特殊需求,SAP推荐不做任何更改
[2]Define特征组
[3]Define特征状态

二 Super BOM和配置BOM应用举例
1.建立特征(Tcode:CT04)
如图1.

Restrictions是做限制的,比如选择了ZST_ZJ特征不能用于某Class type,这很好理解.

上面建立了特征ZST_ZJ(主机)包含3个特征值ZZJ1-ZZJ3同样地,建立特征ZST_BOX包含特征值ZBOX1-ZBOX3,特征ZST_PAK包含特征值ZPAK1-ZPAK3.
建立类(CL01/CL02/CL03)

现在的问题是如何将Characteristic/Class和material master data/BOM master data 挂沟.
为了不混淆视听,通常的做法是各层物料尽量采用class名称,特征值(特征这层似乎不要建立物料)的名称,为了方便理解,假设配置BOM下面再没有可配 置子BOM,于是,本例你需要建立的material No是ZST_MODEL(Super BOM top-level material),ZZJ1-ZZJ3,ZBOX1-ZBOX3,
ZPAK1-ZPAK3 .
为了方便理解,再假设每个主机,机箱和包装材料都由3个material component,比如ZZJ1由970000-970002组成,ZZJ2由970003-970005组成,ZZJ3由970005-970008 组成. 依此类推,机箱ZBOX1-ZBOX3和包装材料ZPAK1-ZPAK3的material component从970009-970026(假设每组件有3component组成).
建立物料(Tcode:MM01)
ZST_MODEL
(1)Basic data2 的Material is configurable一定要选上.表示其是可被配置的物料
(2) 在Classification view选上分类ZST_MODEL(Class和物料同名),带出上面所设定的三特
征值.
(3)MRP1 view 的MRP type可设置成ND不跑MPR
(4)MRP2 view Special procurement 设成50,就是说通常这料是Phantom Part,关于phantom part请看例1-Phantom Part的使用.

ZZJ1-ZZJ3,ZBOX1-ZBOX3,ZPAK1-ZPAK3
根据实际需要,如果你需要进行库存管理,和普通物料一样,如不需要可简称phantom part.
注意:这层物料并不需要建立Classification .
建立Super BOM(CS01)

从图5-[1]进去维护Object Dependency(注意在创建OD时不要直接双击item进去维护).

图6-[2]Rltnship使用BOM material加Item.然后到图6-[1]维护Dependency,Dependency维护如图7.

图7-[1]$ROOT表示跟特征,$ROOT.ZST_ZJ表示其下的特征ZST_ZJ(请回顾图3-[3]), = ‘ZJJ1’ ,ZJJ1表示特征ZST_ZJ的特征值ZJJ1(请回顾图2-[3]),这样就将item component ZZJ1和特征ZST_ZJ的特征值ZZJ1 link上了.
同样地,建立好图5-[2]的其他component的OD ,比如ZBOX1的SEL. Condition是
ZST_MODEL_ZBOX1,Dependency是$ROOT.ZST_BOX = ‘ZBOX1’ . ZPAK1 Condition是
ZST_MODEL_ZPAK1,Dependency是$ROOT.ZST_PAK = ‘ZPAK1’ 等.
*如需要你也可使用$ROOT.ZST_PAK in ‘ZPK1’.
至此,一个超级BOM就建立好了,下面假设你做了一电子商务网站,允许用户在3种主机3种机箱3种包装选择.选择好了自动建立Sales part和BOM,为此你建立sales part ZMODEL1.
建立configurable profile (Tcode:CU41)
为配置物料建立configurable profile .

进去后class type 选300,保存就为configurable material ZST_MODEL建好了configurable profile .
(1) 建立sales part MM01
如图8,在basic data2 view中选择Configurable material ZST_MODEL,然后进classification view.

到MRP3 view,如图9-[3],只要简单按”copy x-plant configuration”按钮就可,接下来在使用CS40对configurable material ZST_MODEL做个link,sales model物料ZMODEL1的BOM就有了,你必须使用CS11/CS12/CS13等查看而不能使用CS02/CS03查看配置BOM.
*假设在sales model物料ZMODEL1选特征值是ZZJ1, ZBOX1,ZPAK1,如图8-[5]

(2) Link to Super BOM (Tcode: CS40)
CS40 将ZMODEL1和Configurable material ZST_MODEL link 上

如图11-[1],单击按钮’All Allocs to BOM’将ZMODEL1和ZST_MODELlink上.

(3) Check with CS12
使用CS12检查ZMODEL1的BOM,OK .

熟悉make-to order之前,先说一下什么是Super BOM,因为一般make-to order和这该死的Super BOM,变式(配置)BOM通常总鬼混在一起.
降低材料成本(11%-40%)、提高生产率(6%-45%)、加快资金周转(8%-3
5%)、提高用户服务水平(10%-27%)?要是让我吹,干脆就一口咬定俺家SAP不但能滋阴壮阳关还能延年益寿得啦.
一 Classification System(分类系统)简介
|
顾名思义,分类系统就是根据一定的特征组合相似对象从而使你能快速查找到所需的对象.SAP预定义了许多对象类型你几乎不要做,实际上应用分类系统基本上不用做任何或很少设置就可直接使用
首先明白这几概念,请看图1[4]-[6] .(MD,自己看帮助去)
1. Object(对象)
物料,供应商,客户,批次,BOM等都可作为可分类的对象
2. Object key(对象关键码)
3. object type
4. class
5. class type
6. characteristic
7. class/characteristic group
|
[1]Define Default Settings
状态 1 (released)被预定义给所有的特征(characteristics),除非你有特殊需求,SAP推荐不做任何更改
[2]Define特征组
[3]Define特征状态
二 Super BOM和配置BOM应用举例
|
我做过的一个CTO的项目是.算了,还是假设你为电脑厂家设计一CTO项目,客户通过网站选定主机,机箱和产品包装材料,假设每种有3中选择,如使用普通的BOM,就有3*3*3中BOM组合,实际上可能是9*9*8或更多选择.
客户通过网站选定机型后通过程序Link到ERP系统,自动产生material number和相关BOM然后汇集到生产部门生产.
典型的应用还发生在制鞋制衣行业.
|
1.建立特征(Tcode:CT04)
如图1.
Restrictions是做限制的,比如选择了ZST_ZJ特征不能用于某Class type,这很好理解.
上面建立了特征ZST_ZJ(主机)包含3个特征值ZZJ1-ZZJ3同样地,建立特征ZST_BOX包含特征值ZBOX1-ZBOX3,特征ZST_PAK包含特征值ZPAK1-ZPAK3.
建立类(CL01/CL02/CL03)
现在的问题是如何将Characteristic/Class和material master data/BOM master data 挂沟.
为了不混淆视听,通常的做法是各层物料尽量采用class名称,特征值(特征这层似乎不要建立物料)的名称,为了方便理解,假设配置BOM下面再没有可配 置子BOM,于是,本例你需要建立的material No是ZST_MODEL(Super BOM top-level material),ZZJ1-ZZJ3,ZBOX1-ZBOX3,
ZPAK1-ZPAK3 .
为了方便理解,再假设每个主机,机箱和包装材料都由3个material component,比如ZZJ1由970000-970002组成,ZZJ2由970003-970005组成,ZZJ3由970005-970008 组成. 依此类推,机箱ZBOX1-ZBOX3和包装材料ZPAK1-ZPAK3的material component从970009-970026(假设每组件有3component组成).
建立物料(Tcode:MM01)
ZST_MODEL
(1)Basic data2 的Material is configurable一定要选上.表示其是可被配置的物料
(2) 在Classification view选上分类ZST_MODEL(Class和物料同名),带出上面所设定的三特
征值.
(3)MRP1 view 的MRP type可设置成ND不跑MPR
(4)MRP2 view Special procurement 设成50,就是说通常这料是Phantom Part,关于phantom part请看例1-Phantom Part的使用.
ZZJ1-ZZJ3,ZBOX1-ZBOX3,ZPAK1-ZPAK3
根据实际需要,如果你需要进行库存管理,和普通物料一样,如不需要可简称phantom part.
注意:这层物料并不需要建立Classification .
建立Super BOM(CS01)
从图5-[1]进去维护Object Dependency(注意在创建OD时不要直接双击item进去维护).
图6-[2]Rltnship使用BOM material加Item.然后到图6-[1]维护Dependency,Dependency维护如图7.
图7-[1]$ROOT表示跟特征,$ROOT.ZST_ZJ表示其下的特征ZST_ZJ(请回顾图3-[3]), = ‘ZJJ1’ ,ZJJ1表示特征ZST_ZJ的特征值ZJJ1(请回顾图2-[3]),这样就将item component ZZJ1和特征ZST_ZJ的特征值ZZJ1 link上了.
同样地,建立好图5-[2]的其他component的OD ,比如ZBOX1的SEL. Condition是
ZST_MODEL_ZBOX1,Dependency是$ROOT.ZST_BOX = ‘ZBOX1’ . ZPAK1 Condition是
ZST_MODEL_ZPAK1,Dependency是$ROOT.ZST_PAK = ‘ZPAK1’ 等.
*如需要你也可使用$ROOT.ZST_PAK in ‘ZPK1’.
至此,一个超级BOM就建立好了,下面假设你做了一电子商务网站,允许用户在3种主机3种机箱3种包装选择.选择好了自动建立Sales part和BOM,为此你建立sales part ZMODEL1.
建立configurable profile (Tcode:CU41)
为配置物料建立configurable profile .
进去后class type 选300,保存就为configurable material ZST_MODEL建好了configurable profile .
(1) 建立sales part MM01
如图8,在basic data2 view中选择Configurable material ZST_MODEL,然后进classification view.
到MRP3 view,如图9-[3],只要简单按”copy x-plant configuration”按钮就可,接下来在使用CS40对configurable material ZST_MODEL做个link,sales model物料ZMODEL1的BOM就有了,你必须使用CS11/CS12/CS13等查看而不能使用CS02/CS03查看配置BOM.
*假设在sales model物料ZMODEL1选特征值是ZZJ1, ZBOX1,ZPAK1,如图8-[5]
(2) Link to Super BOM (Tcode: CS40)
CS40 将ZMODEL1和Configurable material ZST_MODEL link 上
如图11-[1],单击按钮’All Allocs to BOM’将ZMODEL1和ZST_MODELlink上.
(3) Check with CS12
使用CS12检查ZMODEL1的BOM,OK .
Super BOM应用步骤总结
(1) 建立特征和特征值(Tcode :CT04)
在本例你建立了特征ZST_ZJ表示电脑主机包含3特征值(主机类)ZZJ1-ZZJ3,特征ZST_BOX包含3特征类型(机箱)ZBOX1-ZBOX3,特征ZST_PAK包含3特征值(电脑包材)ZPAK1-ZPAK3 .
(2) 建立类(Tcode:CL01)
在本例你建立ZST_MODEL类,class type是300(variant)
(3) 建立物料
首先建立ZST_MODEL,这是一个configurable material,可建成phantom part,为了便于管理,将它建立和class ZST_MODEL同名称,同样按9个特征值建立物料
(4) 建立BOM.
假设物料ZZJ1-ZZJ3,ZBOX1-ZBOX3,ZPAK1-ZPAK3有BOM,这些物料是普通的part(如需要,这些料也可建立成configurable material,这也没什么复杂的,本例只是为了简化实例),BOM也是普通的BOM
然后为Configurable material ZST_MODEL建立Super BOM包含ZZJ1-ZZJ3,
ZBOX1-ZBOX3,ZPAK1-ZPAK3,建立OD(Object Dependency)
(5)建立configurable Profile (Tcode:CU41).
为configurable material ZST_MODEL建立configurable profile
(6)建立MTO物料及其从Super BOM派生出配置BOM
假设客户选择了ZZJ1,ZBOX1,ZPAK1组装电脑,为止产生了物料ZMODEL1,指想ZST_MODEL ,在classification view选取特征值ZZJ1,ZBOX1和ZPAK1.
(7) Link to configurable material (Tcode:CS41)
将ZMODEL1 link to ZST_MODEL,就完成了配置BOM的应用.
*建议测试ZST_MODEL,ZMODEL1,ZZJ1-ZZJ3,ZBOX1-ZBOX3,ZPAK1-ZPAK3建立物料,然后下面component 使用系统里的,希望通过上面你对Super BOM和配置BOM有全面的了解.
*实际应用中,一Top lever的Super BOM下的component也可能是一Super BOM.
2013年4月5日 星期五
sap供应商的添加
http://skylfx.blog.163.com/blog/static/7523122420088116345785/
sap供应商的添加
创建一个customer, 第一步需要为其创建一个account group,为什么呢?
让我们看看account group的定义:
The
Account group controls the amount of data and the response for customer
master records.帐户组确定对于一个客户的不同伙伴功能(partner function)以及该客户的主记录编号.
也就是说,account group有两个主要的功能(当然可能有其它)
A:确定根据这个account group所创建的客户可以具备哪些功能(即partner function).
B:生成的客户,会怎么样来进行编号.
创建account group方法:
IMG:
-->Lojistics-General
-->Business Partner
-->Customers
-->Control
-->Define Account Groups and Field Selection for Customers
注意事项
A: Number range: F4功能选择一个range,请注意,其中的EXT如果打上X,表明客户编号由创建指指定,没打X表明编号将由系统自动产生.
B: PartnDet.Proc.: 这个在做完第二步创建一个Partner determination procedure ,并assign给account group后会自己显示出来.
创建一个customer, 第二步需要为其创建一个Partner determination procedure,为什么呢?
A
partner determination procedure is where you determine which partner
functions should or must appear on the sales documents. 利用这一个partner
determination procedure 来决定了一个account group中需要加入哪些partner function。
{{{这里需要了解一下,什么是partner funtion?
partner
function represent the roles played by business partners within the
business transaction,也就是说,partner function代表的是业务事务(business
transaction)中partner所对应的角色.
例如sold-to-
party,Ship-to-party,Bill-to party,Payer,Forwarding agent,Sales
employee,Customs agent等等在现实市场中可以抽象出来的角色,放到SAP系统中,以角色实现代表具有一定的功能}}}
创建Partner Determination procedure的方法:
IMG
->Sales and Distribution
->Basic Functions
->Partner Determination
->Set up Partner Determination
注意事项
1, 新建一个procedure,选中,双击partner functions in procedure,为此procedure加入partner function ,常见有四项:
SP:Sold-to party;BP:Bill-to party;PY:Payer;SH:Ship-to party.这些项目在用于创建sales order等信息时,会显示出来.
2, 双击partner determination procedure assignment,将新建好的procedure assign给所要的account group,此时,account group 的两个功能已经齐全.
创建一个customer, 第三步需要为Account grout定义Screen layout,为什么呢?
如果我们没有做这一步,会发现,使用XD01或者VD01来进行customer创建的时候,里面出现的tab只有address,并且address tab里只有一两个字段.而一个健全的customer是应该需要我们维护很多数据的.
所以,这里就是我们漏掉的Define Account Groups with Screen Layout (Customers).
Define Account Groups with Screen Layout (Customers)的方法:
IMG
-->Financial Accounting
-->Accounts Receivable and Accounts Payable
--> Customer Accounts
-->Master Data
-->Preparations for creating Customer Master Data
-->Define Account Groups with Screen Layout (Customers)
选
中所创建的account group,在Field Status的block中,有三个主数据:General data;Company code
data;Sales
data,双击进入每一个,可以对每一个主数据需要在建customer里的屏幕上输出,让用户填写的字段进行设定.每一个设定完成之后,整个
Account Groups的screen就好了.
在创建一个customer常见问题: 1,Error: Account group uses internal no. assignment, leave blank
Answer: Number range 中的EXT没有X,表明是系统给出客户编号.
2,建Customer时,tab只有address.
Answer:没有进行第三步的工作.
2013年3月15日 星期五
Month End and Year End Closing Operations
| Month End Closing Operations | |||||
| Module | Sr. No. | Process Description | T Code / Menu-path | Periodicity(D/W/M) | Person Responsible / Location |
| MM | 1 | Inventory balance | Programm ZBIL | Monthly | Logistic |
| MM | 2 | Inventory Revaluation | MR22 Logistics > Materials Management > Valuation > Change in Material Price > Change Material Prices |
Monthly | Corporate Accounts |
| MM | 3 | Physical Inventory Differences-Post , after Physical counting | MI07 - Logistics > Materials Management > Physical Inventory > Difference > Post (+ MI01 MI04 ) |
Monthly | Depot/corporate accounts after prior approval from head of finance |
| MM | 4 | PO Closure | ME22N - Logistics > Materials Management > Purchasing > Purchase Order > Change |
Monthly | Purchase dept |
| SD | 5 | Check Billing Due List for the last days in the month | VF04 - * *Logistics > Sales and Distribution > Billing > Billing Document > Process Billing Due List |
Monthly | Logtistics/Sales Admin. |
| SD | 6 | General check of SD billing flows of Goods Issues without invoices | VL06F - Information Systems > General Report Selection > Sales and Distribution >Shipping > Delivery Monitor |
Monthly | Logtistics/Sales Admin. |
| FI | 7 | General account manual FI postings | FB50 / KE21N | Monthly | Corporate Accounts |
| SD | 8 | Release SD billing to Accounting | VFX3 - Logistics > Sales and Distribution > Billing > Billing Document > Blocked Billing Docs |
Monthly | Logtistics/Sales Admin. |
| COPA | 9 | Reconciliation between CO/FI/SD | KEAT Accounting > Controlling > Profitability Analysis > Tools > Analyze Value Flows |
Monthly | Reporting |
| FI & COPA |
10 | Invoicing Regularisation of deliveries non invoiced | FB50 Accounting -> Financial Accounting-> General Ledger -> Document Entry -> FB50 - Enter G/L Account Document |
Monthly | Reporting |
| FI-CO-SD | 11 | Ensure Return sale order -credit memo and transfer posting tally | KE24/MB51 | Monthly | Sales Admin/Reporting/Accounts |
| Payroll | 12 | Running of payroll interface | NON STANDARD | Monthly | IT/Corporate Accounts |
| MM | 13 | Open next MM Period | MMPV Logistics > Material Managements > Material Master > Other > Close Period | Monthly | Manual orAutomated back ground job |
| FI | 14 | Open FI Posting Periods | OB52 Accounting -> Financial Accounting-> General Ledger -> Environment -> Current Settings -> S_ALR_87003642 - Open and Close Posting Periods | Monthly | Corporate Accounts |
| CO/IM | 15 | Settlement of Investment Orders to AUC | KO8G Accounting > Controlling > Internal Orders > Period-End Closing > Single Functions > Settlement > KO8G Collective Processing |
Monthly | Reporting /Corporate Accounts |
| CO/IM | 16 | Settlement of Investment Orders to Fixed Assets | KO8G Accounting -> Investment Management -> Internal Orders ->Period-End Closing->Single Functions > Settlement > KO8G - Collective Processing |
Monthly | Reporting/Corporate Accounts |
| FI | 17 | Depreciation Run | AFAB -Accounting -> Financial Accounting-> Fixed Assets -> Periodic Processing -> Depreciation Run -> AFAB - Execute |
Monthly | Reporting/Corporate Accounts |
| FI | 18 | Maintain Exchange Rates | OB08 Accounting -> Financial Accounting-> General Ledger -> Environment -> Current Settings -> S_BCE_68000174 - Enter Translation Rates |
interface MEDECO | |
| FI | 19 | Post Accrual / Deferral Entries | FBS1 Accounting -> Financial Accounting-> General Ledger -> Periodic Processing -> Closing -> Valuate -> FBS1 - Enter Accrual/Deferral Doc. |
Monthly | Corporate Accounts |
| FI | 20 | Post Recurring Entries | F.14 Accounting -> Financial Accounting-> General Ledger -> Periodic Processing -> Recurring Entries -> F.14 - Execute |
Depends on Nature of entry and target accrual dates | Corporate Accounts |
| FI | 21 | Reverse Accrual / Deferral Entries | F.81 Accounting -> Financial Accounting-> General Ledger -> Periodic Processing -> Closing -> Valuate -> F.81 - Reverse Accrual/Deferral Document |
Monthly | Corporate Accounts |
| FI | 22 | Receivables and Payables Regroupements | F101 Accounting -> Accounts Receivables -> Periodic Processing -> Closing -> Regroup -> F101 - Receivables/payables | Monthly | Corporate Accounts |
| FI | 23 | GR/IR Clearing | F.13 Accounting -> Financial Accounting-> General Ledger -> Periodic Processing -> Automatic Clearing -> F.13 - Without Specification of Clearing Currency | Monthly | Corporate Accounts |
| FI | 24 | Revaluation of Foreign Currency Balances | F.05 Accounting -> Financial Accounting-> General Ledger -> Periodic Processing -> Closing -> Valuate -> F.05 - Foreign Currency Valuation | Monthly/Weekly | Corporate Accounts |
| COCCA | 25 | Correction of FI documents for wrong cost centre entries | KB61 Accounting > Controlling > Cost Center Accounting > Actual Postings > KB61 Repost Line Items |
Weekly/Monthly | |
| CO | 26 | Period close in CO | OKP1 Accounting > Controlling > Profitability Analysis > Actual Posting > Period End Closing > Transfer Cost Center costs > Assessment | Monthly | Reporting |
| CO-FI | 27 | CO-FI Reco | S_ALR_87013603 Accounting > Controlling > Cost Element Accounting > Information System > Reports for Cost and Revenue Element Acc > Reconciliation > CO/FI Reconciliation in CoCd Currency |
Weekly/Monthly | Reporting |
| COPA | 28 | CO - PA assessment | KEU5 Accounting > Controlling > Profitability Analysis > Actual Posting > Period End Closing > Transfer Cost Center costs > Assessment | Monthly | Reporting |
| COPA | 29 | Reconciliation between CO - CCA - COPA | GR55 ZTL8 Accounting > Controlling > Cost Center Accounting > Information System > Tools > Report Painter > Report Writer > Report Group ZTL8 > Execute | Monthly | Reporting |
| COPA | 30 | RES1 Report execution and validation | KE30 Accounting > Controlling > Profitability Analysis > Information System > Execute Report |
D/W/M | Reporting |
| FI | 31 | Balance Audit Trail | S_ALR_87100205 - General Ledger >Periodic Processing > Closing > Document > Balance Audit Trail > All Accounts > S_ALR_87100205 - General Ledger from the Document File |
Monthly | Corporate Accounts |
| FI | 32 | Compact Journal | S_ALR_87012289 Accounting -> Financial Accounting-> General Ledger -> Periodic Processing ->Closing > Report > General Ledger Reports >Document > General > Compact Document Journal |
Monthly | Corporate Accounts |
| FI | 33 | VAT Liability | F.38 General Ledger >Periodic Processing > Closing > Report > F.38 - Transfer Deferred Tax | Monthly | Corporate Accounts |
| FI | 34 | VAT Liability | F-32 Accounting -> Financial Accounting-> General Ledger -> Document Entry -> F-02 - General Posting | Monthly | Corporate Accounts |
| FI | 35 | Analyse GR / IR a/c to crystalise and close the liability in the GR / IR a/c to chase up invoices | FBL3N / F.13 (TEST run and without tick " only docs which can be cleared" |
Monthly | Corporate Accounts |
| FI | 34 | Review and download the p& l and balance sheet | S_ALR_87012284 Ledger - Reporting -> Information System -> General Ledger Reports > Balance Sheet/ Profit and Loss Statement / Cash Flow ->General > Actual/Actual Comparisons ->S_ALR_87012284 | Monthly | Corporate Accounts/ Reporting |
| IM | 35 | Investment Management Report | S_ALR_87013019 Accounting -> Investment Management -> Internal Orders ->Information System ->Reports for Internal Orders ->More Reports S_ALR_87013019 S_ALR_87012816 , S_ALR_87012824 , S_ALR_87012993 , S_ALR_87012994 : |
Monthly | Reporting |
| IM | 36 | Investment Management Report | AW01N Accounting > Investment Management > Fixed Assets >Asset > AW01N Asset Explorer |
D/W/M | Reporting |
| YEAR END CLOSING OPERATIONS | |||||||
| Module | Sr. No. | Process Description | T Code / Menu-path | Preceding Dependency | Subsequent Process Impacted | Periodicity(D/W/M) | Person Responsible / Location |
| FI | 1 | Open FI Posting Periods | OB52 Accounting -> Financial Accounting-> General Ledger -> Environment -> Current Settings -> S_ALR_87003642 - Open and Close Posting Periods | Open period 13 close Normal periods 1 to 12 initially. Open Special Period 13 , only for non sales accounts ( exclude accounts 7*) |
Allows all specific en year postings | Annual | Corporate Accounts |
| FI | 2 | End year Manual FI Postings | FB50 Accounting -> Financial Accounting-> General Ledger -> Document Entry -> FB50 - Enter G/L Account Document | All specific postings for regularisation involving generation of and FI and non sales imapct -commissions on sales |
Annual | Corporate Accounts | |
| FI | 3 | Fiscal Year Change for Fixed Assets | AJRW Accounting -> Financial Accounting-> Fixed Assets -> Periodic Processing -> AJRW - Fiscal Year Change | None | 1/Calcul evaluation on next period 2/Posting to Assets Accounting in next Fiscal Year 3/reporting Budget |
Annual | Corporate Accounts |
| FI | 4 | Open FI Posting Periods | OB52 Accounting -> Financial Accounting-> General Ledger -> Environment -> Current Settings -> S_ALR_87003642 - Open and Close Posting Periods | Close Special Period 13 to 16 to be closed after full & complete finalisation. of trial balance. | All processing involving generation of and FI Document not allowed in next posting period. | Annual | Corporate Accounts |
| FI | 5 | Fixed Assets Year-End Closing | AJAB Accounting -> Financial Accounting-> Fixed Assets -> Periodic Processing -> Year-End Closing -> AJAB - Execute | After END closing period 13 =>Completion of Capitalization Activities and Posting of Final Depreciation Run for the Fiscal Year. |
Posting to Previous Fiscal Year can not be continued after the year- end closing | Annual | Corporate Accounts |
| FI | 6 | Account Reconciliation for Fixed Assets | ABST2 Accounting -> Financial Accounting-> Fixed Assets -> Periodic Processing -> Year-End Closing -> ABST2 - Account Reconciliation | After END closing period 13 => Completion of Capitalisation Activities and Posting of Final Depreciation Run for the Fiscal Year. |
Rectification of reported errors on account of Capitalisation or depreciation | Annual | Corporate Accounts |
| FI | 7 | Vendors & Customers | F.07 Accounting -> Financial Accounting-> Accounts Payable -> Periodic Processing -> Closing -> Carrying Forward -> F.07 - Balance Carry Forward | Scrutiny and closing of all Vendor & Customer accounts | Annual | Corporate Accounts | |
| FI | 8 | Balance Sheet GL | F.16 Accounting -> Financial Accounting-> General Ledger -> Periodic Processing -> Closing -> Carrying Forward -> F.16 - Balance Carry Forward | Scrutiny and closing of all GL Balance Sheet accounts | Annual | Corporate Accounts | |
| FI | 9 | P & L Items | F.16 Accounting -> Financial Accounting-> General Ledger -> Periodic Processing -> Closing -> Carrying Forward -> F.16 - Balance Carry Forward | Scrutiny and closing of all GL P & L accounts | Annual | Corporate Accounts | |
| CO | 10 | Period close in CO | OKP1 Accounting > Controlling > Profitability Analysis > Actual Posting > Period End Closing > Transfer Cost Center costs > Assessment |
FI closing done and FI period is closed for last month. | CO process and assessment cycle run,RES1 reporting | Annual | Reporting |
| CO-IM | 11 | Carry forward of open commitments for investment | KOCF Accounting > Controlling >Internal Orders > Year-End Closing > Commitment Carryforward |
Budgetory control on investment in next year | Annual | Reporting | |
| COCCA | 12 | Checking overhead report(before and after assessment run) | S_ALR_87013611 , S_ALR_87013634 , S_ALR_87013635 , S_ALR_87013625 | MIS reporting ???? | Annual | Reporting | |
| FI | 13 | Review and download the p& l and balance sheet | S_ALR_87012284 Ledger - Reporting -> Information System -> General Ledger Reports > Balance Sheet/ Profit and Loss Statement / Cash Flow ->General > Actual/Actual Comparisons ->S_ALR_87012284 | Scrutinise & Download P& L and Balance Sheet | Year end | Annual | Corporate Accounts |
| IM | 14 | Investment Management Report | _ALR_87013019 List: Budget/Actual/Commit: Accounting -> Investment Management -> Internal Orders ->Information System ->Reports for Internal Orders ->More Reports : S_ALR_87012816 , S_ALR_87012824 , S_ALR_87012993 , S_ALR_87012994 : |
Special FI periods closed |
Reporting | Annual | Reporting |
2013年3月13日 星期三
SAP FI模組與SD、MM的介面配置基本方法
http://aspromise.pixnet.net/blog/post/19896719--sap-fi%E6%A8%A1%E7%B5%84%E8%88%87sd%E3%80%81mm%E7%9A%84%E4%BB%8B%E9%9D%A2%E9%85%8D%E7%BD%AE%E5%9F%BA%E6%9C%AC%E6%96%B9%E6%B3%95
1 FI/SD 藉口配置
FI/SD通過tcode VKOA為billing設置過帳科目,用戶可以創建自己的科目定義資料表。 科目是做到COA級的,通過KOFI/KOFK這兩個condition type確定分別過帳到FI和CO憑證中。 由於PricingProc.是同SalesOrg.相關聯的,所以科目在Organization上首先要做到SalesOrg. 級,其後的AccountKey是在PricingProc.中和不同的PriceConditionType相關聯的,決定著最終銷售收入、折扣、附加 費用、預提等過到不同科目上。
2 FI/MM 藉口配置
FI/MM通過tcode OBYC為所有的庫存移動設置過帳科目,系統用不同的TransactionKey決定了不同的移動類型/業務類型,對於這些TK的含義,SAPLIB中有較為詳細的解釋,可參閱。
科 目的配置可以按照需要做在ValuationArea(Plant)和ValuationClass層。 特別是我認為FI/MM AccountDetermination中最有意思的就是TK為GBB的科目定義,其中有一個東東叫做GeneralModificationKey, 這個GMK是同MovementType直接相連的;除了很多標準的GMK之外,用戶也可以自定義,並將它們同自定義的MovementType相關聯, 以決定不同的MT連接 到不同的過帳科目上。
3 實例說明
可以按照資料到系統中配置一下,並做一些例子,有助於理解這些科目配置
3.1、對於收貨(特別是來自採購的收貨)和發票錄入IV/LIV,常用的TransactionKey為:
BSX 同ValuationClass相關聯的所有基於存貨科目的過帳
FR1、FR3 運費和關稅的清帳科目(需要通過IV/LIV做Clear,類似GR/IR科目)
FR2、FR4 運費和關稅預提科目(無需Clear)
WRX 存貨GR/IR科目
DIF SmallDifference(小金額差異),未超過發票價差容限的金額過到此科目(OMR6中定義ToleranceLimit)
KDM 處理收貨同收發票匯率不一致造成的差異過帳
KDR 處理收外幣發票時,由於四捨五入的原因造成的本幣金額同GRIR本幣金額不一致的差異過帳
UPF 處理UnplannedDeliveryCost(計畫外運費)是否單獨過到某個制定科目而不是過到存貨或價差科目
PRD 標準成本法下處理PPV的科目,即採購價差科目
3.2、對於發貨和其他庫存移動,常用的TransactionKey通常只需要關注GBB,即所謂庫存移動的抵減或對應科目,其中比較重要的一個概念就是GeneralModificationKey,這個東東是同MovemtType關聯的, 較常用的有:
AUF : 無Acct.Assignmt的PP/CO訂單的收貨和結算
BSA : 通過561/562做庫存初始化的過帳科目
INV : 庫存差異導致的收入和費用科目,一般為P+L科目
VAX/VAY: 銷售訂單的發貨成本科目
VBO : 委託加工業務,提供給供應商的庫存出貨科目
VBR : 處理內部發貨業務,如直接消耗到成本中心、資產或內部訂單等
VKA : 基於Acct.Assignmt的銷售訂單業務,如BTO、MTO業務等
VKP : 基於Acct.Assignmt的項目業務,如BTP、MTP業務等
ZOB : 無PO收退貨,如501/502
ZOF : 無PP訂單收退貨,如521/522
同 樣,你可以基於自定義的MovemtType,設置相關聯的自定義的GMK,並在GBB中指定科目。 此外,如果啟用MaterialLedger、標準成本法核算貨ProductCostbyPeriod等,相關的LKW,PRV, PRP,PRQ和PRY等也需要做相關設置,詳見幫助。
3.3 對於收貨科目設置,舉個稍複雜的例子:
A000工廠下的物料 A,ValuationClass為V000;擬在MM/InfoRecord中定價2%的採購運費,不需要通過IV/LIV清帳;價差容限定義1元以下 為SmallDifference;在採購過程中發生了計畫外運費,並希望過到制定科目上;收發票時的匯率同收貨時不同,有差異。
示例會計科目如下:
1401 原材料存貨科目
2181 預提運費
5121 計畫外運費
5122 SmallDifference
5151 匯率差異
6000 存貨GR/IR
可通過OBYC配置為:
庫存過帳 BSX A000 V000 1401
預提運費 FR2 A000 V000 2181
小額價差 DIF 5122
計畫外運 UPF 5121
匯率差異 KDM A000 V000 5151
GR/IR WRX A000 V000 6000
收貨時的分錄為(MAP計價方式,忽略VAT):
Dr. 1401 1020.00
Cr. 6000 1000.00
2181 20.00
收採購發票時的分錄為:
Dr. 6000 1000.00
5121 100.00
5122 0.80
5151 1.20
Cr. A/P 1102.00
收運費發票的分錄:
Dr. 2181 20.00
Cr. A/P 20.00
比 如你用MB1A通過201做PGI,在OMJJ中你可以看到有一個Account Grouping,雙擊進去後有如下一條String: 201 K X X WA03 2 GBB VBR。其中K表示Consumption Posting,而GBB VBR是連接Account的關鍵。用OBYC,選擇GBB(指庫存抵減過帳)雙擊,裏面比較複雜的設置有可能是:Valuation Modif.(a Plant) > General Modif.(VBR) > VC > Account!。
這樣,201就通過GBB,VBR同相關科目聯到了一起。
當然,這是個很簡單的例子,SAP對於不同的Special Stock,數量、金額是否更新,都會在OMJJ 中引用不同的所謂(Value String),這個東東比較複雜,我是做FICO的,瞭解得不多,不過很值得研究啊.
101 是針對採購、生產和成本控制訂單收貨的MT,在OMJJ>Account Groupg. 中你可以看到常用的Movemt. Indicator是B(採購訂單)和F(生產訂單),請特別注意看Consumption Posting(A,V,E,P...)欄位有值的那些行,他們鏈結的Transaction Key是KBS,這個KBS叫做Account Assigned Purchase-Order,在OBYC中是無法手工配置科目的。SAP在Movement Type的Post String/Value String中處理這種KBS時,會直接指向庫存科目,即在OBYC中,Transaction Key為BSX庫存科目定義。
剛才提到在OMJJ>Account Grouping中的101那些行,它們的Value String是WE06,你可以用t-code SE16看一個表叫做T156W,查看WE06的那些行,你會發現:
WE06 01 KBS
WE06 02 WRX
這KBS剛才說過了,那麼這個WRX你會在OBYC中發現,它定義的是GR/IR的科目,即收貨時
Dr. Inventory (KBS/BSX)
Cr. GR/IR (WRX)
用這種方法,你就可以分析其他的MT了,如同101類似的105/106,122/123等,蠻複雜的。
另外,在SAP Library中的相關IMG配置解釋得也不完整,有很多Transaction Key在4.6C 的Library都沒有說明,只能自己研究了。
我們曾經用過的方法,就是用不同的MT做庫存移動,然後在程式中設動態中斷點,依據那些 Value String,跟蹤它到底用的是那些Transaction Key和科目定義。
我將實際畫面post如下:
T-code : OMJJ
可以看到Transaction Key是KBS,當此PO不用到account assignment時(不用手動指定會計科目),SAP就會到Transaction Key=BSX尋找會計科目,而另一個Transaction Key則是WRX
T-code : OBYC

於是在table BSIS看到的結果如下:(5111601為成本調整-進貨價差-直材)
1 FI/SD 藉口配置
FI/SD通過tcode VKOA為billing設置過帳科目,用戶可以創建自己的科目定義資料表。 科目是做到COA級的,通過KOFI/KOFK這兩個condition type確定分別過帳到FI和CO憑證中。 由於PricingProc.是同SalesOrg.相關聯的,所以科目在Organization上首先要做到SalesOrg. 級,其後的AccountKey是在PricingProc.中和不同的PriceConditionType相關聯的,決定著最終銷售收入、折扣、附加 費用、預提等過到不同科目上。
2 FI/MM 藉口配置
FI/MM通過tcode OBYC為所有的庫存移動設置過帳科目,系統用不同的TransactionKey決定了不同的移動類型/業務類型,對於這些TK的含義,SAPLIB中有較為詳細的解釋,可參閱。
科 目的配置可以按照需要做在ValuationArea(Plant)和ValuationClass層。 特別是我認為FI/MM AccountDetermination中最有意思的就是TK為GBB的科目定義,其中有一個東東叫做GeneralModificationKey, 這個GMK是同MovementType直接相連的;除了很多標準的GMK之外,用戶也可以自定義,並將它們同自定義的MovementType相關聯, 以決定不同的MT連接 到不同的過帳科目上。
3 實例說明
可以按照資料到系統中配置一下,並做一些例子,有助於理解這些科目配置
3.1、對於收貨(特別是來自採購的收貨)和發票錄入IV/LIV,常用的TransactionKey為:
BSX 同ValuationClass相關聯的所有基於存貨科目的過帳
FR1、FR3 運費和關稅的清帳科目(需要通過IV/LIV做Clear,類似GR/IR科目)
FR2、FR4 運費和關稅預提科目(無需Clear)
WRX 存貨GR/IR科目
DIF SmallDifference(小金額差異),未超過發票價差容限的金額過到此科目(OMR6中定義ToleranceLimit)
KDM 處理收貨同收發票匯率不一致造成的差異過帳
KDR 處理收外幣發票時,由於四捨五入的原因造成的本幣金額同GRIR本幣金額不一致的差異過帳
UPF 處理UnplannedDeliveryCost(計畫外運費)是否單獨過到某個制定科目而不是過到存貨或價差科目
PRD 標準成本法下處理PPV的科目,即採購價差科目
3.2、對於發貨和其他庫存移動,常用的TransactionKey通常只需要關注GBB,即所謂庫存移動的抵減或對應科目,其中比較重要的一個概念就是GeneralModificationKey,這個東東是同MovemtType關聯的, 較常用的有:
AUF : 無Acct.Assignmt的PP/CO訂單的收貨和結算
BSA : 通過561/562做庫存初始化的過帳科目
INV : 庫存差異導致的收入和費用科目,一般為P+L科目
VAX/VAY: 銷售訂單的發貨成本科目
VBO : 委託加工業務,提供給供應商的庫存出貨科目
VBR : 處理內部發貨業務,如直接消耗到成本中心、資產或內部訂單等
VKA : 基於Acct.Assignmt的銷售訂單業務,如BTO、MTO業務等
VKP : 基於Acct.Assignmt的項目業務,如BTP、MTP業務等
ZOB : 無PO收退貨,如501/502
ZOF : 無PP訂單收退貨,如521/522
同 樣,你可以基於自定義的MovemtType,設置相關聯的自定義的GMK,並在GBB中指定科目。 此外,如果啟用MaterialLedger、標準成本法核算貨ProductCostbyPeriod等,相關的LKW,PRV, PRP,PRQ和PRY等也需要做相關設置,詳見幫助。
3.3 對於收貨科目設置,舉個稍複雜的例子:
A000工廠下的物料 A,ValuationClass為V000;擬在MM/InfoRecord中定價2%的採購運費,不需要通過IV/LIV清帳;價差容限定義1元以下 為SmallDifference;在採購過程中發生了計畫外運費,並希望過到制定科目上;收發票時的匯率同收貨時不同,有差異。
示例會計科目如下:
1401 原材料存貨科目
2181 預提運費
5121 計畫外運費
5122 SmallDifference
5151 匯率差異
6000 存貨GR/IR
可通過OBYC配置為:
庫存過帳 BSX A000 V000 1401
預提運費 FR2 A000 V000 2181
小額價差 DIF 5122
計畫外運 UPF 5121
匯率差異 KDM A000 V000 5151
GR/IR WRX A000 V000 6000
收貨時的分錄為(MAP計價方式,忽略VAT):
Dr. 1401 1020.00
Cr. 6000 1000.00
2181 20.00
收採購發票時的分錄為:
Dr. 6000 1000.00
5121 100.00
5122 0.80
5151 1.20
Cr. A/P 1102.00
收運費發票的分錄:
Dr. 2181 20.00
Cr. A/P 20.00
比 如你用MB1A通過201做PGI,在OMJJ中你可以看到有一個Account Grouping,雙擊進去後有如下一條String: 201 K X X WA03 2 GBB VBR。其中K表示Consumption Posting,而GBB VBR是連接Account的關鍵。用OBYC,選擇GBB(指庫存抵減過帳)雙擊,裏面比較複雜的設置有可能是:Valuation Modif.(a Plant) > General Modif.(VBR) > VC > Account!。
這樣,201就通過GBB,VBR同相關科目聯到了一起。
當然,這是個很簡單的例子,SAP對於不同的Special Stock,數量、金額是否更新,都會在OMJJ 中引用不同的所謂(Value String),這個東東比較複雜,我是做FICO的,瞭解得不多,不過很值得研究啊.
101 是針對採購、生產和成本控制訂單收貨的MT,在OMJJ>Account Groupg. 中你可以看到常用的Movemt. Indicator是B(採購訂單)和F(生產訂單),請特別注意看Consumption Posting(A,V,E,P...)欄位有值的那些行,他們鏈結的Transaction Key是KBS,這個KBS叫做Account Assigned Purchase-Order,在OBYC中是無法手工配置科目的。SAP在Movement Type的Post String/Value String中處理這種KBS時,會直接指向庫存科目,即在OBYC中,Transaction Key為BSX庫存科目定義。
剛才提到在OMJJ>Account Grouping中的101那些行,它們的Value String是WE06,你可以用t-code SE16看一個表叫做T156W,查看WE06的那些行,你會發現:
WE06 01 KBS
WE06 02 WRX
這KBS剛才說過了,那麼這個WRX你會在OBYC中發現,它定義的是GR/IR的科目,即收貨時
Dr. Inventory (KBS/BSX)
Cr. GR/IR (WRX)
用這種方法,你就可以分析其他的MT了,如同101類似的105/106,122/123等,蠻複雜的。
另外,在SAP Library中的相關IMG配置解釋得也不完整,有很多Transaction Key在4.6C 的Library都沒有說明,只能自己研究了。
我們曾經用過的方法,就是用不同的MT做庫存移動,然後在程式中設動態中斷點,依據那些 Value String,跟蹤它到底用的是那些Transaction Key和科目定義。
我將實際畫面post如下:
T-code : OMJJ
可以看到Transaction Key是KBS,當此PO不用到account assignment時(不用手動指定會計科目),SAP就會到Transaction Key=BSX尋找會計科目,而另一個Transaction Key則是WRX
T-code : OBYC

於是在table BSIS看到的結果如下:(5111601為成本調整-進貨價差-直材)
訂閱:
文章 (Atom)



