Vendor Open items report

BSIK----->BSEG---->EKPE

SUMMERIZATION OF REQUIRMENT

Business require Vendor open items with the details of Profit Centre, PO number, gr
number within desire format.

OVERVIEW/OBJECT OF THE REQUIRMENT

As per standard functionality is not possible to get the VENDOR OPEN ITEMS along with
the details of PROFIT CENTER, PO No, GR No AND DUE DATES etc As per Required
format. Hence, we need to develop the Report to address the requirement of the
Business.

INPUT SELECTION PARAMETERS

1 COMPANY CODE REQUIRED

FIELD
2 PROFIT CENTER From To MULTIPLE SELECTIONS
OPTIONAL FIELD
3 VENDOR From To MULTIPLE SELECTIONS OPTIONAL
FIELD
4 REPORTING KEY DATE
REQUIRED FIELD

LOGIC

Pass the input selection parameters to the BSIK Table and get the vendor open item data
along with the below data from the BSIK table.

VENDOR CODE
DOCUMENT NO
FY
POSTING DATE
BILLING NO (REF NO)
DOC TYPE
AMOUNT IN LOCAL CURRENCY
PO TEXT

Pass the Document Number, Company code, FISCAL YEAR Which is collected from the
table BSIK into the table BSEG and fetch OR get OR collect the below data.

PROFIT CENTER
PO NO
DUE DATE
REFERENCE NO

Pass the PO NO, CO CODE, FY Which is collected from the table BSEG into the table EKBE
--(History Per Purchasing Document)

GR NO
Output:

Vendor Code (BSIK-LIFNR) Vendor Name PROFIT CENTER (BSEG-PRCTR) Doc No (BSIK-
BELNR)

Billing No BSIK-XBLNR Posting Date BSIK-BUDAT Due Date BSEG-FDTAG PO No BSEG-EBELN

GR No EKBE-BELNR Payment Terms BSIK-ZTERM Amount BSEG-DMBTR

Functional Specification

Scenario:

Business requires a program of adding zeroes to the assignement field in documents.

Selection screen

[Link] Code:

[Link] Year :

3.G/L NO.(BSEG/HKONT) : From To

[Link] Nos : From To

Search for Company code, Fiscal Year, and Document Nos from table BSIS as selection parameters
given in selection screen

[Link] Field Table – Field Remark

1 Company Code: BSIS-BUKRS
2 Fiscal Year BSIS-GJAHR
4 Document Nos BSIS- BELNR

Program Logic :

Select the document numbers BELNR from the table BSIS with the above selection parameters.

Then Go to the transaction code FB02, change the assignments field (ZUONR) by adding
prefixes‘000’/00 0to the exciting assignments for all the documents .
1 Functional Specification: Details
Report Z_FCR ageing provides the AR ageing by Business Line. Current report
displays the Original Invoice amount. The new requirement is that the
ageing report to be displayed the Amount after revaluation

1. In the selection screen , output options radio buttons

2.
1. Without Revaluation

2. With Revaluation
If the selection is without revaluation, the report must be same as existing

If the selection is with revaluation, the report should give the details with the
changes as below,

3. The amount field in the report must be changed with Bseg_wrbtr (Amount in document
currency)* Exchange rate from Currency table (TCURR)using report key date
field( P_KEYDAT )and Inv Curr as index instead of WRBTR*[Link] rest of
calculation ageing is the same logic.

Out Put Format: Output format will be the same for both the options ( with valuation & without
valuation)

Document Custome Customer Document Segmen Document

nr r name type t date Due date Keydate

Overdue 1- Overdue 31- Overdue 61- Overdue 91- Overdue >

Non due 30 60 90 720 720

2 Test Scenario’s
Customer No : 1000
Document No. 11001
Invoice amount : 165000(This value to be displayed in the report if the selection
option is without valuation)
After revaluation of the invoice amount : 169000 ( This value to be displayed in
the report if the selection option is with valuation)

Functional Specification

Scenario:
Business requires a report of Net Value( insurance claim and transport charges) and VAT value
against profit centers for a given period in a desired format.

I. Selection screen:

1. Company Code:

2. Fiscal Year :

3. Period :

4. Posting Date: From To

5. Profit Center: From To

Search for Company code, Fiscal Year, Period and Posting Date from table BKPF as selection
parameters given in selection screen and for profit center search in BSEG table. In selection screen
can opt either for period or posting date interval.

[Link] Field Table – Field Remark

1 Company Code: BKPF-BUKRS
2 Fiscal Year BKPF-GJAHR
3 Period BKPF-MONAT
4 Posting Date BKPF-BUDAT
5 Profit Center BSEG_PRCTR

II. Logic Involved:

Select the document numbers BELNR from the table BKPF with the above selection parameters.

Then search for the line items with the same documents in Table BSEG with Fiscal year with the
specified GL Acoounts ( field> HKONT ) (3100 and 3200) of which can make fixed in the program as
constant.

Then Collect Tax Code( field> MWSKZ) for each document/Line item filtered as above and collect the
rate of tax (Field> KBETR) from table BSET.

III. Output

Profit center Description Net value Vat Value Net Value Vat value Total

1 2 3 4 5 6 7

Total (8)

Explanation/logic for each field :

1. Profit Center: Collect the values with profit center PRCTR for each line item and sum up and
display as per the output

2. Description: Collect the profit center Description (Field> KTEXT) from table PRCT_V

3. Net Value : Sum up the values (field> WRBTR) of GL Account 3100

with profit center break up based on the line items available from the table BSEG

4. Calculate the Vat value based on the Tax code ( field> MWSKZ) on each line item with the
following formulae

Field (3) * Rate(Field> KBETR) and tax code collected(MWSKZ) against the documents from
the table BSET .

5. Net Value : Sum up the values (field> WRBTR) of GL Account 3200with profit center break up
based on the line items available from the table BSEG

6. Calculate the Vat value based on the Tax code( field> MWSKZ) on each line item with the
following formulae

Field (5) * Rate(Field> KBETR) and tax code collected(MWSKZ) against the documents from
the table BSET .

7. sum up the values of 3,4,5 and 6

8. Summation of all rows against each column.

Document Splitting Default Profit Center Enhancement

Business Requirement
Enhance the existing Document Splitting functionality for default profit center update in
document line items on company code base instead of controlling area, while simulative
and saving the document if profit center field not selected in all line items of document
then updates the default profit center field in all document line items based on the
company code logic.

1.1 Detailed Description

SAP Standard Document Splitting functionality derive the default profit center based on
the controlling area. Now PBF need the default profit center should derive based on the
company code instead of controlling area.

Standard Document Splitting default profit center functionality is to be enhanced to

update the default profit center in document at line item level based on the company
code.

Reference Function Module is FAGL_DEFPRCTR_DOCUMENT_CHECK.

One new Ztable is required for company code relevant default profit center details
maintain purpose.
Ztable code: ZFI_PRCTR_VAL
Ztable name: Profit center values
 Controlling Area
 Company code
 Profit center

The enhancement should be active for Document splitting active company codes, all
Finance transactions while simulative and saving the document system.

Controlling Area, Company Code and Profit Center fields are to be made as mandatory
and should be validated on user entry with possible entries to be maintained in the
Ztable.

1.2 Design Approach

The Ztable field details are mentioned below:
Field Field Name Type Mandatory / Match
Non- Code
mandatory required
(Y / N)
KOKRS Controlling Area Char(4) Mandatory Y
BUKRS Company Code Char(4) Mandatory Y
PRCTR Profit Center Char(10) Mandatory Y

Enhancing Customer and Vendor Master to use the field Corporate Group for Customer/ Vendor
grouping for BW report

2.0Business Requirement
There is a business requirement to generate a consolidated report for the group of
Customers & Vendors together. The same entity is having multiple vendors & customers
created in SAP based on their addresses. A consolidated report is required to be
generated from BI by grouping this customers & vendors together.

3.0Impact Analysis
As a part of this enhancement, the field Corporate Group will be a “Required” field for the
Customer & Vendor Master. The Corporate Group field will be updated for the existing
vendors & customers. Enhancement will not have any impact on any module. It will
facilitate Finance team in Vendor and Customer reporting.

4.0High Level Design

4.1 Detailed Description
As it is not possible to have many to many relationship between the Customers &
Vendors in SAP, it is decided to use the field Corporate Group. This field will be used to
maintain the Corporate Group id to group the Vendors & Customers together. Currently
this field is not being used in PBF. Z Table ZCORPGR will be created to maintain the
Corporate Group details in order to bring in uniformity in the reporting. The Corporate
Group field will fetch the values from the Z table.

Z transaction ZCORPGR will be created to maintain the Z table.

4.2 Design Approach
The Z table ZCORPGR will be created for maintaining the Corporate Id & Description.

Field Short Text Data Element Field Additional info

/ Field Type Length
CG ID Corporate Group ID Numeric 10 Corporate Group ID
CG Name Corporate Group Char 20 Corporate Group
Name Description

The values maintained in this Z table will be available for Selection (F4 Help) for the
following fields:
Customer Master: KNA1-KONZS
Vendor Master: LFA1-KONZS
The user will not have option to use any value other than maintained in the Z table.

4.3 Configuration Requirement

Corporate Group field will be made Required field for the following Vendor &
Customer Groups:

Vendor: ZPAY, ZCVD

Customer: ZBIL, 0001

SAP FICO Testing

Testing in SAP Implementation life cycle is an important event.

SAP Testing is involved with SAP Standard transactions and custom programs.

Testing verifying the functionality of SAP Standard transactions and custom

programs against business requirements.

What are the different types of testing in SAP project?

Unit Testing

Integration testing

Interface testing

Scenario based testing

User acceptance testing

SAP Stress/Load/Performance testing: It is checking speed of SAP Applications

SAP Security /Authorization Testing

SAP Cutover/Dry run testing

Regression testing: Make sure an existing program has not impacted due to
some other changes.

Ex : Version Upgrade.

Positive Testing: Make program is doing what it is supported to do for a business

requirement.

Negative testing: Not able to do what a function I am not supposed to do.

SAP testing automation tools are like SAP test Acceleration and optimization
tools are often used for this purpose

Test Scenario/Test case: Represent a specific business scenario.

What are the best Automation SAP Testing tools

Automation testing is used to test the application from load, performance and
stress purpose.

This testing is used to increase the coverage of test. It improves the accuracy
and saves time and money in comparison to manual testing.

Testing Tools- HPQC, HPALM,SAP Quality center, Open STA, Load runner, QTP
(Quick test professional tool)

What are the challenges faced during sap FICO testing

During SAP Testing challenges faced are,

 Valid combination of test data required for testing

 All the critical interfaces should be determined, and their connectivity
should be established with corresponding test systems
 To recognize the business processes which are suitable for test
automation
 Identify negative testing conditions
 Mention how does the system design trace back to all captured
requirements and the number of test cases
 Identify Regression scenarios/test cases and build Regression test suite
that requires during each release
 Managing output and input data to complete the scenarios OTC, P2P, etc.
 Design robust Automation Framework that should be maintainable and
scalable
4) Mention how to create an effective SAP Test case. and Answers

 Determine SAP role required to execute the test case

 Identify the SAP transaction that needs to be executed for the test case
 Test Data requires executing the test case. Determine whether the data
needs to be created or whether it is used by another tester or whether the
data is locked & cannot be modified
 Is there any pre-requisites required?
 Create negative as well as positive scenarios
 Create detailed Test Steps
 Test coverage should be robust
 Document defects in a timely manner as soon as they are discovered