Professional Documents
Culture Documents
Hello,
please read explanation below
DEV ID Sales tax report
Functional Team Zaid Azam
(phone)
SAP Dev. Team (lead) Zaid Azam (phone #)
(member) (phone #)
Phase / Priority Phase 1
Medium
The above part is just a header, which system the report is in what report is it i.e sales report, material
reprot etc, then the consultants name, lead name etc.
how important it is medium , low, high
Revisions
Rev. Id Rev. date Author Description
00 Initial release
1 Report definition
Basic Information
Report type 1 A/P
Report type 2 Printed
Language requirem.
Printer requirement Local printer / system printer
Paper requirement Landscape
Source environment: R/3
Module: FI
Suggested technique ALV / other
Triggered: Manually
Frequency: On-demand
Volume: Daily
Then in the report definition
you specify what module it is in i.e FI, MM etc
what subledger AP/AR etc
how often it will be printed etc etc ( nothing really usefull here, just giving a business touch)
Functional Requirements
Functional Requirements
Selection Posting Date, G/l account
Narrative flow The report should list the all the transactions of the G/l account( all items i.e open and
cleared) selected on the initial screen. It should list the vendor name and number when a G/l
transaction is of a vendor
Assumptions / issues
Should have the capability of being exported to excell
In the format i put an excell view of how the final report should look like
4.2 Header elements
SAP Field Report Field Comment
BSAK LIFNR,BSIKLIFNR Vendor number
LFA1_NAME1 Vendor Name
BSIS_BUDAT Posting Date
BSIS_HKONT G/l account
4.3 Line item
SAP Field Report Field Comment
BSIS_WRBTR amount
BSIS_BLART Document type
BSIS_SGTXT Item text
BSIS_BSCHL Posting Key
Then i enter the fields that should be there in the report first the table name is liste then the technical
name and then the english name. Both header and line items are sprecified.
Hope this helps feel free to ask any furhter clarifications
Thank you so much for a quick reply. I really wanted to understand this ASAP. I appreciate your effort
and answers. I still have one question, hope you won't mind to answer me in a sentence or two.
How would you summarize this? I mean what was problem and how did you solve that from this func
spec. Hope you understood my question. I am just looking for 2-3 sentence answer like "this was the
problem and I acheived that from this func. spec."
You effort is rewarded with reward points.
the requirement was to add the vendor name to the fbl3n screen, we couldnt add this so we we went
for a new report with all the fbl3n fields + vendor name. This is a spec for the program.
http://www.youtube.com/watch?v=W-oPV3P2N0w
Question: What is GAP Analysis in terms of FI/CO? Explain in detail with an example.
Answer: Gap means small cracks. In SAP world or in Information Technology world, gap
analysis is the study of the differences between two different information systems or applications
(ex; existing system or legacy system with Client and new is SAP), often for the purpose of
determining how to get from one state to a new state. A gap is sometimes spoken of as "the space
between where we are and where we want to be."
Gap Analysis is undertaken as a means of bridging that space. Actual Gap Analysis is time
consuming and it plays vital role in Business Blueprint (AS IS Process) stage. A through Gap
Analysis will identify the gaps between how the business operates and its needs against what the
package can or can't do. For each gap there will be one of three outcomes which must be
recorded and executed,
A point worth mentioning here is that at time people confuse between user-exits and Gap
Analysis. User exits are standard gate ways provided by SAP to exit the standard code and we
can write our own code with the help of ABAP workbench, it is not new functionality which we
are trying to build in sap but its slight enhancement within the same code.
Gap analysis is start point of Realization and once Business Blueprint is finished we have to find
the realization of sap system for client requirement and there will be certain gaps when compared
to system fit. Those gaps can be closed either by re-engineering of business process to fit with
SAP or we have to use USER exits in case of small deviations or complete enhancements with
the help of ABAP to fit with the SAP system.
In short, GAP Analysis for SAP means identifying the gaps between how the business operates in
a particular scenario and how SAP software operates in a particular scenario. Gap analysis can be
narrowed down to headings like, gaps in master data, gaps in transactional process, gaps in
reports, gaps in all RICEF objects.
1.
The point of creation of asset varies in case of a Corporate asset and Other Dept. assets.
In case of corporate asset, the asset creation process would start after the invoicing is done. So
the cost would initially be expensed out and after the asset is created, the cost would be
transferred to the asset from the expense.
In case of assets other than the above, the asset creation would take place prior to the creation of
the Purchase Requisition, since the asset number would flow to the Purchase Order and
subsequently to the invoice.
The cost category should be defaulted to corporate if corporate asset is selected on the BA
screen. In such a case, Other Dept asset selection will not be allowed on any further lines. The
same applies to selection of Other Dept. asset on the BA (Budget Application) screen.
Hence, a Budget Application can be created entirely for a corporate asset or Other Dept. assets.
Cost category field required at the line depending on the nature of the goods/services. Depending
upon the cost category field selected, the dropdown in OHC code should be restricted. Whether
the fields Cost center, OHC code, Sub OHC, Activity Code and Segment Code are required or
optional or not available for entry should depend on the Cost Category.
2.
GL
Major Findings
Redundant GL Accounts exist in Operative and Global Chart of Account
Business area wise Financial Statement has not been activated
Closing Activities such as Automatic Clearing, Foreign Currency Valuations for G/L
balances, and Carry forward Balance, are not being carried out.
Accounts Payable / Accounts Receivable: Standardization and Automation for Vendor Payment
and Customer Incoming has not been executed properly
Customer Aging is not available since the accuracy of billing data is not yet established
Dunning and Customer statement of Account is not being configured and used
Closing Activities such as Automatic Clearing, Foreign Currency Valuations for Vendor &
Customer and Carry forward Balance, are not being carried out
Bank Accounting: Cash Positioning and Liquidity Forecast has not been configured and used at
all. SAP Banking Functionality, Manual or Automatic is not being configured and used at all.
Controlling: Redundant and Unused Cost & Profit Centers exist in Operative Hierarchy for
Overhead controlling
Cost element Contains Duplicate and Unexplained Accounts
Cost Centre Cycle and their assessment to PA need to be reviewed in detail for accuracy and
synergizing the Cost Allocations
3. The Gaps can differ from company to company. Most commonly, however, missing
functionality is industry-specific.
Examples:
1. MGM Studios and Lycos sometime back worked with SAP to develop its new intellectual
property management and media advertising management functionality, respectively.
2. A leading Oral care product company wanted the promotion of free-goods where they wanted
'Buy one get 2 different products free'.