Credit management activation with letter of credit

Hi Sap guru
I have one queries regarding customer credit limit effect with LC document.
If i creating one LC document for customer after assign to sales order for that perticular customer, it should effect the credit limit of that customer.
In which field it should effect the custmer credit master FD32.
in secured liability field , secured receviable field , or the receviable field .
Can any body tell ,me what is the process of LC attachment with sales order if the credit management is active in company code , and what is the effect in customer credit expouser.
Thanks in advance .
Regards
Anjan Kumar Jha

Hi Anjan
It is the aim of every credit policy to reduce the risk represented by customer receivables.
Along with Credit Management, several other Payment Guarantee Forms within the
business processes are explored. These include letters of credit and payment cards.
These payment guarantee forms differ in the level of security they can offer and are all
integrated within Risk Management.
When a payment guarantee is used (for example, a letter of credit), the system first tries to
provide the optimum in risk minimization. If this is not possible, then Credit Management in
a second step is used to create a credit limit and therefore restrict the level of risk.
Letters of credit are used predominantly for large -scale export transactions, whereas cre dit
while Cards are more important for Retail transactions.
You create a Letter of credit by using VX11 after creating that you assign that in billing tab of sales order in risk Management Financial doc number.
keep in mind the incoterms of Letter of Credit and Sales order should be same.
Reward if helpful
Thanks & Regards
Abhishek Swarup

Similar Messages

Purchase with Letter of Credit

Hi Experts..
Can we manage purchase transaction with letter of credit in SAP Business One?
Thank you.

Hi ,
Check below threads:
Letter of credit management using SAP business one
Re: Letter of Credit management in SAP Business one
Hope this willhelp you.
Thanks,
Neetu

Credit managment against payment terms and credit limit

Dear All,
I have two query against credit management
1 Can We maintain credit managment as per payment days. My client want system should give bolck as per payments days,say if payment terms is 30 days and within 30 days customer has not made payment against invoice so sales order should block. ( sales order will create but shown as block)
2 Credit block with ref to credit limit given to customer, they want credit block with reference to open order.open delivery and open invoice. Means system will check all open order,all open deliveries and all open invoice while considering credit limit.and give the block accordingly.
I am sure about credit limit but how to give block according to payment days (payment terms) and how to give path to check all open order,all open deliveries and all open invoice.
waiting for you valuable input.
Thank you
SD Consultant

Hello,
In OVA8, for the combination of credit group & risk category you maintain the following
(1) CHECK against DYNAMIC with reaction C & TICK in BLOCK
NOTE:path to check all open order,all open deliveries and all open invoice is maintained in OB45 (update 000012)
(2) CHECK against OLDEST OPEN ITEM with reaction C & TICK in BLOCK
(do not maintain any value in DAYS OLDEST ITEM, but maintain the payment terms in the Customer master)
for example, block as per payments days,say if payment terms is 30 days and within 30 days customer has not made payment against invoice so sales order will be blocked.
In both the cases ( credit limit and credit period,the sale orders blocked , can be released by VKM3.
Regards,
Hegal

Credit Management with Letter of Credit.

Hi Gurus,
We need to consider the "Letter of Credit" amout in credit management.
ie. if there is LC created on customer worth Rs. 5lacs, system should not block the sales order unless 5 lacs is consumed.
Pls suggest any workarounds.
Reg.
Amol

Dear Amol Tamhane,
Have not worked on 'letter of credit'.
But if there is any accounting document which gets created due to letter of credit, then you can use the exit for credit management in SALES ORDER LEVEL and write the code to BLOCK THE SALES ORDER ONLY IF
(CREDIT LIMIT + LETTER OF CREDIT AMOUNT ) - (PREVIOUS EXPOSURE + SALES ORDER VALUE ) < 0
You can check BSEG, if accounting document gets created for 'letter of credit' or you can check any tables related to letter of credit based on customer code.
Thanks & Regards,
Hegal K Charles

Credit Management- ,BP with customer

Hello All,
I'm new to Credit management, My concern is how to link my customer account with my BP.
Say example my BP- 1000 is extended for Credit management and have a AR invoice for ABCD customer, How shall i create link between both?
Appreciate your help.
PS: I'm aware of CVI
Regards,
Jain

Dear Jain,
Your idea seems to link SD-customer with BP which has different number from SD-customer .
eg. SD-customer ABCD ==> BP 1000
When FSCM selects BP for credit management, it search for BP which has same number with SD-customer.
eg. SD-customer 1000 ==> BP 1000
This standard logic happens in BAdi definition of 'BADI_SD_CM'.
I guessed that you already activated this BADI
(IMG name >> BAdI: Connection of SD to SAP Credit Management)
My opinion for your requirement is as follows;
If you want to put your own business process into this standard logic,
kindly go to your own BAdi implementation and enhance it
(eg. method: FSCM_GET_ACCOUNT_KEY, FSCM_GET_MASTER_DATA)
More efficient enhancement approach would be welcomed.
Best regards,
Ted

Dynamic Credit Management - issue with released documents

Hi,
I have a problem concerning automatic credit check.
In my project we activated the option "Dynamic Credit Check" to check the customer credit exposure and also the open order value.
Everything is working perfect, and the system blocks when the conditions are not meet.
The problem is:
When the SO is blocked, and after beeing released, everytime we save that SO it triggers the credit check and put it blocked again.
Even with a simple output msg creation, or a change in a text field, triggers the credit check, and everytime we must to release the SO again.
In customizing I see that there are the parameter "Number of Days" in tab "Released Docs are Still Unchecked", however it seems that parameter has no any effect with "Dynamic Check" option.
Do you know if there is some way to avoid to do SO release again and again (after release first time)?
Many thanks,
André

Dear Andre,
this is the standard SAP behavior, I mean when ever you are changing any thing in the sales order after releasing the Credit block which may again affect the credit, it will go into the credit Block again.....
And in your case also it might be the problem. So after releasing when you are saving the sales order, again Dynamic credit check is occurring and putting Sales order into block.
If you dont want this, then follow these
1. Go to VOFM :
2, Click on requirement --> credit check...
3. Write a suitable routine with the help of ABAPer for bypassing check on the things like, adding text, some small modification etc, but not for Quantity and Value
4. Assign this routine in OVA8 for credit group + risk category + credit group combination.
I hope it will help.
Thanks,
Raja

How to deal with Letter of Credit in Oracle Payables ??

In case of letter of credit, an 100% advance payment is done to bank, Bank charges its commission,
The letter of credit is for goods imported which is part of inventory. As standard practices of finance, exchange gain/loss and expenses incurred to bring the inventory to its present location and conditions should form part of inventory cost.
This cost are not known at the time of PO, so only purchase price is ascertain.
How to track custom duty paid, insurance, freight, and cargo handling expenses incurred on material.
All this cost should be charged to item and according unit cost should be adjusted.

Well, when are these other costs known? Perhaps you do not know them until you get the invoice from the supplier? Are you then doing match to invoice (either match to PO or match to receipt?)? What version of EBS are you on? My initial off the top of my head though is that when you match the invoice to receipt, the quantity amount should match, but the cost amount would be higher, by the amount of these extra costs. So you would have to be sure you don't have any match tolerance that would prevent such a match. That would get the entire cost charged to inventory, and the unit cost on that invoice is Cost Amount / Quantity. Without knowing anything about your inventory setup, not sure how that would impact you.
Of course, if any of my assumptions are wrong, then my thinking will be wrong. Thus would be helpful to supply additional information about your situation.
John Dickey

This SQL statement always in Top Activity, with PX Deq Credit: send blkd

Hi gurus,
The following SQL statement is always among the Top Activity. I can see the details in Enerprise manager that it suffers from PX Deq Credit: send blkd
This is the statement:
SELECT S.Product, S.WH_CODE, S.RACK, S.BATCH, S.EXP_DATE, FLOOR(Qty_Beg) QtyBeg_B,
        ROUND(f_convert_qty(S.PRODUCT, Qty_Beg-FLOOR(Qty_Beg), P.UOM_K ), 0) QtyBeg_K,
        FLOOR(Qty_In) QtyIn_B, ROUND(f_convert_qty(S.PRODUCT, Qty_In-FLOOR(Qty_In), P.UOM_K), 0) QtyIn_K,
        FLOOR(Qty_Out) QtyOut_B, ROUND(f_convert_qty(S.PRODUCT, Qty_Out-FLOOR(Qty_Out), P.UOM_K ), 0) QtyOut_K,
        FLOOR(Qty_Adj) QtyAdj_B, ROUND(f_convert_qty(S.PRODUCT, Qty_Adj-FLOOR(Qty_Adj), P.UOM_K ), 0) QtyAdj_K,
        FLOOR(Qty_End) QtyEnd_B, ROUND(f_convert_qty(S.PRODUCT, Qty_End-FLOOR(Qty_End), P.UOM_K ), 0) QtyEnd_K,
        S.LOC_CODE
        FROM V_STOCK_DETAIL S
        JOIN PRODUCTS P ON P.PRODUCT = S.PRODUCT
        WHERE S.Product = :pProduct AND S.WH_CODE = :pWhCode AND S.LOC_CODE = :pLocCode;The statement is invoked by our front end (web based app) for a browse table displayed on a web page. The result can be 10 to 8000. It is used to display the current stock availability for a particular product in a particular warehouse. The stock availability it self is kept in a View : V_Stock_Detail
These are the parameters relevant to the optimizer:
SQL> show parameter user_dump_dest
user_dump_dest                       string   /u01/app/oracle/admin/ITTDB/udump
SQL> show parameter optimizer
_optimizer_cost_based_transformation string   OFF
optimizer_dynamic_sampling           integer 2
optimizer_features_enable            string   10.2.0.3
optimizer_index_caching              integer 0
optimizer_index_cost_adj             integer 100
optimizer_mode                       string   ALL_ROWS
optimizer_secure_view_merging        boolean TRUE
SQL> show parameter db_file_multi
db_file_multiblock_read_count        integer 16
SQL> show parameter db_block_size column sname format a20 column pname format a20
db_block_size                        integer 8192Here is the output of EXPLAIN PLAN:
SQL> explain plan for
SELECT S.Product, S.WH_CODE, S.RACK, S.BATCH, S.EXP_DATE, FLOOR(Qty_Beg) QtyBeg_B,
    ROUND(f_convert_qty(S.PRODUCT, Qty_Beg-FLOOR(Qty_Beg), P.UOM_K ), 0) QtyBeg_K,
    FLOOR(Qty_In) QtyIn_B, ROUND(f_convert_qty(S.PRODUCT, Qty_In-FLOOR(Qty_In), P.UOM_K), 0) QtyIn_K,
    FLOOR(Qty_Out) QtyOut_B, ROUND(f_convert_qty(S.PRODUCT, Qty_Out-FLOOR(Qty_Out), P.UOM_K ), 0) QtyOut_K,
    FLOOR(Qty_Adj) QtyAdj_B, ROUND(f_convert_qty(S.PRODUCT, Qty_Adj-FLOOR(Qty_Adj), P.UOM_K ), 0) QtyAdj_K,
    FLOOR(Qty_End) QtyEnd_B, ROUND(f_convert_qty(S.PRODUCT, Qty_End-FLOOR(Qty_End), P.UOM_K ), 0) QtyEnd_K,
    S.LOC_CODE
    FROM V_STOCK_DETAIL S
    JOIN PRODUCTS P ON P.PRODUCT = S.PRODUCT
    WHERE S.Product = :pProduct AND S.WH_CODE = :pWhCode AND S.LOC_CODE = :pLocCode
Explain complete.
Elapsed: 00:00:00:31
SQL> select * from table(dbms_xplan.display)
PLAN_TABLE_OUTPUT
Plan hash value: 3252950027
| Id | Operation                               | Name                | Rows | Bytes | Cost (%CPU)| Time     |    TQ |IN-OUT| PQ
Distrib |
|   0 | SELECT STATEMENT                        |                     |     1 |   169 |     6 (17)| 00:00:01 |        |      |
         |
|   1 | PX COORDINATOR                         |                     |       |       |            |          |        |      |
         |
|   2 |   PX SEND QC (RANDOM)                   | :TQ10003            |     1 |   169 |     6 (17)| 00:00:01 | Q1,03 | P->S | QC
(RAND) |
|   3 |    HASH GROUP BY                        |                     |     1 |   169 |     6 (17)| 00:00:01 | Q1,03 | PCWP |
         |
|   4 |     PX RECEIVE                          |                     |     1 |   169 |     6 (17)| 00:00:01 | Q1,03 | PCWP |
         |
|   5 |      PX SEND HASH                       | :TQ10002            |     1 |   169 |     6 (17)| 00:00:01 | Q1,02 | P->P | HA
SH       |
|   6 |       HASH GROUP BY                     |                     |     1 |   169 |     6 (17)| 00:00:01 | Q1,02 | PCWP |
         |
|   7 |        NESTED LOOPS OUTER               |                     |     1 |   169 |     5   (0)| 00:00:01 | Q1,02 | PCWP |
         |
|   8 |         MERGE JOIN CARTESIAN            |                     |     1 |   119 |     4   (0)| 00:00:01 | Q1,02 | PCWP |
         |
|   9 |          SORT JOIN                      |                     |       |       |            |          | Q1,02 | PCWP |
         |
| 10 |           NESTED LOOPS                  |                     |     1 |    49 |     4   (0)| 00:00:01 | Q1,02 | PCWP |
         |
| 11 |            BUFFER SORT                  |                     |       |       |            |          | Q1,02 | PCWC |
         |
| 12 |             PX RECEIVE                  |                     |       |       |            |          | Q1,02 | PCWP |
         |
| 13 |              PX SEND BROADCAST          | :TQ10000            |       |       |            |          |        | S->P | BR
OADCAST |
|* 14 |               INDEX RANGE SCAN          | PRODUCTS_IDX2       |     1 |    25 |     2   (0)| 00:00:01 |        |      |
         |
| 15 |            PX BLOCK ITERATOR            |                     |     1 |    24 |     2   (0)| 00:00:01 | Q1,02 | PCWC |
         |
|* 16 |             MAT_VIEW ACCESS FULL        | MV_CONVERT_UOM      |     1 |    24 |     2   (0)| 00:00:01 | Q1,02 | PCWP |
         |
| 17 |          BUFFER SORT                    |                     |     1 |    70 |     2   (0)| 00:00:01 | Q1,02 | PCWP |
         |
| 18 |           BUFFER SORT                   |                     |       |       |            |          | Q1,02 | PCWC |
         |
| 19 |            PX RECEIVE                   |                     |     1 |    70 |     4   (0)| 00:00:01 | Q1,02 | PCWP |
         |
| 20 |             PX SEND BROADCAST           | :TQ10001            |     1 |    70 |     4   (0)| 00:00:01 |        | S->P | BR
OADCAST |
|* 21 |              TABLE ACCESS BY INDEX ROWID| STOCK               |     1 |    70 |     4   (0)| 00:00:01 |        |      |
         |
|* 22 |               INDEX RANGE SCAN          | STOCK_PK            |     1 |       |     2   (0)| 00:00:01 |        |      |
         |
|* 23 |         TABLE ACCESS BY INDEX ROWID     | MV_TRANS_STOCK      |     1 |    50 |     3   (0)| 00:00:01 | Q1,02 | PCWP |
         |
|* 24 |          INDEX RANGE SCAN               | MV_TRANS_STOCK_IDX1 |     1 |       |     2   (0)| 00:00:01 | Q1,02 | PCWP |
         |
Predicate Information (identified by operation id):
14 - access("P"."PRODUCT"=:PPRODUCT)
16 - filter("CON"."PRODUCT"=:PPRODUCT)
21 - filter("STOCK"."LOC_CODE"=:PLOCCODE)
22 - access("STOCK"."PRODUCT"=:PPRODUCT AND "STOCK"."WH_CODE"=:PWHCODE)
23 - filter("STS"(+)='N')
24 - access("PRODUCT"(+)=:PPRODUCT AND "WH_CODE"(+)=:PWHCODE AND "LOC_CODE"(+)=:PLOCCODE AND "RACK"(+)="STOCK"."RACK" AND
              "BATCH"(+)="STOCK"."BATCH" AND "EXP_DATE"(+)="STOCK"."EXP_DATE")
42 rows selected.
Elapsed: 00:00:00:06Here is the output of SQL*Plus AUTOTRACE including the TIMING information:
SQL> SELECT S.Product, S.WH_CODE, S.RACK, S.BATCH, S.EXP_DATE, FLOOR(Qty_Beg) QtyBeg_B,
    ROUND(f_convert_qty(S.PRODUCT, Qty_Beg-FLOOR(Qty_Beg), P.UOM_K ), 0) QtyBeg_K,
    FLOOR(Qty_In) QtyIn_B, ROUND(f_convert_qty(S.PRODUCT, Qty_In-FLOOR(Qty_In), P.UOM_K), 0) QtyIn_K,
    FLOOR(Qty_Out) QtyOut_B, ROUND(f_convert_qty(S.PRODUCT, Qty_Out-FLOOR(Qty_Out), P.UOM_K ), 0) QtyOut_K,
    FLOOR(Qty_Adj) QtyAdj_B, ROUND(f_convert_qty(S.PRODUCT, Qty_Adj-FLOOR(Qty_Adj), P.UOM_K ), 0) QtyAdj_K,
    FLOOR(Qty_End) QtyEnd_B, ROUND(f_convert_qty(S.PRODUCT, Qty_End-FLOOR(Qty_End), P.UOM_K ), 0) QtyEnd_K,
    S.LOC_CODE
    FROM V_STOCK_DETAIL S
    JOIN PRODUCTS P ON P.PRODUCT = S.PRODUCT
    WHERE S.Product = :pProduct AND S.WH_CODE = :pWhCode AND S.LOC_CODE = :pLocCode
Execution Plan
   0      SELECT STATEMENT Optimizer Mode=ALL_ROWS   1   169   6
   1    0   PX COORDINATOR
   2    1     PX SEND QC (RANDOM) SYS.:TQ10003 1   169   6   :Q1003 P->S   QC (RANDOM)
   3    2       HASH GROUP BY   1   169   6   :Q1003 PCWP
   4    3         PX RECEIVE   1   169   6   :Q1003 PCWP
   5    4           PX SEND HASH SYS.:TQ10002 1   169   6   :Q1002 P->P   HASH
   6    5             HASH GROUP BY   1   169   6   :Q1002 PCWP
   7    6               NESTED LOOPS OUTER   1   169   5   :Q1002 PCWP
   8    7                 MERGE JOIN CARTESIAN   1   119   4   :Q1002 PCWP
   9    8                   SORT JOIN          :Q1002 PCWP
10    9                     NESTED LOOPS   1   49   4   :Q1002 PCWP
11   10                       BUFFER SORT          :Q1002 PCWC
12   11                         PX RECEIVE          :Q1002 PCWP
13   12                           PX SEND BROADCAST SYS.:TQ10000           S->P   BROADCAST
14   13                             INDEX RANGE SCAN ITT_NEW.PRODUCTS_IDX2 1   25   2
15   10                       PX BLOCK ITERATOR   1   24   2   :Q1002 PCWC
16   15                         MAT_VIEW ACCESS FULL ITT_NEW.MV_CONVERT_UOM 1   24   2   :Q1002 PCWP
17    8                   BUFFER SORT   1   70   2   :Q1002 PCWP
18   17                     BUFFER SORT          :Q1002 PCWC
19   18                       PX RECEIVE   1   70   4   :Q1002 PCWP
20   19                         PX SEND BROADCAST SYS.:TQ10001 1   70   4      S->P   BROADCAST
21   20                           TABLE ACCESS BY INDEX ROWID ITT_NEW.STOCK 1   70   4
22   21                             INDEX RANGE SCAN ITT_NEW.STOCK_PK 1     2
23    7                 TABLE ACCESS BY INDEX ROWID ITT_NEW.MV_TRANS_STOCK 1   50   3   :Q1002 PCWP
24   23                   INDEX RANGE SCAN ITT_NEW.MV_TRANS_STOCK_IDX1 1     2   :Q1002 PCWP
Statistics
        570 recursive calls
          0 physical write total IO requests
          0 physical write total multi block requests
          0 physical write total bytes
          0 physical writes direct temporary tablespace
          0 java session heap live size max
          0 java session heap object count
          0 java session heap object count max
          0 java session heap collected count
          0 java session heap collected bytes
         83 rows processed
Elapsed: 00:00:03:24
SQL> disconnect
Commit complete
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining optionsThe TKPROF output for this statement looks like the following:
TKPROF: Release 10.2.0.3.0 - Production on Thu Apr 23 12:39:29 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Trace file: ittdb_ora_9566_mytrace1.trc
Sort options: default
count    = number of times OCI procedure was executed
cpu      = cpu time in seconds executing
elapsed = elapsed time in seconds executing
disk     = number of physical reads of buffers from disk
query    = number of buffers gotten for consistent read
current = number of buffers gotten in current mode (usually for update)
rows     = number of rows processed by the fetch or execute call
SELECT S.Product, S.WH_CODE, S.RACK, S.BATCH, S.EXP_DATE, FLOOR(Qty_Beg) QtyBeg_B,
    ROUND(f_convert_qty(S.PRODUCT, Qty_Beg-FLOOR(Qty_Beg), P.UOM_K ), 0) QtyBeg_K,
    FLOOR(Qty_In) QtyIn_B, ROUND(f_convert_qty(S.PRODUCT, Qty_In-FLOOR(Qty_In), P.UOM_K), 0) QtyIn_K,
    FLOOR(Qty_Out) QtyOut_B, ROUND(f_convert_qty(S.PRODUCT, Qty_Out-FLOOR(Qty_Out), P.UOM_K ), 0) QtyOut_K,
    FLOOR(Qty_Adj) QtyAdj_B, ROUND(f_convert_qty(S.PRODUCT, Qty_Adj-FLOOR(Qty_Adj), P.UOM_K ), 0) QtyAdj_K,
    FLOOR(Qty_End) QtyEnd_B, ROUND(f_convert_qty(S.PRODUCT, Qty_End-FLOOR(Qty_End), P.UOM_K ), 0) QtyEnd_K,
    S.LOC_CODE
    FROM V_STOCK_DETAIL S
    JOIN PRODUCTS P ON P.PRODUCT = S.PRODUCT
    WHERE S.Product = :pProduct AND S.WH_CODE = :pWhCode AND S.LOC_CODE = :pLocCode
call     count       cpu    elapsed       disk      query    current        rows
Parse        1      0.00       0.00          0          0          0           0
Execute      1      0.04       0.12          0         10          4           0
Fetch       43      0.05       2.02          0         73          0          83
total       45      0.10       2.15          0         83          4          83
Misses in library cache during parse: 1
Misses in library cache during execute: 1
Optimizer mode: ALL_ROWS
Parsing user id: 164
Rows     Row Source Operation
     83 PX COORDINATOR (cr=83 pr=0 pw=0 time=2086576 us)
      0   PX SEND QC (RANDOM) :TQ10003 (cr=0 pr=0 pw=0 time=0 us)
      0    HASH GROUP BY (cr=0 pr=0 pw=0 time=0 us)
      0     PX RECEIVE (cr=0 pr=0 pw=0 time=0 us)
      0      PX SEND HASH :TQ10002 (cr=0 pr=0 pw=0 time=0 us)
      0       HASH GROUP BY (cr=0 pr=0 pw=0 time=0 us)
      0        NESTED LOOPS OUTER (cr=0 pr=0 pw=0 time=0 us)
      0         MERGE JOIN CARTESIAN (cr=0 pr=0 pw=0 time=0 us)
      0          SORT JOIN (cr=0 pr=0 pw=0 time=0 us)
      0           NESTED LOOPS (cr=0 pr=0 pw=0 time=0 us)
      0            BUFFER SORT (cr=0 pr=0 pw=0 time=0 us)
      0             PX RECEIVE (cr=0 pr=0 pw=0 time=0 us)
      0              PX SEND BROADCAST :TQ10000 (cr=0 pr=0 pw=0 time=0 us)
      1               INDEX RANGE SCAN PRODUCTS_IDX2 (cr=2 pr=0 pw=0 time=62 us)(object id 135097)
      0            PX BLOCK ITERATOR (cr=0 pr=0 pw=0 time=0 us)
      0             MAT_VIEW ACCESS FULL MV_CONVERT_UOM (cr=0 pr=0 pw=0 time=0 us)
      0          BUFFER SORT (cr=0 pr=0 pw=0 time=0 us)
      0           BUFFER SORT (cr=0 pr=0 pw=0 time=0 us)
      0            PX RECEIVE (cr=0 pr=0 pw=0 time=0 us)
      0             PX SEND BROADCAST :TQ10001 (cr=0 pr=0 pw=0 time=0 us)
     83              TABLE ACCESS BY INDEX ROWID STOCK (cr=78 pr=0 pw=0 time=1635 us)
     83               INDEX RANGE SCAN STOCK_PK (cr=4 pr=0 pw=0 time=458 us)(object id 135252)
      0         TABLE ACCESS BY INDEX ROWID MV_TRANS_STOCK (cr=0 pr=0 pw=0 time=0 us)
      0          INDEX RANGE SCAN MV_TRANS_STOCK_IDX1 (cr=0 pr=0 pw=0 time=0 us)(object id 143537)
Elapsed times include waiting on following events:
Event waited on                             Times   Max. Wait Total Waited
----------------------------------------   Waited ---------- ------------
PX Deq: Join ACK                               17        0.00          0.00
PX qref latch                                   2        0.00          0.00
PX Deq Credit: send blkd                       72        1.95          2.00
PX Deq: Parse Reply                            26        0.01          0.01
SQL*Net message to client                      43        0.00          0.00
PX Deq: Execute Reply                          19        0.00          0.01
SQL*Net message from client                    43        0.00          0.04
PX Deq: Signal ACK                             12        0.00          0.00
enq: PS - contention                            1        0.00          0.00
********************************************************************************The DBMS_XPLAN.DISPLAY_CURSOR output:
SQL> select * from table(dbms_xplan.display_cursor(null, null, 'ALLSTATS LAST'))
PLAN_TABLE_OUTPUT
SQL_ID 402b8st7vt6ku, child number 2
SELECT /*+ gather_plan_statistics */          S.Product, S.WH_CODE, S.RACK, S.BATCH, S.EXP_DATE, FLOOR(Qty_Beg) QtyBeg_B,
ROUND(f_convert_qty(S.PRODUCT, Qty_Beg-FLOOR(Qty_Beg), P.UOM_K ), 0) QtyBeg_K,      FLOOR(Qty_In) QtyIn_B, ROUND(f_convert_qty(S.P
RODUCT,
Qty_In-FLOOR(Qty_In), P.UOM_K), 0) QtyIn_K,      FLOOR(Qty_Out) QtyOut_B, ROUND(f_convert_qty(S.PRODUCT, Qty_Out-FLOOR(Qty_Out), P
.UOM_K ),
0) QtyOut_K,      FLOOR(Qty_Adj) QtyAdj_B, ROUND(f_convert_qty(S.PRODUCT, Qty_Adj-FLOOR(Qty_Adj), P.UOM_K ), 0) QtyAdj_K,
FLOOR(Qty_End) QtyEnd_B, ROUND(f_convert_qty(S.PRODUCT, Qty_End-FLOOR(Qty_End), P.UOM_K ), 0) QtyEnd_K,      S.LOC_CODE      FROM
V_STOCK_DETAIL S      JOIN PRODUCTS P ON P.PRODUCT = S.PRODUCT      WHERE S.Product = :pProduct AND S.WH_CODE = :pWhCode AND S.LOC
_CODE =
:pLocCode
Plan hash value: 3252950027
| Id | Operation                               | Name                | Starts | E-Rows | A-Rows |   A-Time   | Buffers | OMem |
1Mem | Used-Mem |
|   1 | PX COORDINATOR                         |                     |      1 |        |     83 |00:00:02.25 |      83 |       |
      |          |
|   2 |   PX SEND QC (RANDOM)                   | :TQ10003            |      0 |     21 |      0 |00:00:00.01 |       0 |       |
      |          |
|   3 |    HASH GROUP BY                        |                     |      0 |     21 |      0 |00:00:00.01 |       0 |       |
      |          |
|   4 |     PX RECEIVE                          |                     |      0 |     21 |      0 |00:00:00.01 |       0 |       |
      |          |
|   5 |      PX SEND HASH                       | :TQ10002            |      0 |     21 |      0 |00:00:00.01 |       0 |       |
      |          |
|   6 |       HASH GROUP BY                     |                     |      0 |     21 |      0 |00:00:00.01 |       0 |       |
      |          |
|   7 |        NESTED LOOPS OUTER               |                     |      0 |     21 |      0 |00:00:00.01 |       0 |       |
      |          |
|   8 |         MERGE JOIN CARTESIAN            |                     |      0 |     21 |      0 |00:00:00.01 |       0 |       |
      |          |
|   9 |          SORT JOIN                      |                     |      0 |        |      0 |00:00:00.01 |       0 | 73728 |
73728 |          |
| 10 |           NESTED LOOPS                  |                     |      0 |      1 |      0 |00:00:00.01 |       0 |       |
      |          |
| 11 |            BUFFER SORT                  |                     |      0 |        |      0 |00:00:00.01 |       0 | 73728 |
73728 |          |
| 12 |             PX RECEIVE                  |                     |      0 |        |      0 |00:00:00.01 |       0 |       |
      |          |
| 13 |              PX SEND BROADCAST          | :TQ10000            |      0 |        |      0 |00:00:00.01 |       0 |       |
      |          |
|* 14 |               INDEX RANGE SCAN          | PRODUCTS_IDX2       |      1 |      1 |      1 |00:00:00.01 |       2 |       |
      |          |
| 15 |            PX BLOCK ITERATOR            |                     |      0 |      1 |      0 |00:00:00.01 |       0 |       |
      |          |
|* 16 |             MAT_VIEW ACCESS FULL        | MV_CONVERT_UOM      |      0 |      1 |      0 |00:00:00.01 |       0 |       |
      |          |
| 17 |          BUFFER SORT                    |                     |      0 |     21 |      0 |00:00:00.01 |       0 | 73728 |
73728 |          |
| 18 |           BUFFER SORT                   |                     |      0 |        |      0 |00:00:00.01 |       0 | 73728 |
73728 |          |
| 19 |            PX RECEIVE                   |                     |      0 |     21 |      0 |00:00:00.01 |       0 |       |
      |          |
| 20 |             PX SEND BROADCAST           | :TQ10001            |      0 |     21 |      0 |00:00:00.01 |       0 |       |
      |          |
|* 21 |              TABLE ACCESS BY INDEX ROWID| STOCK               |      1 |     21 |     83 |00:00:00.01 |      78 |       |
      |          |
|* 22 |               INDEX RANGE SCAN          | STOCK_PK            |      1 |     91 |     83 |00:00:00.01 |       4 |       |
      |          |
|* 23 |         TABLE ACCESS BY INDEX ROWID     | MV_TRANS_STOCK      |      0 |      1 |      0 |00:00:00.01 |       0 |       |
      |          |
|* 24 |          INDEX RANGE SCAN               | MV_TRANS_STOCK_IDX1 |      0 |      1 |      0 |00:00:00.01 |       0 |       |
      |          |
Predicate Information (identified by operation id):
14 - access("P"."PRODUCT"=:PPRODUCT)
16 - access(:Z>=:Z AND :Z<=:Z)
       filter("CON"."PRODUCT"=:PPRODUCT)
21 - filter("STOCK"."LOC_CODE"=:PLOCCODE)
22 - access("STOCK"."PRODUCT"=:PPRODUCT AND "STOCK"."WH_CODE"=:PWHCODE)
23 - filter("STS"='N')
24 - access("PRODUCT"=:PPRODUCT AND "WH_CODE"=:PWHCODE AND "LOC_CODE"=:PLOCCODE AND "RACK"="STOCK"."RACK" AND "BATCH"="STOCK"."B
ATCH" AND
              "EXP_DATE"="STOCK"."EXP_DATE")
53 rows selected.
Elapsed: 00:00:00:12I'm looking forward for suggestions how to improve the performance of this statement.
Thank you very much,
xtanto

xtanto wrote:
Hi sir,
How to prevent the query from doing parallel query ?
Because as you see actually I am not issuing any Parallel hints in the query.
Thank you,
xtantoKristanto,
there are a couple of points to consider:
1. Your SQL*Plus version seems to be outdated. Please use a SQL*Plus version that corresponds to your database version. E.g. the AUTOTRACE output is odd.
2. I would suggest to repeat your exercise using serial execution (the plan, the autotrace, the tracing). You can disable parallel queries by issuing this in your session:
ALTER SESSION DISABLE PARALLEL QUERY;
This way the output of the tools is much more meaningful, however you might get a different execution plan, therefore the results might not be representative for your parallel execution.
3. The function calls might pose a problem. If they are, one possible damage limitation has been provided by hoek. Even better would be then to replace the PL/SQL function with equivalent plain SQL. However since you say that it generates not too many rows it might not harm here too much. You can check the impact of the functions by running a similar query but omitting the function calls.
4. The parallel execution plan contains a MERGE JOIN CARTESIAN operation which could be an issue if the estimates of the optimizer are incorrect. If the serial execution still uses this operation the TKPROF and DBMS_XPLAN.DISPLAY_CURSOR output will reveal whether this is a problem or not.
5. The execution of the statement seems to take on 2-3 seconds in your tests. Is this in the right ballpark? If yes, why should this statement then be problematic? How often does it get executed?
6. The statement uses bind variables, so you might have executions that use different execution plans depending on the bind values passed when the statement got optimized. You can use DBMS_XPLAN.DISPLAY_CURSOR using NULL as "child_number" parameter or DBMS_XPLAN.DISPLAY_AWR (if you have a AWR license) to check if you have multiple execution plans for the statement. Please note that older versions might have already been aged out of the shared pool, so the AWR repository might be a more reliable source (but only if the statement has been sampled).
7. You have disabled cost based transformations: "_optimizer_cost_based_transformation" = OFF. Why?
Regards,
Randolf
Oracle related stuff blog:
http://oracle-randolf.blogspot.com/
SQLTools++ for Oracle (Open source Oracle GUI for Windows):
http://www.sqltools-plusplus.org:7676/
http://sourceforge.net/projects/sqlt-pp/

Letter of Credit functionality and Credit Management

Hi,
we want to use Letter of Credit functionality for exports.
Currently, we have an ERP system that contains the sales data. In a separate system we have the credit management functionality (Financial Supply Chain Mgt - FSCM).
When order is created, the credit limit is checked in the FSCM system (via PI messages).
Now, we want to link some of the Sales orders with Letter of Credit. I believe, this is standard functionality in GTS.
So when Sales Order is created a LOC should be connected to this.
Can the GTS be connected also to FSCM credit management, so credit limit is not affected?
Example:
Sales Order value: 1 Mio USD
10% down-payment > this would be in the credit exposure visible (net exposure).
90 % covered through LOC > credit exposure should showing this, or it shows order value and in a negative figure this amount deducted so no effect on exposure.
Down-payment has no relation to LOC. When money is received for this the net exposure of the sales order is 0.
partial invoice: 0.4 Mio USD > it should be possible to link this invoice to the LOC. The posting FI document should have some LOC information, so when payment comes in the amount in LOC is reduced as well as in credit management this open.
Final invoice 0.5 USD: as above, all values go out from exposure if there are any.
A second case would be guarantees, where there is no reduction of values. This would stay same.
Anyone who can advise a solution here?
Thanks + Regards
Hein

Letter Of Credit can be used as a standard solution of SAP GTS with ERP solution. Yes you can connect both SAP & no SAP systems with GTS, but plugins, PI etc needs to be built in. But it would not be real time like RFC works. There are some standard available which needs to be hard coded to meet specific requirements.
Connecting LOC to Sales Order, invoice etc, is manual, based on business specific parameters and it comes standard with SAP GTS. Maintaining Values & Quantity of LOC based on actual LOC from bank is also possible. The depreciation of values & quantities is also standard with in LOC in GTS.
You can also setup various communication methods for LOC.
I think when Invoice is raised and payment is received the LOC should be closed in the system. There can also be other scenarios where in system determines LOC based on predefined logics for determination strategy put in to the GTS system.
Cheers,
Abir

Credit Management with advance payment

Hi,
We have credit management scenario with advance payment.
In most cases the customer pays an advance. This advance may / may not be against a specific Sales order. At the time of checking the Credit limit, the system has to check the customer advance account as well.
We have 2 types of products u2013 standard (fast moving products) for which there is a min stock defined. There is also a non standard product for which there is no min stock defined.
When a customer places order for standard products & pays an advance against that, this advance may be used to deliver any product in any sales order for standard items. Hence for standard products advance is not linked to a sales order.
However, in case a client places an order for Non standard product & pays an advance against that order then that advance cannot be used to deliver a standard product.
This is to ensure that if advance is paid for non standard profiles, then advance paid against that should not be used to clear orders for standard products.
This can be administered correctly by locking an advance received to specific sales orders. This can be done at the time of receipt of advance & order confirmation.
If this is possible then please suggest step by step configuration.

Hi
If the credit limit is specific to only few customers who pays in advance then you can go with dynamic credit check.
Please go through this link which will help you for configuration
http://help.sap.com/saphelp_erp60_sp/helpdata/en/4d/4653b0cfd70692e10000000a42189b/frameset.htm
Regards
Srinath

Open Delivery value update error in credit management

Hi
We have credit management active at delivery level. The value of open deliveries is not getting updated correctly for items with material substitution (material determination). For all other items, its getting updated correctly.
E.g Let say the credit limit set in FD32 is 10000 and the credit limit used % is 98 and the credit exposure value is 9800.
Now when I create an order with qty 10 for mat A, it creates a sub item B due to material determination and the value of the item is Rs.1200. In our system, the sub item with TAPS item category is relevant for pricing.
Then I create a delivery in VL01N and save it.
Now if i check in FD33, the credit limit used should be 101% and the credit exposure value should be 11000, but its not updating the open delivery value correctly. Its not considering the value of the new delivery.
However, If I add a normal item (TAN) in the same sales order and create a delivery for that item and save it, its updating the credit exposure based on the value of the normal item in the delivery correctly.
How to make the system update the open delivery values correctly by taking the items with material determination also into account.??
Please advise if any specific settings need to be done.
Regards
Madhu

Hi,
the system updates open values for credit management. These are:
Open sales order credit value (S066-OEIKW)
Open delivery credit value (S067-OLIKW)
Open billing document credit value (S067-OFAKW)
The system updates the open values in standard SIS structures S066 and S067. Technically, the structures are transparent tables. You can display the contents using transaction SE16 or using table maintenance.
The S067-OLIKW will give the open delivery credit values credit.Check in you system whether this table is updated with the delivery values for the credit account(customer number)
RVKRED77 u2013 Reorganize SD credit data
When updating errors occur, it enables you to reorganize the open credit, delivery and billing document values.
If the table is not updated run this report in background.
Regards,
Saju.S

Down payments u2013 Credit Management, Sales Value FD32.

Hi,
We have a problem with the credit management in Down payments. The down payments requests are not decreasing the Sales Value of the client. I mean when I bill a down payment, the sales value of the client in transaction FD32 keep with the same value. I have to bill the next milestone where the down payment is cleared to decrease the sales value of the client.
Billing Plan
1º Down payment 200
2º Final Billing 1000
Bill the down payment. Sales Value FD32 = 1000. It should be 800?
Bill the Final Invoice. Sales Value FD32 = 0.
Are there any way in the customizing to modify this behavior?
Thank you in advance and best regards.

Hello Alberto,
As you mentioned down payment of 200 and final bill of 1000, generally down payment is received at the start of activity. If you have credit limit say 500 and you receive down payment of 200 then system store down payment in separate GL account and when you carry out business, system first consider consuming down payment and then credit limit. So down payment never consider as sales till it get cleared off as it is before start of business as extra security to manage risk
Same thing happen when you do business with letter of credit
Hope this will resolve your confusion
Regards,
Mukul

Customer complaint and credit management

Hi,
we have the following business case, credit management activated:
1. a customer has a complain about a delivery (e.g. poor quality/wrong material)
2. the corresponding invoice is shown as an open item in FBL5N
3. a credit note request is created for the sales order, but it can take weeks until it gets released. In the meantime the customer becomes overdue.
4. now the following happens: when the customer wants to place a new order he will be blocked by the credit management.
We first have to release him e.g. via VKM4. The same with deliveries.
Is there a possibility to mark the invoice in question as not relevant for the credit management?
My first idea was to change the credit note requests as relevant for the credit management (VOV8), but unfortunately those requests are not visible in FBL5N. Thus we would loose the overview of invoices in question.
Thanks for your answers...
Cheers,
Marc

hello, PP.
i don't have an answer yet. actually, i will add to your question.
a credit memo request is supposed to be not relevant for delivery. so why is this updating open delivery value? maybe it's SAP standard? maybe credit group 03 (delivery docs) was assigned to the credit memo request doc type? if so, why assign credit management to credit memo requests anyway?
regards.

Credit Management - Maximum time overdue limit for open item

Dear all,
I've this scenario to configure for automatic credit control. A customer is billed on Jan 22nd '10 and now the account receiveable shows an open item. This customer is allowed 52 calendar days to make payment for this invoice, hence no credit block yet. As such, the customer can still make orders.
In my existing configuration, I've already enable "static" credit check on "open orders" and "open deliveries". The static check is to check against the customer's credit limit.
So, if I were to add in the earlier mentioned overdue open items check, is it sufficient to just maintain the field "Days oldestItem" with "52" within the automatic credit control screen?
Thanks.
Steven

Hi
The sytstem will shows oldest open items depending on the payment terms from the invoice date.
Once it crosses the days of payment then it will show in oldest open items
if you want to extend some more days for that then you need to maintain the days in "Days oldestitem" the automatic credit control area
Prerequisites for credit management to work in Sales and Distribution:
1.Assign credit control area to company code
2.Maintain the credit limit in FD32 with details of risk category and the credit limit value
3.Do the settings in OVA8 -automatic credit control area with combination of Credit control area/Risk category /credit group.
4.Assign the credit groups to the sales and delivery document types.
5.Maintain the Subtotal 'A' in the pricing procedure against which value the sytem should check the credit limit.
If you have any further clarifications on above let me know
Regards
Damu

Credit management configuration in Third party sales

Dear All,
Please let me know , what are the configuration setting for Credit Management in Third Party Sales.
Regards
SKumar

Hi...
For Third Party, since there is no Delivery and PGI, the block can be at Billing.
however the total outstanding value from the customer at the time of billing along with the days as set in the credit limit shall be basis of blocking.
Config Steps:
u2022     Assigned the credit control area to the company code
Financial Accounting (New)  Accounts Receivable and Accounts Payable  Credit management  Credit Control Account  Assign Permitted Credit Control Area to Company Code
u2022     Assign Sale Document and Delivery Document, The credit limit check for the selected sales document type is set to automatic control.
Sales and Distribution  Basic Functions  Credit management / Risk management Credit Management Assign Sales Documents and Delivery Document  Credit limit check for order types
u2022     Assigning Risk Category to Credit Control Area
Financial Accounting (New)  Accounts Receivable and Account Payable  Credit management  Credit Control Account  Define Risk Categories
u2022     Defining Automatic Credit Control
Financial Supply Chain Management  Credit Management  Integration with Accounts Receivable Accounting and Sales and Distribution  Integration with Sales and Distribution Define Automatic Credit Control

Credit management activation with letter of credit

Similar Messages

Maybe you are looking for