David's Untitled Life

LO615 Billing中的一个练习。感觉这是一个相对不错的练习(培训中大部分练习感觉都是鸡肋) 一个down payment的billing过程涉及到了billing plan以及FI clear过程。短短几步但是可以看出billing plan的作用和clear的过程。

-1 Create a standard order (OR) for customer T-S66F## (sales organization 1000,
distribution channel 10 and division 00). This customer orders an elevator (material
number: T-FS2##). The purchase order number is ##LO615-AZ.

2-1-1 Go to the billing plan.
Select the item and choose →→ goto->item->billing plan

2-1-2 Create an invoice for the down payment request.

Enter the order number above and choose the to
restrict the dates as described above.

=> Billing type FAZ is used for billing the down payment request

2-1-3 The customer paid the down payment that was figured into the invoice. Post the payment.
Accounting->FI->Customer->Document Entry->Down Payment->Down payment
Doc Date: current date
customer account: 1280
Special G/L indicator: A
Bank Account:113100
Amount: Refer FI Doc generated by billing doc
Choose Request

Select the down payment requests in the list and choose .
Save.

2-1-4 Now execute the milestone billing process for the first settlement period

=> Two items appear in the billing document:
The amount from the first partial billing document and the down payments
made by the customer that still need to be settled

2-1-5 How could you arrange for the down payment to be only partially calculated
into the first partial invoice?

Condition type AZWR is used especially for down payment processing. If you
only want to carry out partial settlement, you can select the down payment item
to be settled in the billing document, branch to the pricing screen, and change
the value of condition type AZWR.

2-1-6 Check the document flow for this order.

IDES与培训环境数据对应：
Company code 1000 1000

Sales organization 1000 1000

Distribution channel 10 or 14 10 or 14

Division 00 00

Shipping point 1200 1200

Plant 1200 1200

Customer T-S66A## 2141

T-S66B## 2141

T-S66C## 2141

T-S66D## 2141

T-S66E## 1171

T-S66F## 1280

Materials T-ASA## M-06

T-ASB## M-07

T-ASC## M-08

T-ASD## M-09

T-ZS2## REPAIR_SERVICE

T-FS2## E-1002

我们知道一般跑BDC用sy-subrc判断是否成功是不准确的。要用BDC的message table。
今天reivew一个物料主数据的interface程序，用得subrc，在我DEBUG的时候就出现了有意思的事情。这个MM01是写在一个subroutine里的，如果我直接F6，过掉这个subroutine没有任何问题，说明subrc为0。如果我F5跟了进去，CALL TRANSACTION之后，SUBRC是不等于0的，是1001.但是BDC MESSAGE是两条S型的。

除此以外，BDC程序的DEBUG还有很多奇怪的好玩的现象，比如无论返回的MESSAGE是否都是S型，数据都没有成功更新，只有将MODE改为一屏一屏跟进去才行。但是如果不DEBUG直接后台跑就不会有问题。呵呵~~~ BDC确实应该被BAPI替代掉。好多问题很诡异的。