Integrated Testing

[Former Member]

Can anybody give me the clear picture for INTEGRATED TESTING with detailed Example?

Thanks

[email protected]

[Former Member · Accepted solution]

hi Kishore,

FI-MM: The integration between FI-MM happens in T-code OBYC.

1. When PO is created :

-

---

No Entry -

---

2. When GR is posted

Inventory Account dr (Transaction Key BSX in OBYC)

To GRIR account (T.Key WRX in T-code OBYC)

3. When Invoice is posted

GRIR account Dr.

Vendor account Cr.

4. Payment made to Vendor

Vendor A/c Dr

To Bank Clearing A/c Cr.

Points to know : Movement Types, Assignment of Movement types to T-keys (T-code OMJJ), Value string (I also need some information on this) , OMWN and OMWB transactions.

---

There is a close integration b/w FI & MM, actually document flows from MM to FI in the following areas such as,

1. Movement Types:

Used to enable the system to find the predefined posting rules determining how the accounts of financial accounting system are to be posted & to update the stock fields in the matrl master data.(Goods Receipt, Goods Issue, etc)

2. Valuation Class:

Assignment of material to grp of gl account, used to determine the gl accounts that are updated as a result of goods movement.

3. Transaction/Event key:

Used to control the storage or filing of documents & assignment of documents.Used to differeniate b/w various transactions such as goods movement tht occur in inventory.

4. Material Type:

Each material should assign mtrl type in mtrl master record used to update whether changes made in qty are updated in material master record & change in value also updated in stock account.

FI-SD Integration: The integration is done in T-code VKOA

1. Sales Order Created

-No Entry-

2. PGI done (Goods issue)

Cost of Goods Sold Dr (Configured in OBYC GBB T-Key)

To Inventory Account

3. Billing document released to Accounting

Customer Account Dr.

To Sales Revenue Account (ERL T-key in Pricing procedure)

Note : The GL account is assigned to this ERL in VKOA

4. Payment Received

Bank Clearing A/c Dr

Customer A/c Cr.

Points to Know : Good to understand the pricing procedure and how the different transaction keys are used like ERL, ERS etc

FI-MM integration scenarios

1. Procure to pay: a) Purchase requisition b) purchase order 3)goods receipt

d)invoice receipt e)Payment f)balance verification g) Reports

2.Invoice to receipt:a)Goods issue b)sales order c)goods issue d)cash receipt

e)balance verification f)Reports

3.FI-PS :a)Create project b)Define structures(wbs elements,networks,acivities )

c)Release Project d)Project/WBS planning e)Project/WBS budgeting

(Create,release,transfer,suppliments etc) f) Actual postings from all

modules(FI,CO,MM,SD,HR) g) Define settlement rules h)settlement

http://help.sap.com/saphelp_erp2005vp/helpdata/en/26/08723521faee41e10000009b38f889/frameset.htm

Assign me the points....

Ranjit

[Former Member]

Dear Kishore,

Testing

: the core team members along with endusers will test whether the postings done in SAP is resulting as per the requirements of the organisation. They will test whether the output documents such as purchase order, invoice document are printed in the required format and showing the correct data.

Unit testing

is refer to the module which are going to implement. SD, MM, FICO etc. there will be test script based on that testing will be performed.

A unit test is a procedure used to validate that a particular module of source code is working properly. The procedure is to write test cases for all functions and methods so that whenever a change causes a regression, it can be quickly identified and fixed. Ideally, each test case is separate from the others; constructs such as mock objects can assist in separating unit tests. This type of testing is mostly done by the developers and not by end-users

eCATT: extended Computer Aided Test Tool (BC-TWB-TST-ECA)
Use extended Computer Aided Test Tool (eCATT) to create and execute functional tests for software. The primary aim is the automatic testing of SAP business processes. Each test generates a detailed log that documents the test process and results.

eCATT enables automatic testing in SAP GUI for Windows and SAP GUI for Java. In order to offer a complete test solution that covers other GUIs, eCATT has interfaces to third party tools.

Test cases usually make database changes. Therefore, you should not normally run them in productive systems.

In general, do not use eCATT to manipulate data in a productive system: eCATT is a test tool. Instead, use techniques such as Batch Input.

eCATT can be used with the Test Workbench.

You can migrate test cases from Computer Aided Test Tool (CATT) to take advantage of the better features of eCATT.

eCATT is also integrated with the Object Navigator (SE80).

You can:
· Test transactions, reports, and scenarios
· Call BAPIs and function modules
· Test remote systems
· Check authorizations (user profiles)
· Test updates (database, applications, GUI)
· Test the effect of changes to customizing settings
· Check system messages

eCATT runs in a system based on SAP Web Application Server 6.20 or higher. However, you can use this system to test systems with Release 4.6C or higher.

You can find a step by step introduction to eCATT in the eCATT Tutorial.
http://help.sap.com/saphelp_nw04/helpdata/en/1b/e81c3b84e65e7be10000000a11402f/frameset.htm




http://www50.sap.com/businessmaps/6D1236712F84462F941FDE131A66126C.htm
http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wbia_adapters.doc/d...

Integration testing

will be cross the modules. MM-SD-FICO for example. Integration testing is also called SIT ( System integration testing)

Testing mathologies and types: there are 6 types of testings:
1.

Unit Testing

2. System Testing
3.

System Integration security Testing

4. Performance Testing
5. User Acceptance testing
6. Regression Testing

Unit testing

is done in bit and pieces. Like e.g. in SD standard order cycle; we do have 1-create order, then 2-delivery, then 3-transfer order, then 4-PGI and then 5-Invoice. So we will be testing 1,2,3,4 and 5 seperately alone one by one using test cases and test data. We will not be looking and checking/testing any integration between order and delivery; delivery and TO; TO and PGI and then invoice.

Whrereas

System testing

you will be testing the full cycle with it's

integration

, and you will be testing using test cases which give a full cyclic test from order to invoice.

Security testing you will be testing different roles and functionalities and will check and signoff.

Performance testing is refered to as how much time / second will take to perform some actions, like e.g. PGI. If BPP defination says 5 seconds for PGI then it should be 5 and not 6 second. Usually it is done using software.

Regression testing is reffered to a test which verfies that some new configuration doesnot adversly impact existing functionality. This will be done on each phase of testing.

User Acceptance Testing: Refers to Customer testing. The UAT will be performed through the execution of predefined business scenarios, which combine various business processes. The user test model is comprised of a sub-set of system integration test cases.

We use different software during testing. Most commonly use are

Test Director: which is used to record requirement, preparing test plan and then recording the progress. We will be incorporating defects that are coming during these testings using different test cases.

Mercury Load Runner: is used for performance testing. This is an automatic tool.

What does the following terms means :
- Technical Unit Testing
- Functional Unit Testing
- IntegrationTesting
- Volume Testing
- Parallel Testing?

Technical Unit Testing: Test of some technical development such as a user exit, custom program, or interface. the test usually consists of a test data set that is processed according to the new program. A successful test only proves the developed code works and that it performed the process as as designed.

Functional Unit Testing: Test of configuration, system settings or a custom development (it may follow the technical unit testing) These usually use actual data or data that is masked but essentially the same as a real data set. A successful test shows that the development or configuration works as designed and the data is accurate as a result.

IntegrationTesting:

Testing a process, development or configuration within the context of any other functions that the process, development or functionality will touch or integrate . The test should examine all data involved across all modules and any data indirectly affected. A successful test indicates that the processes work as designed and integrate with other functions without causing any problems in any integrated areas.

Volume Testing: testing a full data set that is either actual or masked to insure that the entire volume does cause system problems such as network transmission problems, system resources issues, or any systemic problem, A successful test indicates that the processes will not slow or crash the system due to a full data set being utilized.

Parallel Testing: Testing the new system or processes with a complete data set while running the same processes in the legacy system. A successful test will show identical results when both the legacy system and new system results are compared.

I would also note that when a new implementation is being done you will want to conduct at least one cut over test from the old system to the new and you should probably do several.

What kind of testings that are carried out in testing server?

1. Individual Testing ( Individually which we've created)

2. Regressive Testing ( Entire Process)

3. Integration Testing ( Along with other integrated modules)

The 3 types of testing is as follows:-

1. Unit testing (where an individual process relevant to a SD or MM etc is tested)

2. Integration testing (where a process is tested that cuts across all areas of SAP).

3. Stress testing (where lots of transactions are run to see if the system can handle the data)

Regards,

Naveen.