Showing posts with label FI. Show all posts
Showing posts with label FI. Show all posts

Saturday, 22 April 2017

CIN configuration in SAP SD

CIN configuration in SAP SD

In his video you will see the concept of CIN and step by step Configuration in SAP SD


Also see

Friday, 31 March 2017

SAP Tips and Tricks - 3

/n - Takes the user to the root SAP Easy Access menu from anywhere.
/n + [T-code] - Takes the user directly to the desired T-code from anywhere. For example, “/nVA01” will take the user directly to the Create Sales Order screen.
/* + [T-code] Like ‘/n + [T-code]’, but takes the user directly into the desired T-code with the last values used. For example, “/*XD02” will take the user directly into change mode screen for the last customer you were changing.
/nexCloses all windows for the current system/client and logs off of SAP.
/oAlone, it will generate an “Overview of Sessions” screen for the current system. It also allows you to generate a new session.
/o + [T-code]When used as a prefix to a transaction code, it will open the target transaction in a new window. For example, “/ova01” will open up the Create Sales Order screen in a new window.
Ctrl-Y - Use this key combination on a variety of screens to grab several lines of text or several cells of values in a table. Results can be pasted just about anywhere including Word, Excel, and Outlook. After you hit Ctrl-Y, you will see the mouse pointer turn to a cross-hair. You can then select values from ALV tables, SAPscript reports, etc.
SEARCH_SAP_MENUThis t-code is available on most newer versions of ECC. It will allow you to perform a text search for a specific transaction code or text string and returns all possible menu paths to arrive at related t-codes.
SDMOThis T-code allows the user to search for Transaction Codes using one or two text strings.
PDF! - to download a pdf copy of any print preview.
SU3 - T code to manage your own user id and default settings.
PID - On any field, press F1 and then on help window press F9 (technical information) - you will know the parameter id for the field if there is one.
Debugging - Have a notepad file with below code:
[ FUNCTION ]
Command= /H
Title=Debugger
Type=SystemCommand
While running the transaction, drop this file on transaction screen, the debugging will switch on.
Use ALT+F+W and ALT+F+U in SAP Easy Access Screen to download and upload the user favourites within/across systems.
CTRL+? - to go to the tcode command field on SAP screen.
CTRL+/ - Cursor jumps directly to the OK-Code field.

Saturday, 31 March 2012

SAP eCATT Step by Step

eCATT (extended Computer Aided Test Tool) is an SAP Testing Tool used to automate & test business scenarios in SAP R/3. Each test that was executed on eCATT will generate a detailed log on test process and results. If the testing is successful without any errors log we can say that the business scenario mapped in SAP is correct. If the test results shows error then the problem can be analyzed using the error log that is generated by the system

You will get to know what eCATT is, how we can use it, how we can load a test data from a file in ECC 6.0 with an example

Transaction Code: SECATT

1) Create Test Script


Click Create or F5 and the following screen will be displayed


Enter Title as required and the Component as BC-TWB-TST-ECA and Click on the Pattern Button on the menu bar

An Insert Statement dialog box appears


Select Group as UI Control, Command as TCD (Record), Transaction code as MM01 and Press Enter. The system generates a default interface as a MM01_1
Click the Enter

System will start Record the function that you are attempting to perform i.e creation of Material Master


Select the material views, organizational elements as required and follow the views of the material master. After creating material master system will be returned to the eCATT and prompt the alert box with message

You will see following screen


Now double-click on the interface. In this example the interface was named MM01_1, 

you will get following screen


By using split screen now you can navigate through various screens you are recorded and replace the fixed values with variables


This is done by opening the Dynpro menu and going through each numbered screen to review your input

From the above screen print you can see the values Industry sector “M “and Material Type “FERT” as in input values i.e. VALIN. You must change it to a value as shown in the next screen


he variable names are MBRSH and MTART for industry sector and Material type respectively. Once you enter the variable name and press ENTER, the following screen will appear


The default parameter will be Local. You can change this to Import and click on the "Yes" button

The screen will now look like the following screen. Note the icon on screen 1 has changed from the Green Square. This icon indicates a variable is present


Now you can change the all the variables in same process
Click on SAVE icon after completing and save as a local object or place in a development class to transport the eCATT



Click on the SAVE icon you can see the message” Test Script: “………..” saved successfully is generated

2) Creating Test Configuration
Before executing eCATT first you need to create a Test Configuration. Use Transaction code SECATT to executing and entering a name for the Test Configuration and clicking on the Create icon. (In this Example I have given same name as Test Script)



Give Test Configuration a Name and Component and then click on the configuration tab to see the following screen


Enter the name of the Test Script you would like to execute
 Download icon or just press ctrl+shift+F11. You will be prompted with a window "save as" dialog box. Accept the default name and directory and click save, here file will be saved in text format (ex: VAR_ECTC_Z_MATERIALMASTER_MM01.TXT)

After click on SAVE system will prompt the following alert box


This appears since we did not create a Test Container. Click on the YES icon and you can see the message at the bottom of the screen "variants successfully downloaded"

Now click on the Variants tab and you should see the following screen


We must now set the default mode for each time the Test Configuration is executed. Since you will always be running the script with an external file choose the External Variants /Path option


Now click on the drop-down on the File and choose the variant file you just created in the previous step. Your screen should look similar to the one shown below:


Now click on the SAVE icon and save as a local object or place into a development class (package) so that it can be transported

The message
appears at the bottom of the screen
Now you are ready to execute your new eCATT Test Script via the Test Configuration. Open your .txt file and convert the file in to excel file (ex: VAR_ECTC_Z_MATERIALMASTER_MM01.xls) enter your variables


Convert the same Excel file to text file to upload during the execution. If you upload it in .xls format, then SAP will not be able to read it
Now go back to SAP and run tcode SECATT and enter your Test Configuration and click Execute. You can see the below screen


You can choose your Error behavior. Change it to "NO termination, Continue with Next Script Command"
Click on the Variants tab and validate the mode and file path are correct


Click on the UI control and specify whether you would like to execute in the foreground or background. The test configuration will normally default to the background. As with the CATT the foreground method of execution is very helpful when trying to troubleshoot errors in the test script


Then click execute and you are done
eCATT display log appears



Also see


CIN configuration in SAP SD

CIN configuration in SAP SD In his video you will see the concept of CIN and step by step Configuration in SAP SD Also see ...