AP350 FD E FIN EF005 - Asset Master Uploader v.0.1

Report Functional Specifications

OoredooAsset AccountingAsset Master Upload

Prepared byFerdian P PutraReviewed byApproved by

Date 11/11/2013DateDate

Asset Master Upload

Sign-Off

NameDate (DD-MM-YYYY)Signature

Revision History

VersionDateAuthorStatusDescription

0.111/11/2013Ferdian P PutraFirst Draft

RICEF Work Unit #: (Required)[-I-###]

Interface Title: Asset Master Data Upload

Module & Sub module: FI - AA

1a. General Requirements

Functional Description of Interface: (Required)The purpose of this interface is to have tool to create multiple asset master data from external file.

From System:To System:N/ASAP AAFrequency:Processing Type:Daily Async Asynchronous interface, not real time update. Update might be triggered by user or batch job.Owner:Audience:Asset AccountingAsset Accounting

Business Driver:KPI to improve the efficiency of asset master data creation

Priority:Medium - Item is not required to run the business on 'day one' and indirectly supports the business case and quality of the project.

Complexity:Medium - 2 to 5 transactions in upload or data read from 5 to 9 tables in download. Moderate ABAP (some validation). Some retry logic and error processing. Minimal reconciliation. 2 to 4 external files; 3 to 5 more different record types.

Design Assumptions:The program might be able to process file with multiple asset master data. No transaction data (e.g. acquisition, etc.) will be posted in this asset upload program. If any error happened during the uploading, the program will cancel all process and generate error log. Every successful process, program will generate successful log.

1b. DesignProcess Flow Diagram:

Detailed Description of New Interface/Changes to Existing Interface:The enhancement will have the capability to upload multiple asset master data and if have any error, it can cancel all asset master data creation.Log file will be available for error/successful processing. The created asset number will be displayed in successful log.

SAP Transaction ID (Inbound only):AS01 Create Asset Master DataAS06 Delete Asset Master Data

Standard Load Module (IDoc/ALE/BAPI/Direct Input/BDC) (Inbound only):BAPI_FIXEDASSET_CREATE1

Selection Criteria:[When selection screen is needed please provide selection criteria for the enhancement required in the following table]

Input/Output File Layout: InputInput file name: Input file type: spreadsheet (xls)Input file layout:

PositionField NameField DescriptionData TypeLength

1ASSETCLASSAsset ClassC6

2COMPANYCODECompany CodeN4

3ASSETDESCRIPTIONAsset DescriptionC50

4ADDITIONALDESCRIPTIONAdditional Asset DescriptionC50

5BUSSINESSAREABusiness AreaN4

6COSTCENTERResponsible Cost CenterC10

7CATEGORY1Category 1C4



10WBSELEMENTWBS ElementC

11INVENTORYNOInventory NoN

Output Error LogLog file name:Log file type: spreadsheet (xls)Log file layout:


1RECNORecord numberNumeric4

2MESSAGEMessageCharacter200

Success LogResult file name: Result file type: txt file (txt)Result file layout:


1ASSETCLASSAsset ClassC6

2COMPANYCODECompany CodeN4

3ASSETDESCRIPTIONAsset DescriptionC50

4ADDITIONALDESCRIPTIONAdditional Asset DescriptionC50

5BUSSINESSAREABusiness AreaN4

6COSTCENTERCost CenterC10




10SITEIDSite IDC8

11INVENTORYNOInventory NoN

12NUMBEROFCREATEDASSETNumber of Created AssetsN12

Data Mapping:[Provide the field name, a short description, and any functional notes, translations and calculations. If a transaction was referenced to obtain the table and field names, please list the transaction code.]Transaction Code Screen NumberSAP Table Field NameSAP DescriptionExternal Field NameExternal Field DescriptionFunctional Notes/ Calculations/ Translations

AS011ANLA- ANLKLAsset ClassASSETCLASSAsset ClassMandatory

AS012ANLA-BUKRSCompany CodeCOMPANYCODECompany CodeMandatory

AS013ANLA-TXT50Asset DescriptionASSETDESCRIPTIONAsset DescriptionMandatory

AS014ANLA- TXA50Additional Asset DescriptionADDITIONALDESCRIPTIONAdditional Asset Description

AS015ANLZ- GSBERBusiness AreaBUSSINESSAREABusiness AreaMandatory

AS016ANLZ-KOSTLVCost CenterCOSTCENTERResponsible Cost CenterMandatory

AS017ANLA- ORD41Evaluation Group 1CATEGORY1Category 1



AS0110ANLA-PS_PSP_PNR2WBS ElementWBSELEMENTWBS ElementMandatory

AS0111ANLA-INVNRInventory NoINVENTORYNOInventory No

Processing Details (Business Rules/Selection Criteria and Validation):The program will have screen to upload file similar to the following illustration:

Once the file uploaded, the user will have one TCODE to process it.

The following is technical processing logic:1. Program will read and validate all the data in file (mandatory and length).2. Program will also do the error checking per each entry:a. Check if Asset Class data in file available in ANLA- ANLKL. If no record exists:i. generate error message Asset Class (ASSETCLASS) does not existii. Append the record number and error message to the log fileiii. Skip all proceeding error checkingb. Check Company Code (Single Value). If no record exists:i. generate error message Company Code (COMPANYCODE) does not existii. Append the record number and error message to the log fileiii. Skip all proceeding error checkingc. Check if Business Area data in file available in ANLZ- GSBER. If no record exists:i. generate error message Business Area (BUSINESSAREA) does not existii. Append the record number and error message to the log fileiii. Skip all proceeding error checkingd. Check if Cost Center data in file available in ANLZ-KOSTLV. If no record exists:i. generate error message Cost Center (COSTCENTER) does not existii. Append the record number and error message to the log fileiii. Skip all proceeding error checkinge. Check if WBS Element data in file available in ANLA-PS_PSP_PNR2. If no record exists:i. generate error message WBS Element (WBSELEMENT) does not existii. Append the record number and error message to the log fileiii. Skip all proceeding error checkingf. Check if Category1 data in file available in ANLA- ORD41. If no record exists:i. generate error message Category 1 (CATEGORY1) does not existii. Append the record number and error message to the log fileiii. Skip all proceeding error checkingg. Check if Category 2 data in file available in ANLA- ORD42. If no record exists:i. generate error message Category 2 (CATEGORY2) does not existii. Append the record number and error message to the log fileiii. Skip all proceeding error checkingh. Check if Category 3 data in file available in ANLA- ORD43. If no record exists:i. generate error message Category 3 (CATEGORY3) does not existii. Append the record number and error message to the log fileiii. Skip all proceeding error checking3. In error found during checking, end the program. Else, proceed to next step.4. Call BAPI BAPI_FIXEDASSET_CREATE1 with test-run activated.5. If BAPI test-run failed, log the error message from BAPI and end the program. Else, proceed to next step.6. Call BAPI BAPI_FIXEDASSET_CREATE1. (This time, test-run must not activated)a. If the BAPI fails:i. Get the error message generated by BAPI.ii. Append the error message with Asset Class, Asset Description and a message indicating that the error came from BAPI in log file.iii. Append 0 as record number and error message to the log file.iv. If there is any Asset Master Data already created by the program, get the asset number and delete all created asset master using AS06 with input: Asset Number and Company Codev. Break the loop, and put the log file at folder.b. If the BAPI success:i. Generate Asset Master Upload Success messageii. Append all generated asset number with the description to the success log file.

Pre-Processing/Post-Processing Dependencies:[Enter the prerequisite steps, i.e., any customized table that the program retrieved the data from. In that case, the user must provide valid data record in the table. Also state the post-processing steps, i.e. interface is sent to a dept via spool request.]

Data Inclusion/Exclusion: [Any data to be excluded/included by default]

Design Constraints:The file must follow asset upload template in spreadsheet. Only one asset upload template will be used.

Interface Report Layout: [Enter sample layout or provide a document containing the layout.]

Output Field Descriptions: [Please provide the fields and their descriptions in the record layout.]

Report Field NameField TypeField LengthSAP Table-Field Name/TCode-Screen No-Screen Field NameComments / Calculation / Formula / Descriptions

LegendField Type AAlpha onlyNNumericCAlphanumericR Radio buttonXCheck boxDDate

2a. Selection Criteria

Selection Criteria (Input Parameters) [Provide select options (ranges), parameters (single value options), whether the item is mandatory/optional and whether the input parameter should have a drop-down list with values for selection. Group the selection criteria in frames.]Screen Field NameSAP Table-Field NameField TypeField LengthRanges / Single valueMandatory / OptionalFrames and GroupsComments

Authorization Check[Provide the authorization check requirements, such as the field to check, authorization objects, field value, etc. This authorization check should be able to control that only user with the correct authorization can execute/view the data in this interface. ]

2b. Error Handling

Potential Errors:[Describe instances where errors may occur. This should include the extent to which the organization is responsible for error monitoring in correction versus users responsibilities. Full details on how operations will be notified are not required; however, state the business expectations for level of service provided.]

NoPossible ErrorsNotification Procedures

1Mandatory field not inputted View in Application View in log file

2Length of entry data over the limit View in Application View in log file

3Asset Class, Company Code, Business Area, Cost Center, or Category (1,2,3) are invalid View in Application View in log file

3a. Existing/Sample Interfaces or Related Transaction

Existing SAP Program Name: [Enter the name of the related SAP program]

Existing SAP Menu/Transaction:[Enter the related SAP Menu path and/or transaction]

Legacy Report Name:[Indicate document/sample cross reference or link design object into form.]

Legacy Report Number:[Indicate legacy number on document/sample cross reference.]

3b. Related Documents

No.Related DocumentsDescriptionAttachment

1.

2.

3c. Configuration Requirements: Company Code ConfigurationAsset Class ConfigurationEvaluation Group ConfigurationCost Center ConfigurationBusiness Area Configuration

[What configuration is required to support this process? Does this process require master data to be loaded? Do all configuration, master, and transactional data exist in the development system? ]

3d. Component Testing Requirements[List at a high level any requirements that exist to fully test this program.. Please enter functional conditions that are required for testing. Please include normal conditions and error handling conditions. This should include the following categories of test conditions:(1) Normal Processing: To test and display the report as the normal situation.(2) Exception Processing: To test and display the exception process (e.g.: zero amounts are not display, do not show deleted material, etc).(3) Error Processing: To test and display the error message (e.g.: invalid company code, invalid sales order number, etc).]

Test conditionExpected results

File contains incorrect data format (length and mandatory field) but also contains some correct data- Error message with record number is generated- No asset master data created

File contains invalid data (Asset Class, Company Code, Business Area, Cost Center, or Category 1,2,3) but also contains some correct data- Error message with record number is generated- No asset master data created

All format correct and all data valid- Successful message generated- Asset number and the details are appear on the successful log

Test Data: (Required)[Provide the test data that to perform the above test conditions]

3e. Performance Watch[Consider the following items:1. Online & time critical reports.2. Transaction volume.3. Interface result monitoring / monitoring tools]

APPENDIX A : Screen shots of process[Set of screen shots to clarify steps of process. For example if the report is a standard modification, then provide the screen shots of transaction]

File Name: Document14Page 6 of 13Status: DRAFTDate Printed: 19/11/2013Start

Upload Data to System

Program will Check Data Validity

Data Valid?

Program will Run BAPI to Create Asset Master Data

Y

Succeed?

Create Error Messages

N

N

User Prepare Data on spreadsheet

Generate Error Log File

Create Success Messages

Y

End

Generate Success Log File

User Run TCODE

AP350 FD E FIN EF005 - Asset Master Uploader v.0.1

Documents

Transcript of AP350 FD E FIN EF005 - Asset Master Uploader v.0.1