Case Study Ppt
-
Upload
amiya-chakrabarty -
Category
Documents
-
view
195 -
download
1
Transcript of Case Study Ppt
Copyright © 2009 Accenture All Rights Reserved. Accenture, its logo, and Accenture High Performance Delivered are trademarks of Accenture.
TRANSACTION UPLOAD
PRIYA SELVAAPARNA PRASHANTHSARANYA PUSHKAR
Copyright © 2009 Accenture All Rights Reserved.
OBJECTIVE:
• To upload an MS Excel spreadsheet of journal entries to SAP.
• Journal entries supported
Posting to Vendor Accounts without clearing.
Posting to Customer Accounts without clearing.
Posting to GL Accounts without clearing.
2
Copyright © 2009 Accenture All Rights Reserved.
PARAMETERS:
INPUT
• File path
• Reference key
• Radiobuttons for check/post
OUTPUT
• Screen output of log
3
Copyright © 2009 Accenture All Rights Reserved.
TABLES USED:
• BKPF:
Accounting document header table.
• BSEG:
Accounting document segment table.
4
Copyright © 2009 Accenture All Rights Reserved.
PROCESS:
5
Copyright © 2009 Accenture All Rights Reserved.
SELECTION SCREEN DESIGN:
6
Copyright © 2009 Accenture All Rights Reserved.
VALIDATION:
• It checks the existence of file.
• Uses AT_SELECTION SCREEN.
7
Copyright © 2009 Accenture All Rights Reserved.
AUHTORIZATION:
• AUTHORITY_CHECK.
• Performs a check against object and fields of user master.
8
Copyright © 2009 Accenture All Rights Reserved.
Copyright © 2009 Accenture All Rights Reserved.
START-OF-SELECTION:
• Introduces any initial processing to be done prior to next event keyword.
GUI_UPLOAD BAPI_ACC_DOCUMENT_CHECK BAPI_ACC_DOCUMENT_POST
10
Copyright © 2009 Accenture All Rights Reserved.
GUI_UPLOAD:
• Function module to process sequential files on the presentation
server.
• Data is transferred to or from an internal table.
• It requires an internal table for data transfer.
11
Copyright © 2009 Accenture All Rights Reserved.
GUI_UPLOAD:
12
Application server files
Presentation server files
READ DATASET
TRANSFER
GUI_UPLOAD
GUI_DOWNLOAD
Copyright © 2009 Accenture All Rights Reserved.
GUI_UPLOAD:
13
CALL FUNCTIONGUI_DOWNLOADCALL FUNCTIONGUI_DOWNLOAD
File name:
File type:
CALL FUNCTIONGUI_UPLOADCALL FUNCTIONGUI_UPLOAD
File name:
File type:
Convertaccording tofile type
Convertaccording tofile type
Convertaccording tofile type
Convertaccording tofile type
Copyright © 2009 Accenture All Rights Reserved.
BAPI:
• RFC Enabled Function module.
• Is an interface for data transfer.
• Provides access to different business process.
14
Copyright © 2009 Accenture All Rights Reserved. 15
Copyright © 2009 Accenture All Rights Reserved.
BAPI:
16
Copyright © 2009 Accenture All Rights Reserved.
BAPI FUNCTION MODULES:
• BAPI_ACC_DOCUMENT_POST
• BAPI_ACC_DOCUMENT_CHECK
17
Copyright © 2009 Accenture All Rights Reserved.
TESTING REQUIREMENTS
• ID • Condition • Expected results • Cycle Ref.
• Check an input file • File is checked and a log is generated.
• Load a single GL document • GL document posted. Log indicates total debits and credits which ties to source Excel file.
• Load multiple GL documents • Multiple GL documents posted. Log indicates total debits and credits which ties to source Excel file.
• Load of AR invoice/credit memos • AR documents posted correctly. Log totals tie to source file.
• Load of AP invoice/debit memos • AP documents posted correctly. Log totals tie to source file.
• Load of mixture of AR, AP and GL documents.
• Documents post correctly. Log indicates correct totals.
Copyright © 2009 Accenture All Rights Reserved.
TECHNICAL TEST CONDITIONS• ID • Condition • Expected results • Cycle
Ref.
• Load of multiple GL, AP and AR documents with correct data.
• All documents posted successfully. Error log tallies with source Excel file.
• Check/Post of file with incorrect/non-existent filename
• Program ends with an error message (no log) indicating that the file does not exist.
• Load of document with more than 950 lines • Program log indicates that document could not be posted due to the number of line items.
• Foreground processing of a file with 66,000 lines.
• No time-out. All journal entries loaded.
• Check/Post of file with bad source data, e.g. incorrect account numbers, cost centres.
• Program log indicates that the data is incorrect. In ‘Post’ mode, the correct records are loaded and the incorrect records ignored.
• Check/post of file with legacy code which is not mapped to a profit center/cost center
• Program log indicates that no mapping could be found for the legacy code. Record is not posted.
• System shuts down during processing. • No log generated of documents posted. Use of compact document journal allows user to easily reconstruct what has been posted and what has not been posted.
Copyright © 2009 Accenture All Rights Reserved.
FIELDS:
Additional fields not reflected in the standard transfer table but
used by the BAPI interfaces.
Manufacturer
Commodity
20
Copyright © 2009 Accenture All Rights Reserved.
USER EXITS
• Allow us to add our own functionality to SAP standard program.
• Modification is not required.
• SYNTAX:
FORM USEREXIT_..
……..
ENDFORM.
Copyright © 2009 Accenture All Rights Reserved.
LOG FILE
• A list of SAP accounting document numbers generated with external document numbers
• The total debits and credits posted
• The total number of line items posted.
• Error log detailing failed documents.
Copyright © 2009 Accenture All Rights Reserved.
OUTPUT SCREEN: