I want to chain va01 and me21n. purchase requistion number will be at sales order schdule line data. by taking that number i have to create a purchase requisition. i can do chaining by taking number from the messages with the help of &ms1, &ms2 etc. How to do chainging by taking data from sales order shedule line. That purchase requisition number will be in grey mode and it will appear only in sales order change mode(va02).
thanks in advance
You can do chaining of parameters. You can even take the values from the message parameters and pass that value to next transaction as input.
Find the following weblog written by me for step by step chaining details-
Hope this helps.
PS If the answer solves the query, plz close the thread by rewarding each reply and mark it Solved.
I've found your blogs very helpful, but now I'm stuck. I have the transactions VD01, VD02, and VD06 chained, with the customer number in the VD01 message stored and parameterized for use in VD02 and VD06.
My problem is that while the chaining works fine, the subsequent transactions VD02 and VD06 (which I REF-ed after VD01) are always pulling the customer number created prior to the script creation. For example, if I run the chained script, I get a message "Account 87 has been created" at the completion of the VD01 part. Then, when it proceeds to VD02 and VD06, it uses customer number 86.
I've tried REFing a separate script that is just the ABAP code to COMMIT WORK and that fails.
So, I've worked through your blog, and done everything I can, but I cannot figure out how to make subsequent transactions use the actual data generated by the first script. Can you help, please?
SAP CATT - Computer Aided Test Tool
Just sharing my experiences with CATT (although, I have not used this feature in the last 2 years or so !).
Simply, any one in SAP can use this tool as long as you can access to the tcode. I used CATT atleast in 3 different SAP modules. Typically, in SAP projects, CATT execution is a favorite task for "technical" associates. When the technical resources are either not available immediately or their plate is full with other important tasks, functional associates can simply jump into this activity, since there is no coding or programming involved. This tool has been a great gift from SAP since I am a functional person and could not do coding ! I can remember at least 30 or 40 occassions where I used CATT to get this and that done.
Below find few examples:
1. Created multiple sales orders (excess of 200) in a matter of minutes for the purpose of end user training
2. Created multiple purchase ordes (excess of 200) in a matter of minutes for the purpose of end user training
3. Created Deliveries for the sales orders in a matter of minutes for the purpose of end user training
4. Created config. entires, if the volume of records is large. I remember once I entered 900 records.
5. Extensively used in preparing the transactional data for the purpose of archiving. It worked impeccably.
6. Loading of master data (example: material groups)
Note: Upon execution of CATT, it is very possible that some records will fail, which have to be addressed manually. SAP really needs to further enhance this area of CATT because, there is no easy way of identifying the failed ones, it has to be done manually. One workaround is simply download the result into an Excel and using sort feature of Excel, identify the failed ones and deal with them manually.
With Compliment by: Ranga Rachapudi
CATT stands 4 Computer Aided Testing Tool
Although CATT is meant for as a testing tools, many SAP users have now use CATT frequently to upload vendors master data and make changes to other master record.
SAP Consultant and Abapers tends to used it for creating test data.
With CATT, you don't have to create any ABAP upload programs and this save on development time. However, you still have to spend time on data mapping into the spreadsheet format.
The transactions run without user interaction. You can check system messages and test database changes. All tests are logged.
What CATT does is record you performing the actual transaction once.
You then identify the fields that you wish to change in that view.
Then export this data to a spreadsheet to populate with the data required.
This is uploaded and executed saving you keying in the data manually.
To perform CATT, it has to be enabled in your production environment (your systems administrator should be able to do this - SCC4).
You will also need access to your development system to create the CATT script.
With Compliment by: Vijay
User Guide for Data Upload
The use of CATT is for bulk uploading of data. Although CATT is primarily a testing tool, it can be used for the mass upload of data. The way CATT works is like a real user actually inputting on the SAP screen. You prepare a set of data that are required to be input into the system and execute what you called a Test Case and CATT will do the boring task of keying for you.
The over-all procedure to upload data using CATT is as follows:
· Creation of the CATT test case & recording the sample data input.
· Download of the source file template.
· Modification of the source file.
· Upload of the data from the source file.
Details of each step are provided in the following paragraphs.
Creation of the CATT test case:
Creation of the test case is completed as follows:
· Execute Transaction SCAT
· Name the test case. Test case name must start with Z. It is also good practise to include the transaction code in
the test case name (e.g. Z_IE01_UPLOAD for the upload of equipment)
· Click the Record button.
· Enter the transaction code (e.g. IE01)
· Continue recording the transaction. Ensure data is entered into every field that is to be used during the upload.
· Save the test case.
Download the source file template
Download of source file template is conducted in two stages as follows:
· Creation of import parameters:
· Within transaction SCAT, Double Click on the TCD line in the Maintain Functions screen.
· Click the Field List button (Field list is displayed).
· For every field that you wish to upload data, double click in the Column New field contents (This creates an
· In the Maintain Import Parameter Pop-Up:
· Delete the default value if not required.
· Press Enter
· The New field contents column now contains the character & followed by the field name (e.g. &EQART). This
is the name of the import parameter.
· Repeat this for every field (in every screen) to be uploaded.
· Back out and save the CATT test case
· Download of source file template:
· Use the path GOTO -> Variants -> Export Default
· Select path and file name (e.g. C:TEMPZ_IE01_UPLOAD.TXT)
· Click Transfer
Modify the source file
The downloaded source file template is now populated with the data that is to be uploaded. This is completed as follows:
· Using Excel, open the tab-delimited text file.
· Do not change any of the entries that already exist.
1st row contains the field names.
2nd row contains the field descriptions.
3rd row displays the default values which are set in the test case.
4th row contains a warning that changing the default values in the spreadsheet has no effect on the actual default values.
· The data to be uploaded can be entered in the spreadsheet from row 4 onwards (delete the 4th row warning &
replace with data for upload).
· Save the file as a Text file (Tab delimited).
Upload data from the source file
Uploading the data is completed as follows:
· Execute the CATT test case
· In the Execute screen:
· Set processing mode to Errors or Background (your choice).
· Set variants to External from file.
· Click the Choose button and select the file to be uploaded.
· If uploading to another client, click the Remote execution button and select the RFC connection to the required client.
· If uploading to the current client, click the execute button.
Also, refer the links....
Reward points if useful...
we are using inline ABAP to get the PREQ number.
MESSAGE ( MSG_1 ). SAPGUI ( SAPGUI_1 , DVX910 ). ENDMESSAGE ( E_MSG_1 ). L_SALESDOC = SALES_DOC. ABAP. select banfn from vbep into l_BANFN where vbeln = L_SALESDOC. exit. endselect. ENDABAP. E_BANFN = l_BANFN.
The first step is the VA01 that is capsuled with MESSAGE and ENDMESSAGE.
The result of VA01 is moved in to the variable SALES_DOC (using the message).
Then the inline ABAP starts.
As I do not know the line item number, I just read the table VBEP and exit the selection after the first hit.
I hope this helps.