Hi can any prepare TS for the FS ?ITS URGENT

Question

1.0     Functional Spec Header
1.1     Business Requirement
The management structure for reporting is currently maintained in Hyperion by the Financial Analysis and Planning group.  This management structure is critical throughout Cessna for managing the business.  The interface is needed to download the management structure hierarchy from Hyperion and load to SAP as a cost center group.
1.2     Purpose/Objectives/Reason for Need
The purpose of this interface is to ensure the management structure in SAP remains in sync with the management structure in Hyperion.  This interface will eliminate the need for manual changes to both Hyperion and SAP and also reduces the chance for error to occur when both systems are updated.  This interface will save time when making changes to the management structure.
There is no record retention requirement for the management structure in Hyperion.
1.3     Assumptions
The management structure for reporting will managed by Financial Analysis and Planning and a process will be in place to coordinate changes to the structure.  This interface will be run automatically daily.
1.4     Alternatives
If the interface doesn’t exist, then changes to the management structure in Hyperion and SAP will have to be done separately and manually in both systems.  This will increase the chance of error that could result in the management structure being different in Hyperion and SAP causing confusion and unnecessary reconciliations.
1.5     Similar FRICE Item
None found
2.0     Security Requirements
2.1     User profiles allowed to use this development
N/A
It is not known at this time what role this transaction will reside.  Financial Analysis and Planning will be responsible for maintaining the management structure in Hyperion but Finance management has not decided what Finance group will be responsible for the upload into SAP.
2.2     Authorizations Included
Controlling Area = 1000
Access granted to project team.
There are standard transactions available to view and maintain cost center groups in SAP.  This ability to change groups will be restricted to a small group of people.  Many users will be able to display the structure and use it in reporting.
This is not ITAR sensitive data.
[Below the transaction level, what auth objects should this development be controlled by?  (plant, company code, etc.)]
3.0     Functional Requirements
3.1     Report/Form
3.1.1     Input
[Electronic picture(s) of selection screen and screen flow including success/error messages, icons, colors.]
3.1.2     Processing
[Electronic text and picture of processing steps, including if/case logic, authority checks and runtime issues.  A good way to show this is with flow charts or dummied up screen shots, including arrows and text to tell the story.]
3.1.3     Output
[Electronic picture of desired output, including sort, totals, hotspots, drill-down and other functionality like ALV.]
3.1.4     Example Data
[Demo of example data moving thru each step of processing, including usual, exception and error cases.]
3.2     Enhancement/Modification
3.2.1     Input/New Screens
[Electronic picture(s) of input and/or new screen(s) and screen flow including success/error messages, icons, colors.]
3.2.2     Processing
[Electronic text and picture of both current and requested processing steps, including if/case logic, authority checks and runtime issues.  A good way to show this is with flow charts or dummied up screen shots, including arrows and text to tell the story.]
3.2.3     Expected Results
[Data to be created/updated/deleted.]
3.2.4     Example Data
[Demo of example data moving thru each step of processing, including usual, exception and error cases.]
3.3     Interface/Conversion
3.3.1     Source
The source data for the management structure is maintained in Hyperion.  Currently, the management structure data is extracted from Hyperion using a XML file.  A XML file can be utilized to upload the structure into SAP as cost center groups.  John Shelton (phone [phone]) and Mike LaBarge (phone [phone]) are the SME’s for the Hyperion management structure.  The file will be stored in a format and location so the interface in SAP can run to check for the file.  If an updated file is found the interface will execute and update SAP.  If no file or an old file is found, the interface will not execute.
[Electronic text and picture of source system as it pertains to requested interface/conversion, including details.]
3.3.2     Translation
The entire management structure hierarchy should be loaded into SAP overwriting whatever previously existed in the cost center groups.  The cost center group should contain all active cost centers.  There are additional alias fields in Hyperion which can be populated with the cost center group name.  The field length for cost center groups in SAP is 10 and group name will always start with CM_. This can also be downloaded to excel in addition to the management level name with will become the cost center group description field in SAP.  Management levels 3, 4, and 5 in Hyperion will be loaded as cost center groups in SAP.  There is a relationship between each of these management levels: 
Hierarchy for Management Structure:
           Management Level 3
                     Management Level 4
                              Management Level 5
Level 3 is the top level. Level 4 is linked to 3 and level 5 is linked to 4. 
An email should be automatically generated when the update has run and should be sent to the assigned Finance group responsible for the SAP management structure regardless of error status.
[Electronic text and picture of translation steps, including if/case logic, authority checks and runtime issues.  A good way to show this is with flow charts or dummied up screen shots, including arrows and text to tell the story.]
3.3.3     Target
Daily the interface should check for a file to upload to SAP.  If no file or an existing file is found, the interface will stop processing.  If a new file is found the interface should execute and update the cost center group in SAP.  The cost center group name will not change (CM_MGTHIER).  The new file should overwrite the existing hierarchy in SAP.  This cost center group should contain all active cost centers in SAP and no cost center can appear more then once in the structure.  To validate this logic a completeness and ambiguity check should be completed after the management structure is loaded into SAP. 
The completeness check in SAP is a feature in the standard transaction that will check all the cost centers assigned to the group against the active cost centers in master data table in SAP, (Table CSKS, Field KOSTL).
The ambiguity check is a feature in the standard transaction that will check for duplicate records in the hierarchy.   This could be either the group name, or the cost center value.  It returns a report of the results and the user can manually adjust the cost center group to remove the ambiguity inconsistencies.  This program should be used when the interface loads a new management cost center group.  The hierarchy structure will need to be locked while the update is running.
The function module K_HIERARCHY_TABLES_READ in SAP maintains the parent / child relationships of cost center groups, sub-groups, and cost centers.  This functional module can be utilized when loading the hierarchy data from the Hyperion extract file. 
There are also a few BAPI’s available for loading the hierarchy;
BAPI_COSTCENTERGROUP_ADDNODE
BAPI_COSTCENTERGROUP_CREATE
BAPI_COSTCENTERGROUP_GETDETAIL
BAPI_COSTCENTERGROUP_GETLIST
The following IDOC’s  can also be used for loading the hierarchy;
IDOC_INPUT_COSTCENTERGROUP_ADD
IDOC_INPUT_COSTCENTERGROUP_CRE
The technical decision for how to load the hierarchy will come from the technical team.  The Functional Modules, BAPI’s, and IDOC’s mentioned above are for reference and can evaluated during the development of the technical spec.
Example of SAP Cost Center Group Hierarchy:
Ambiguity and Completeness Check:
Transaction code KSH1.  Enter cost center group name in field and follow menu path: extras> check and help functions
[Electronic text and picture of target system as it pertains to requested interface/conversion, including details.]
3.3.4     Example Data
[Demo of example data moving thru each step of processing, including usual, exception and error cases.]
3.3.5     Error Handling
The detail log should state the following:
     Number of records converted successfully
     Number of records sent to the error report
     Details of the errors – what caused the errors?
If the completion check finds missing cost centers, or the ambiguity check finds duplicate records and an email should be sent to a group defined by Finance for the given error conditions.  These issues can be researched and corrected by a user with access to create/maintain cost center groups.
If there is an error in processing the file (i.e. IDOC error), the interface should stop and return an error message to be researched by a technical resource who monitors interface activity.
There are no required fields or conditional inputs when creating cost center groups.  If the file is formatted correctly the interface should process without incident.  Errors that occur because of duplicate or missing records can be addressed through ambiguity and completeness checks and be corrected by a user with access to the standard transaction.
An email should be automatically generated when the update has run and should be sent to the assigned Finance group responsible for the SAP management structure regardless of error status.
[FMEA (Failure Modes and Effects Analysis) on possible run conditions and how to address them.]
4.0     Electronic Attachments/Documentation
[Required for Functional: 1) Unit Test Plan, 2) Related BPPs or Instructional Pertinent Functional Info]
Document Name     Location
Field mapping file     Hierarchy data is not maintained in a table in SAP.  The functional module K_HIERARCHY_TABLES_READ maintains the relationships of the group including the hierarchy level and parent/child relationship.
Unit Test Plan     There are approximately 1,000 active cost centers at Cessna.   The Unit Test plan can send a sample of the data, (one or two nodes and associated cost centers).  The full file is available and can used for a more robust unit test. 
Sample Data                  
FIN0116 - Hyperion to SAP Management Structure.vsd     Cessna3\cessnaim\Prod\Projects\Specifications\D2 Interface_Summaries\
5.0     Technical  Requirements
5.1     Report/Form
5.1.1     Technical Objects
[Tables, APIs, structures, EDI segments, data elements, domains, indexes, function Modules]
5.1.2     Technical Strategy
[Outline processing steps: include 5.1.2 items with fields, selection/join conditions, perf, err handling, control]
5.1.3     Production Support
[Batch: electronic job flow with technical names]
5.2     Enhancement/Modification
5.2.1     Technical Objects
[Tables, APIs, structures, EDI segments, data elements, domains, indexes, function Modules, user exits]
5.2.2     Technical Strategy
[Outline processing steps: include 5.1.2 items with fields, selection/join conditions, perf, err handling, control]
5.2.3     Production Support
[Only include info not already found in spec]
5.3     Interface/Conversion
5.3.1     Source/Middleware/Target (WBI/Middleware Technical Implementation Details)
WBI will call the BAPI (RFC function module) from middle ware and populates the data into BAPI.
          Interface Overview
               This section describes the detailed interface design with all the required information regarding the source 
               system, WBI Components and the destination application of the FIN0116 Hyperion Mgmt Structure to SAP
               The FIN0116 Hyperion Mgmt Structure to SAP integrates management structure data from the source
               system (Hyperion) to the target system (SAP) in near real-time. This section describes detailed information
               regarding the WBI Components and its Connectivity.
          Interface Assumptions
1.     Hyperion mgmt structure XML file will be placed in the directory where WBI have access to read and archive.
2.     WBI (Middleware) is going to have FTP get access and FTP service account to the Hyperion File System.
3.     All Hyperion XML files placed in the directory are going to have unique file name (Ex: HyperionFile_MMDDYYYY.xml)
        Interface E2E Flow
Step 1     
Hyperion mgmt structure XML data file will be placed in E:\Hyperion\SAP\Event directory on Hyperion Server..
Step 2     
The CES_FIN01_JText_POLConnector will be polling on the E:\Hyperion\SAP\Event directory, which resides on Hyperion file system; whenever there is a new file in the directory, the connector will process that file to WBI Server and Archive file to E:\Hyperion\SAP\Archive directory.
Step 3     
The CES_FIN01_JText_POLConnector will send the XML document to Interchange server (WBI).
Step 4     
Interchange Server (WBI) will process the XML data and map the Hyperion Mgmt data to SAP BAPI. WBI will send the SAP BAPI formatted mgmt structure data to ASD_CES_SAPFIN1_UPRConnector Agent.
Step 5     
The ASD_CES_SAPFIN1_UPRConnector Agent will call ZC_BAPI_COSTCENTERGRP_MANGMNT and pass mgmt data to it.
Step 6     
Interchange server (WBI) will receive a response from SAP application and the response can be either a success or a failure/Error.
Step 7     
If the transaction is success, do nothing end success the process.
Step 8     
If the transaction is failed in SAP, SAP will send the return object to WBI server.
If error information received from SAP via return object or the transaction is failed in WBI (Middleware), WBI is going to send an error email notification to business email distribution list.
    WBI Components
     Please refer the attached interface spread sheet.
    Interface Mapping Document
   Please refer section 4.0 for mapping document.
     Error Handling and Logging
          Successful Transactions:-
      Once WBI receives a success return code from SAP, WBI will end the transaction as End Success.
System Failure Transactions:-
Step 1     Any ICS component is down on production server.
Business Process/Data Failure Transactions:-
Step 1     Error while executing Collaboration (Business Logic) or Mapping of Lawson data to SAP format
WBI will send an Email Notification to Business Email Distribution List.
Step 2     WBI Received a TYPE = W or E from SAP in return structure.
SAP system should be able to raise an error and send an email to Business Email Distribution List
SAP SAMPLE RETURN OBJECT STRUCTURE To WBI:-
sap_return = 1
TYPE = S
ID = MM
NUMBER = 90104
MESSAGE = The Cost Center Group 90104 has been successfully created
LOG_NO = CxBlank
LOG_MSG_NO = 000000
MESSAGE_V1 =
MESSAGE_V2 = CxBlank
MESSAGE_V3 = CxBlank
MESSAGE_V4 = CxBlank
PARAMETER = CxBlank
ROW = 0
FIELD = CxBlank
SYSTEM = SD6CLINT223
ObjectEventId = CxIgnore
From the return object for the field “TYPE” the following are the possible values that SAP is returning.
Type     Meaning
S     Success
I     Information
W     Warning
E     Error
For all Warning or Error messages received from SAP, WBI needs to send an Email notification to the Email distribution List mentioned in Section bellow.
Email Distribution Information
EMAIL ADDRESS     Successful Transactions     System Failure Transactions     Business Process/Data Failure Transactions
  WBI Performance Considerations
    Collaboration General Properties
Property Name     Value     Notes
Maximum number of concurrent events     1     The GBO size is going be huge for this collaboration, so we want it to process 1 at a time, to minimize the use of system resources.
Recovery Mode     Deferred     By setting the Recovery Mode to ‘Deferred’, it will increase the ICS performance and reduce the ICS startup time. For more questions, please refer WBI documentation.
Max Event Capacity     1     We don’t want this collaboration to process more than 1 event at any given time, so we set this value to 1.
CES_FIN01_JText_POL Connector Properties
Property Name     Value     Notes
AgentConnections     1     It is a system default value, and for daily batch process interfaces, don’t need more than 1 agent connections
ConcurrentEventTriggeredFlows     4     As of now this connector will be used by 4 interfaces.
ControllerEventSequencing     true     This is a default and not much of a use for this interface
Max Event Capacity     8     To give buffer to the connector, we just doubled the ConcurrentEventTriggerFlows.
Poll Frequency     10000     As of now, we defined this parameter to poll every 10 sec, once we move the interface to production we can change the Poll Frequency to 10 min or 30 min depends on the requirement.
Poll Quantity     3     Though we define Poll Quantity to 3, we are not expecting more than 1 at anytime.
JvmMinHeapSize     1m     System Default, need to be tuned based on interface performance.
JvmMaxHeapSize     256m     System Default, need to be tuned based on interface performance.
JvmMaxNativeStackSize     128k     System Default, need to be tuned based on interface performance.
ASD_CES SAPFIN1UPR Connector Properties
Property Name     Value     Notes
AgentConnections     1     It is a system default value, and for daily batch process interfaces, don’t need more than 1 agent connections
ControllerStoreAndForwardMode     true     By setting this value to true, if the SAP connector agent to SAP is down, then the transaction will wait until the agent is restored and once it restored, connector will successfully complete the transaction
JvmMinHeapSize     1m     System Default, need to be tuned based on interface performance.
JvmMaxHeapSize     256m     System Default, need to be tuned based on interface performance.
JvmMaxNativeStackSize     128k     System Default, need to be tuned based on interface performance.
5.3.2     Processing/Translation (SAP Technical Details)
[Outline processing steps: include 5.3.2 items with fields, selection/join conditions, perf, err handling, control]
Assumptions:
1.     All data that is received by RFC Function Module is pre-converted and ready to upload to SAP.
2.     A set of records will be populated to RFC function module table.
3.     The Main Cost center group name will be ‘CM_MGTHIER’ and it will be a constant.
4.     Cost center group names will be provided along with cost center groups.
5.     Controlling Area is assumed to be '1000'.
6.     If an invalid cost center is found, Cost center group will not be created or modified and the error message will be returned along with the invalid cost center.
Process Flow:
1.     Create new RFC function module ‘ZC_BAPI_COSTCENTERGRP_MANGMNT’ in SE37 transaction with importing parameters includes a table with all the fields in the input file structure.
2.     Source code written in this function module to create cost center groups in ‘KSH1’ transaction using the BAPI ‘BAPI_COSTCENTERGROUP_CREATE’.  
3.     If Cost center repeats error message will be displayed through RETURN parameter.
4.     Errors generated while cost center group creation, will be displayed as the Return table in the output of the RFC function module.
Program Structure and processing:
1.     Create a new  RFC function module ‘ZC_COSTCENTERGRP_MANGMNT’ with below parameters
Parameters     Type     Description
Exporting          
RETURN     BAPIRET2     Return Parameter
Tables          
CCGRP     ZCSF_CCGRP     Cost Center Groups
2.     Pass the contents of table CCGRP into another internal table IT_CCGRP where group names come first.
3.     Sort internal table IT_CCGRP by MGMT3_NAM, MGMT4_NAM and MGMT5_NAM fields.
4.     Loop at table IT_CCGRP into a work area WA_CCGRP.
     If Cost center is not initial, Select KOSTL from CSKS table into a variable V_KOSTL where KOSTL = WA_CCGRP-CCID.
     If SY-SUBRC is equal to zero, then pass the following fields to the BAPI structure
WA_ HIERARCHYVALUES-VALFROM = WA_CCGRP-CCID.
WA_ HIERARCHYVALUES-VALTO      = WA_CCGRP-CCID.
Append WA_ HIERARCHYVALUES to IT_ HIERARCHYVALUES.
     Else, populate an error message saying ' Cost center groups contain invalid Cost Centers' into RETURN table. And exit from the loop.
     At FIRST,  do the following,
a.     Pass the following fields to create Cost center group ‘Cessna Management structure’ initially.
WA_HIERARCHYNODES-GROUPNAME = ‘CM_MGTHIER’
WA_HIERARCHYNODES- HIERLEVEL = ‘0’
WA_HIERARCHYNODES- VALCOUNT = ‘0’
WA_HIERARCHYNODES- DESCRIPT = ‘Cessna Management Structure’
Append WA_HIERARCHYNODES to IT_HIERARCHYNODES.
     At new of MGMT3_NAM_NAM field,  do the following,
a.     Pass the following fields, to create Management level 3 group
WA_HIERARCHYNODES-GROUPNAME = WA_CCGRP-MGMT3_NAM
WA_HIERARCHYNODES- HIERLEVEL = ‘1’
WA_HIERARCHYNODES- VALCOUNT = ‘0’
WA_HIERARCHYNODES- DESCRIPT = WA_CCGRP-MGMT3_DES
Append WA_HIERARCHYNODES to IT_HIERARCHYNODES.
     At new of MGMT4_NAM field,  do the following,
a.     Pass the following fields, to create Management level 4 group
WA_HIERARCHYNODES-GROUPNAME = WA_CCGRP-MGMT4_NAM
WA_HIERARCHYNODES- HIERLEVEL = ‘2’
WA_HIERARCHYNODES- VALCOUNT = ‘0’
WA_HIERARCHYNODES- DESCRIPT = WA_CCGRP-MGMT4_DES
Append WA_HIERARCHYNODES to IT_HIERARCHYNODES.
     ADD V_VALCOUNT = V_VALCOUNT + 1.
     At end of MGMT5_NAM field,  do the following,
a.     Pass the following fields, to create Management level 5 group
WA_HIERARCHYNODES-GROUPNAME = WA_CCGRP-MGMT4_NAM
WA_HIERARCHYNODES- HIERLEVEL = ‘3’.
WA_HIERARCHYNODES- VALCOUNT = V_VALCOUNT.
WA_HIERARCHYNODES- DESCRIPT = WA_CCGRP-MGMT5_DES
Append WA_HIERARCHYNODES to IT_HIERARCHYNODES.
     At LAST,  do the following,
a.     Call BAPI ' BAPI_COSTCENTERGROUP_CREATE' by passing the below parameters.
CALL FUNCTION 'BAPI_COSTCENTERGROUP_CREATE'
  EXPORTING
    CONTROLLINGAREAIMP       = '1000'
  IMPORTING
     GROUPNAME                        = GROUPNAME
     RETURN                                 = RETURN
  TABLES
    HIERARCHYNODES           = IT_HIERARCHYNODES
    HIERARCHYVALUES          = IT_HIERARCHYVALUES.
5.3.3     Technical Objects
[Tables, APIs, structures, EDI segments, data elements, domains, indexes, function Modules, user exits, BAPIs]
Function Modules:
‘ZC_COSTCENTERGRP_MANGMNT'
‘BAPI_COSTCENTERGROUP_CREATE’
‘BAPI_TRANSACTION_COMMIT’
Tables: EKPO, CSKS     
Structure: ‘ZCSF_CCGRP’
FIELD NAME     DATA ELEMENT     DOMAIN     DATA TYPE     LENGTH     FIELD  DESCRIPTION
MGMT3_NAM     ZCMGMT_N     GRPNAME     CHAR     15     Management level 3 Name
MGMT3_DES     ZCMGMT_D     TEXT40     CHAR     40     Management level 3 Description
MGMT4_NAM     ZCMGMT_N     GRPNAME     CHAR     15     Management level 4 Name
MGMT4_DES     ZCMGMT_D     TEXT40     CHAR     40     Management level 4  Description
MGMT5_NAM     ZCMGMT_N     GRPNAME     CHAR     15     Management level 5 Name
MGMT5_DES     ZCMGMT_D     TEXT40     CHAR     40     Management level 5  Description
CCID     KOSTL     KOSTL     CHAR     10     Cost Center
CCDES     KLTXT     TEXT40     CHAR     40     Cost center Description
5.3.4     Technical Overview and Strategy
[Performance, error handling, control]
Error Handling:
Errors generated will be displayed as the Return table in the output of the RFC function module, when
1.     Cost center in invalid.
2.     Cost center group name repeats.
3.     Cost Center repeats.
5.3.5     Production Support
[Describe scenarios in which the interface components should/should not run. (Source/Middleware/Target systems down, etc.)]
6.0     Technical Development Objects
[Include development objects that would be required in order for the business to be able to provide production support.]
Package/Dev Class: ZCK_INT
RFC Function Module Name: ZC_COSTCENTERGRP_MANGMNT
Function Group Name: ZCFMC_COSTCENTERGRP_MANGMNT
Structure: ZCSF_CCGRP

Answer 1

SDN is the place to discuss technical problems..
Please avoid such weird post.
G@urav.