As you may already know, we can create COND_A IDocs from condition records report such as VK13, TK13, AKE3 etc (as posted here: Quick and Easy – EDI/ALE – Pricing Condition Records). However, when we are dealing with large number of condition records, the foreground send condition process will takes time and we have to keep our user session until it finished. Thus, we need to somehow create COND_A IDocs in background.
As a quick solution, I choose to utilize transaction recorder with the following steps:
Step 1 – Create Recording
Go to transaction SHDB > New Recording > Put your recording name and VK13 transaction code for my case > Start Recording
In the recording session, the flow should be input Condition Type > Choose Condition Information > Fill up the selection parameter > Execute > Select All (F7) > Send Condition > Fill up Message Type COND_A and target system in Logical System. Then go back until we exit the recording session.
There is may be some challenge when recording selection parameter, especially when we want to use multiple single values. I use ‘select ranges’ to overcome this situation.
Also, I use ‘Select All’ to simplify my recording, thus I have to set selection parameter in such a way that only condition records that I want that will be appear. Attached is sample of my recording.
Step 2 – Create Session
After I saved my recording, next step will be create session based on my recording.
I will send multiple condition types, thus for every condition type I will adjust the recording by just changing the condition type code and the selection program (RV13ANA*) if it has different access sequence then the previous one.
Step 3 – Run the Session in Background
Go to transaction SM35 > Choose your session > Process> Choose Background > Process
Now I can send condition records from multiple condition type in the same time and without developing custom ABAP program. 🙂