Transactions FD32

Hi, what will happen with transaction FD32 if you change from an SD Credit management to FSCM Credit management?
Many thanks,
M.

Are there any transactions from SD credit management still in use once you implement FSCM Credit management?
Edited by: Mario Sousa on Feb 25, 2011 9:58 AM

Similar Messages

F4 Help for a standard field in transaction FD32

Hello Expert,
i need to create a list selection for the standard field "KNKK-DBPAY" in the transaction FD32, program "SAPMF02C" dynpro 1090, is it possible ? if yes can you show me how to do?
thank you in advance that will be very helpful.

Hello
Refer:
http://help.sap.com/saphelp_nw04/helpdata/en/e9/635fa6e01e11d195490000e82de14a/frameset.htm
Re: adding field to screens

Adding a field the transaction 'FD32'

Hi,
I want to add an custom field to the trasaction FD32.
I couldn't find any screen exit for that one.
Please help me if anybody is having an idea.
Regards
(YUGANDHAR)

Hi,
Try this Enhancement
RFDRRANZ User exits: Accounts Receivable Information System
BADI Available
FI_DUZI_ROUND_CML Rounding in Accordance with Contract Conditions
Check this thread:
Workflow for transaction FD32
workflow triggering using "Z" object's event
Regards,
Satish

Need BTE for the transactions FD32, XD05,FD05...

HELLO FRIENDS,
can any one tell me the BTE for the transactions FD32, XD05,FD05...?
thanks,
Romanch

Hi Romanch,
You can use the following BTE
00001321 - CUSTOMER MASTER DATA: Save with Data Transfer
Also you can check from FIBF Transaction -> Environment -> Infosystem(P/S or Processes) to find the BTE's related to application component.
Hope this helps.
Thanks
Lakshman
Edited by: Lakshman Tandra on Jan 25, 2008 12:47 PM

Workflow for transaction FD32

Hello,
      I need to know, if there is a workflow for FD32 transaction, i searched by events and i didn´t found nothing, I found only a BO BUS1010, but this the object there isn´t a event create, the program relating doesn´t have a BADI or a User-Exit.
      Is there another way to make a workflow for this transaction?
Thanks,
Roberto

Hi Aran,
     Create an Subtype for that bus object(BUS1010). Create your own Event. Link it to the Workflow Using Transaction SWE2 and SWEC(Change Documents). Delegate your Business Object to the Standard Bussiness Object. Use the Standard Business Object to trigger the Workflow. now in this Business Object U'll find the Event you have created.
     Hope this might Help you.
Cheers,
Prashanth

Post Upgrade error in Transaction FD32

Dear All,
I am getting an error in FD32 when opening details for a customer. The error message is:
10005000 - is my customer number.
XXX - is my Credit Control area.
System error: Error in routine KNKK_LESEN 10005000 XXXX
Message no. F4308
Diagnosis
An internal error has occurred.
System Response
Processing cannot be continued.
Procedure
Contact SAP to clarify whether the error can be corrected by a program adjustment or by changes in the parameters.
In order to clarify the error situation, specify the routine KNKK_LESEN in which the error occurred, as well as any other parameters (if specified in the message) which could refer to a key which does not exist.
Let me know if you have seen this, and whats the possible solution. Thanks.
Vivek
Edited by: Vivek Sahni on Sep 9, 2011 2:27 PM

Hello
You can refer SAP Note 1599993 - RFDKLI40: System error F4 308 on returning to main list.
This has a valid since 01.09.2011 and says it is Program error.
Thanks & Regards
JP

Doubt in fd32

Hi Abpers,
i have doubt in transaction fd32. in that tr.code once after giving customer and credit control area and selecting status check box of credit control area data .press enter then the field
*credit limit used *
u can see my user requirement is by that transaction he want to check the blocked customers who crossed 100 % credit limit used.
that i want to list and show to him .
i want to know the field name and where this corresponding data is stored.

Hi,
The Credit limit details can be found in Table KNKK.
Field KLIMK customer credit limit value and field CRBLB corresponds to whether the customer is blocked in that credit control area.
Hope your problem is solved.
Regards,
Babul.

Performance credit master data (FD32)--SAP Note 705317

Hi,
When running the FD32 tranasaction,I am changing the credit account and saving the transaction...it is taking quite a long time and going for dump....TIME_OUT error.
The appropriate notes for this problem are 705317 and 9937.
I shall give the details details of the note.
SymptomLong runtimes occur for the reorganization of credit data in SD documents.
This reorganization can occur in two situation:
- You start report RFDKLI20.
- You create or change credit master data in Transaction FD32.
Reason and PrerequisitesIn the credit management, you change assignments in Customizing or create or change
credit master data. The transfer of the changed settings into existing SD documents
requires a reorganization of these documents.
The reorganization is triggered from Transaction FD32 or using report RFDKLI20. Since
the relevant partner function in the credit management is the payer, all open sales
documents for a payer are selectedfor the reorganization.
The selection is performed within function module SD_CREDIT_RECREATE, which is called
from both Transaction FD32 and report RFDKLI20.
The documents are selected according to one of the two following options:1. Partner index VAKPA
The relevant documents are selected via partner index VAKPA. In index table VAKPA,
the system updates all SD documents for a customer number in dependency on the
partner function. All documents for a payer can be determined using index table
VAKPA.
CAUTION: Partner index VAKPA is only updated if the corresponding partner
functions and transactions are activated in Customizing table TINPA. Table TINPA
does not provide any update for the payer partnerfunction in the standard system!
2. Document table VBPA
If the update for the payer is not active in table TINPA, the relevant documents
are selected via application table VBPA. Table VBPA contains the used partners
(customer numbers) for SD documents.
The access to table VBPA with the customer number of the payer requires a long
SAP Note Nr. 705317 07.02.2008 Page 1
runtime because the customer number is not a key field in table VBPA. It might
result in a TIME_OUT.
Solution
Due to the technical conditions described above, there are two possible solutions for
runtime problems in Transaction FD32 or with report RFDKLI20:
1. Activate the update of index table VAKPA for the payer partner function:
Activate the update of index table VAKPA for the payer partner function by
creating an entry with transaction = 0, partner function = RG in table TINPA. You
can use Transaction SM31 for that.
Subsequently, a reorganization of index table VAKPA is absolutely required!! You
can execute the reorganization with report RVV05IVB. Note that all existing SD
documents thus also those ones already closed are indexed again by this report.
Depending on the number of your documents in the system, this can result in a
runtime which is correspondingly long. Therefore test this beforehand in a copy of
your production system!
2. Create a database secondary index for table VBPA:
If a reorganization of index table VAKPA is not possible or not wanted, you can
optimize the access via document table VBPA. For that, create a database secondary
index for table VBPA.
We cannot provide a general recommendation on how you have to define the secondary
index in detail. This basically depends on your dataset.
Use the SQL trace with Transaction ST05 in order to analyze the access onto table
VBPA within function module SD_CREDIT_RECREATE. Then define a suitable database
secondary index for table VBPA according to your analysis results.
For example, you could create the secondary index for VBPA fields KUNNR and PARVW.
Test the new secondary index by creating an SQL trace with Transaction ST05 again
in order to check the effectiveness of the database access and the runtime.
Also take the related notes into account.
Use Note 99937 to avoid the automatic reorganization - and thus runtime problems - in
Transaction FD32. Note that this does not solve the runtime problem during the
reorganization in general, but shifts it to RFDKLI20 which you can schedule as a job.
Thus, you are not disturbed by the runtime problem.
Please can anyone help me as to in which table and what fields i need to take to create secondary index.Thank you,
madhu.

Hi
Instead of creating Indexxes u contact basis to increase the the time limit for the execution
Regards
Shiva

Skip first screen when calling transaction via BDC

I need to use BDC to call transaction FD32 and suppress the first screen. Do I need to set BDC_OKCODE? However, when I set BDC_OKCODE to '/00', this error occured, "System error: Error in routine DYNPRO_ERSTES_BILD".
Here is my code:
CLEAR ls_bdcdata.
ls_bdcdata-program = 'SAPMF02C'.
ls_bdcdata-dynpro = '0100'.
ls_bdcdata-dynbegin = 'X'.
APPEND ls_bdcdata TO lt_bdcdata.
CLEAR ls_bdcdata.
ls_bdcdata-fnam = 'RF02L-KUNNR'.
ls_bdcdata-fval = gs_data-kunnr.
APPEND ls_bdcdata TO lt_bdcdata.
CLEAR ls_bdcdata.
ls_bdcdata-fnam = 'RF02L-KKBER'.
ls_bdcdata-fval = p_kkber.
APPEND ls_bdcdata TO lt_bdcdata.
CLEAR ls_bdcdata.
ls_bdcdata-fnam = 'RF02L-D0105'.
ls_bdcdata-fval = 'X'.
APPEND ls_bdcdata TO lt_bdcdata.
CLEAR ls_bdcdata.
ls_bdcdata-fnam = 'BDC_OKCODE'.
ls_bdcdata-fval = '/00'.
APPEND ls_bdcdata TO lt_bdcdata.
opt-dismode = 'E'.
opt-defsize = 'X'.
CALL TRANSACTION 'FD32' USING lt_bdcdata OPTIONS FROM opt.
Any suggestions?

Hi,
Try this..This is working fine for me..
CLEAR ls_bdcdata.
ls_bdcdata-program = 'SAPMF02C'.
ls_bdcdata-dynpro = '0100'.
ls_bdcdata-dynbegin = 'X'.
APPEND ls_bdcdata TO lt_bdcdata.
CLEAR ls_bdcdata.
ls_bdcdata-fnam = 'BDC_CURSOR'.
ls_bdcdata-fval = 'RF02L-D0110'.
APPEND ls_bdcdata TO lt_bdcdata.
CLEAR ls_bdcdata.
ls_bdcdata-fnam = 'BDC_OKCODE'.
ls_bdcdata-fval = '/00'.
APPEND ls_bdcdata TO lt_bdcdata.
CLEAR ls_bdcdata.
ls_bdcdata-fnam = 'RF02L-KUNNR'.
ls_bdcdata-fval = gs_data-kunnr.
APPEND ls_bdcdata TO lt_bdcdata.
CLEAR ls_bdcdata.
ls_bdcdata-fnam = 'RF02L-KKBER'.
ls_bdcdata-fval = p_kkber.
APPEND ls_bdcdata TO lt_bdcdata.
CLEAR ls_bdcdata.
ls_bdcdata-fnam = 'RF02L-D0105'.
ls_bdcdata-fval = 'X'.
APPEND ls_bdcdata TO lt_bdcdata.
CLEAR ls_bdcdata.
ls_bdcdata-fnam = 'RF02L-D0110'.
ls_bdcdata-fval = 'X'.
APPEND ls_bdcdata TO lt_bdcdata.
CLEAR ls_bdcdata.
ls_bdcdata-fnam = 'RF02L-D0120'.
ls_bdcdata-fval = 'X'.
APPEND ls_bdcdata TO lt_bdcdata.
CALL TRANSACTION 'FD32' USING lt_bdcdata MODE 'E'.
Thanks,
Naren

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

Using CREATE_TEXT function module in LSMW for Tcode: FD32

Hi Friends,
I have to upload texts to the transaction FD32 via LSMW by using
CREATE_TEXT function module. If anyone has worked on this before
then please clarify the following doutb.
In which event (Begin of record, End of transaction etc) I have to write the code?
Any sample code snippet for this requiremen would be helpful to me.
Thanks in Advance
Murthy

Hi,
Thanks for your responses.
I had found the solution on my own.
Thanks
Murthy

Attachment List - FD32/FD33

Hi...
I want create a copy from Customer for new credit control area, but I need copy the Attachment List too (transaction FD32).
It's possible? How?
Thanks...

Hi...
I want create a copy from Customer for new credit control area, but I need copy the Attachment List too (transaction FD32).
It's possible? How?
Thanks...

FD32 Payment history

Hello,
we have one customer created for company code/credit control area A with payment history
we now created the customer for company code/credit control area B, when looking at the payment history, we see the same payment history as for area A (no payments have been made for B)
Shouldn't the payment history in area B be empty?
kr
N

Hi nico,
Pls do like I would suggest running RFDKLI20 (F.28) Reset credit limit for a specific customer. This job will go through and recalculate all the credit exposure based on the current credit account .
check here also Customer payment history - transaction FD32 and tick 'Payment History' box. (S_ALR_87012218)
Regards
Sridhar
Edited by: sridhar.shetty on Feb 25, 2012 7:55 AM

FD32 Credit management 'sales value'

I am on SAP ERP, I'm trying to figure out how to pull the data that makes up the credit exposure - 'SALES VALUE.' I believe the sale value includes all undelivered or only partially delivered orders. I can not find a way to confirm what makes up the total sales value. How would i oull that detail?
Thanks in advance for your assistance!

check oss note 378833.. it has loads of information.
It is difficult to analyze incorrect open credit values:
The open credit values are updated in Sales Information System (SIS) structures. The structures cumulate values due to common characteristics. Due to the cumulation, you cannot find out subsequently which documents caused the values.
The system generates and reduces open credit values in the SD document chain. The system posts the credit value to the SIS structure and clears it later. This may cause differences between the posted value and the cleared value.
See Note 377165 for a detailed description about updating open credit values.
To correct the incorrect open credit values, proceed as follows:
1. Correct known errors that occur in the update of the open credit values. To do this, check the relevant composite SAP Notes and implement the relevant corrections in your system if you have not yet imported a Support Package that contains them.
1176872 Composite SAP Note: Incorrect credit update, 60*
735791 Composite SAP Note: Credit update incorrect, 500
735163 Composite SAP Note: Incorrect credit update, Release 4.70
410685 Composite SAP Note: Incorrect credit update, 4.6B/C
385481 Composite SAP Note: Incorrect credit update, 4.5B
385091 Composite SAP Note: Incorrect credit update, Release 4.0B
364928 Composite SAP Note: Incorrect credit update, Release 3.1I
2. Use composite SAP Note 425523 to check that there is no explanation for the update that you observed.
3. Check whether incorrect open credit values exist in your system. To do this, compare the sales values in transaction FD32/FD33 (status view) with the results of the report RVKRED88 which you run for the same credit customer and credit control area.
4. Check whether the incorrect update is caused by user exits or by modifications in your system. The following notes describe possible sources of errors in customer-defined source code.
216448 BW/SIS: Incorrect update / SD user exit
178328 Problems due to incorrect user exits in SD
5. Use the report RVKRED77 to correct the open credit values. For more information about the report, see Note 400311 (or the documentation of the report in your system) and Note 363343 or Note 755395.
To determine the reason for the incorrect open credit values and to reproduce the error, proceed as follows. Reproducing the error in the test system is a basic prerequisite for analyzing and correcting the problem.
1. Monitor the open credit values to find out when incorrect values occur. To do this, compare the sales values in transaction FD32/FD33 with the results of the report RVKRED88 again.
2. Identify the documents that were created or changed since the last run of the correction report RVKRED77 in accordance with Note 389377. One of these documents must have caused the incorrect credit values.
3. Try to determine which document caused these values. To reproduce the problem on your test system, use the same data as in the document that is causing the incorrect values.
4. Use transaction MC30 (as described in Note 381789) to check the update of the open credit values after a document is posted.
5. Use Note 1042857 "Logging credit values" to log the update of the credit values so that you can evaluate this later.
If you can reproduce the error in your test system but there is no explanation for the update you observed, open a customer message with logon data, sample data, a detailed description of the procedure and the relevant contact person.

LSMW for FD32

hello All.
i am doing LSMW for making the changes in FD32.
here i wish to update the customer credit limits for the fields
KNKA-KLIMG
KNKA-KLIME
KNKK-KLIMK
what all are the steps that i need to do.
please suggest,i have tried following the standard steps,but little confused.
appreciate your help.
thanks!

Hi there
Go to the transaction LSMW. Click on the create button.
Type in a project name: i.e. Creditlimit
Etc
Etc
once in it click on the button 'DISPLAY/CHANGE'
Then double click on 'Maintain object attributes'
Click on Batch input recording
Click on the overview button in the middle right of the screen
Click on new page (create)
Give the recording a name and description
Type in the transaction FD32
The recording has started now. Do the steps carefully
Put a customer number and select all button. This will jump to the address screen. Click on the right arrow (top left)
This is the screen that you want.
Key figures into all the fields and save the customer. This ends the recording.
In the object screen
Click on 'default all'
Double click on Customer number. Remove the number used in the recording. copy the 'field name' i.e. RF02L-KUNNR and overwrite the first name field. Do the same for the three fields that you need to fill in.
Save and type in the name you gave the recording in the field by batch processing.
Next
Go to Source structures > create new. Give any name like ExcelCSV and a description
Save and go back
Click on maintain source structures. These will be the fields in your spreadsheet.
Click on the name of the source structure and click on Table maintaince (it looks like a spreadsheet)
Type in the exact field names that are in your object maintaince
RF02L-KUNNR                 Char 15   Description
KNKA-KLIMG                    n       18   Description
KNKA-KLIME                     n        18    "
KNKA-WAERS                  C          4    Currency
Save and go back to the steps screen
Click on maintain Structure relations - just save and go back
Click on field mapping and conversion rules Back
Do the same for the others. (you are going to make your spreadsheet in this order) save and go back
Do your spreadsheet, then save it as a CSV field (Comma delimited)
Goto 'specify files' and double-click on 'Legacy data On the Pc (frontend)
select your file (CSV) Change the delimiter to Comma
Just enter and save.
Read Data, > execute (show no of lines > Back > Back
View read data - double click on a line and view it
Convert data, execute > no of lines > back > back
Read converted data > double click on one item and view if all looks fine.
Create batch
process batch.
Hope this helps
Kind regards
Dawn

Transactions FD32

Similar Messages

Maybe you are looking for