cancel
Showing results for 
Search instead for 
Did you mean: 

FD32 Risk category change -- Credit re Org.

Former Member
0 Kudos

Hi,

We are in ECC5.0 and turned on credit management using FD32. My question is: When we change the risk category in FD32 the system prompt us to run program rfdkli20. When we run this program in production system it takes more than 5 to 6 hours per payer and need a quite system (No postings). I would like to know how others are managing this issue. Do you run it in parallel for the same payer with 2 different credit control area or do some thing else to reduce the run time. We have warehouse activities on all the 7 days and find it very difficult to run this. Any ideas.

Thanks Ram

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

You shouldn't have to run the program RFDKLI20. You can initiate the reorg directly from FD32 via menu path Credit management --> Reset.

As for the performance problem, you need to create a index on the payer via config (SPRO: SD --> Sales --> Lists --> Set Updating of Partner Index. Add entry '0 PY').

Remember to execute RVV05IVB in production after making this config change.

Once you have the index set up, this should run so fast that the 'quiet system' will no longer matter.

Refer to Note 30737 for more info on this.

Anisha.

Former Member
0 Kudos

Thanks Anisha,

I will try and post a message once the testing is complete in the QA system. I checked the config you mentioned and we have 7 for the partner function 'PY'. As you mentioned i will add '0' for 'PY' and try. If i have one payer in 2 different creadit control area can i run both in parallel.

Ram

Former Member
0 Kudos

You will have to run the reorg separately for the two different credit control areas.

Also, you should run RVV05IVB in prod in off hours. I think that could take a long time to run.

Anisha.

Former Member
0 Kudos

Hi,

Problem:

When this program RFDKLI20 try to access some tables were used by other programs to retrieve the data or Code stuck in program to access relevant information.

Solution:

1. Cancell the job without core in SM51

2. Go to program RFDKLI20 job and click the job log

3. Take the message text where it has cancelled or Double click on message text it will take to ABAP runtime error screen.

4. Scroll down the screen until you get this sign >>>>

5. Take the value and give it ABAPer

6. They will tell you where your program or data's needs to correct.

regards

rc gopi