[T-code "VKM3" for release credit
block].
[T-code "VKM4" is for sales
document & delivery document]
[T-code "VKM5" is for release
delivery block]
how system should respond, if order
is blocked for credit i.e. whether to
give warning message or error
message or no message.
while creating sales order if
customer credit limit exceed then
system will block the order for
credit.
while creating sales order, if user
changes any of the critical fields
then system will block the order for
credit even though the customer is
having enough credit balance.
if we maintain Max. Open item %,
then while creating sales order
system will check is there any open
item existing for this customer or not
It is nothing but
overdue item.
After releasing the order which is blocked
for credit, if user is changing the value in
that order then system will again block the
order for credit.
After releasing the order which is blocked
system will perform credit check for credit, if there is no further process
while entering the line item in sales within the number of days mentioned here
document.
Payer is checked, if customer have
multiple payers. Payer Check is only
applicable only for open item and oldest
open item.
In static it updates all open order values,
open delivery In Dynamic it updates all You have Open Orders for one year &
open order values, open
values, open invoice values and open item system will perform credit check while you only want to consider Sales Order for
creating order and if customer credit limit next three months, then set 3 in Horizon
values. is exceed then system will block the order.
& system will NOT consider any open
Order after three months.
system will perform credit check while
creating delivery document. The blocked
order values will not be update into
credit management (FD32) .
In Dynamic it updates all open order if we maintain Max. Doc. Value. then
values, open while creating sales order if sales order
Delivery values, open invoice values and value exceeds Max. Doc. value
open item
values but any open order if the delivery
creation date
is exceeding horizon date then it will not
update in
Credit management (FD32).
Dunning is the process of sending
reminders to the customers, whose
payment is delayed. Dunning
configuration done by FI consultant.
if clients‟ requirement related to credit management is
not fulfilling with standard configuration then we use
use user exits. SAP has provided 3 user exits if we are
using 1st user then check user 1, if we are using 2nd user
exits then check user 2 and if we are using 3rd then
check user 3.
 Configuration:
Item cat grp: BANC
Item Cat: TAB
Schedule line: CB
movement type: 101

Configuration:
Configuration:
PO Type: UB
PO Type: UB
Del. Type: NLR
Del.Type: NL
Item category: NLRN
Item Category: NLN
Schedule line: NR
Schedule Line cat.: NN
Movement type: 677& 671
Movement Type: 641 & 647
copy control: DL-NL
Billing type: F8

Inter company STO:

Inter company STO Return:
Process: Configuration:
Configuration:
1. ME21N (PO) PO Type: NB
PO Type: NB
2. VL10D (Delivery) Del. type: NLCC
Del. Type: NCR
3. VF01(F8)- Invoice Item Cat.: NCL
Item cat: NCRN
4. MIGO (In case 2 step) Schedule line: NC
Schedule line: NS
Billing type: IV
movement type: 675 & 673
Movement type: 643 & 645
Configuration:
Item category: TAS
Billing relevance: F
Schedule line category: CS
Order Type: NB
Item Category: 5
Acct. Assign grp: 1
Billing qty: F
Copy Control: OR-F2
 PR: ME51N
PO: ME21N
Table: EKPO, EKKO
VOV6: maintained order type
NB for PR automatic
VOV7: PO automatic check

Consignment Process:
VOV7 VOV6 0VLP M0 type
Consign Fill up(CF): KBN E1 LF 631
Cosign Issue (CI): KEN C1 LF 633
Consign Return(CONRN): KRN D0 LR 634
Consign Pickup(CP): KAN F1 LR 632

Return Order(RE): REN DN LR 651,653

Bill type: RE