Beruflich Dokumente
Kultur Dokumente
RFC-85890
Clearing Dispute Cases
Document Name: TS_GIS_PP_I157_RFC_85890_Production_Receipts To APS-
Datamart
Development ID: I157
Development Title: Production Receipts To APS Datamart
IS Business Transformation ERP Phase 1
Initiative:
Requesting Team/Workstream FTD
TABLE OF CONTENTS
Revision History 3
Approval 3
Distributed 3
Reviewers
Approvals 3
1 General Information 3
1.1 Development Items Technical Identification / Development Consolidation 3
1.2 Dependencies / Touch Points 3
1.3 Performance Considerations 3
1.4 Assumptions
2 Interface Technical Design 3
2.1 Program Functionality Description, Flow Chart / Pseudocode 3
2.2 Inputs 3
2.3 Considerations/ Instructions 3
2.4 General Information 3
2.5 ALE Information 3
2.5.1 ALE Scenario Review 3
2.5.2 ALE Attributes 3
2.6 .
3 General Mapping Information 3
3.1 File Formats 3
3.2 Source System to BDC (Inbound Interfaces) / Custom Transactions / Custom Screens 3
3.3 Source System to BAPI / Function Module / Method 3
3.4 Source Target Mapping (Inbound Interfaces / Outbound Interfaces / XML) 3
3.5 IDOC / BDOC / ALE Messaging Attachments / XML 3
3.6 IDOC / BDOC / ALE Mapping (Inbound / Outbound EDI Interfaces) 3
4 Job Creation/Scheduling 3
5 Application Controls 3
5.1 Audit Trail 3
5.2 Error Handling / Correction and Recovery 3
5.3 Notifications 3
5.4 Reconciliation 3
5.5 Data Maintenance Requirements 3
6 Security / Authorization Requirements 3
7 Technical Unit Testing 3
7.1 Data Requirements 3
7.2 Unit Test Plan / Expected Results / Actual Results 3
TS_GIS_PP_I157_RFC_85890_Production_Receipts To APS-Datamart
Printed: 4/25/2017
Page 2 of 15
Enhancement Technical
Specification
Revision History
Revision Revision Date Summary of Changes Updated
1.0 10 November 2016 Initial version (RFC-85890) Pankaj Kumar
Approval
Distributed
Name/Signature Title
Pankaj Kumar ABAP Consultant
Babu Badvelu ABAP Consultant
Peer Reviewer
Approvals
Name/Signature Title
Sudhir Prusty Track Lead, AT
Annitre Edision Director, Application Operations, Service Delivery
TS_GIS_PP_I157_RFC_85890_Production_Receipts To APS-Datamart
Printed: 4/25/2017
Page 3 of 15
Enhancement Technical
Specification
1 General Information
Document Type: Technical Specification
Document Name:
TS_GIS_PP_I157_RFC_85890_Production_Receipts To APS-Datamart
Development Item Type Development Item Name and Description Category(Cust System / Platform Contacts
om, Standard,
New)
Performance Considerations
Functional Requirement
IDocs with large number of segments are getting split in to multiple IDocs. Business doesnt want
IDoc to get split even in case of processing of large number of segments. Also, they want start and
end date in selection screen.They require End of file segment to be added once all the records have
been processed from SAP end
1. To remove the Split logic in the program to avoid any split of IDoc.
2. To include Start date and End date fields in the input selection screen.
3. To add the end of file segment in the program. An End of File (EOF) segment will be added
to the IDOC ZAPSRECEIPTS to indicate all records have been processed from SAP. To
make sure MQ not to deliver the file to DataMart until they receive the EOF segment in the
IDoc.
TS_GIS_PP_I157_RFC_85890_Production_Receipts To APS-Datamart
Printed: 4/25/2017
Page 4 of 15
Enhancement Technical
Specification
RFC 85890
In the selection screen, we will be adding 2 new selection criteria i.e. Start Date and End Date. This
will be used in case user wants to run the report for a particular date range. We will be changing the
logic and populating date range for which the user wants to run the report .i.e cpudt IN lr_date_range.
By default the program will run for last run date time that it will get from zmt_last_run table to the
current date. We are adding extra functionality of date in selection screen so that in case of
troubleshoot user can provide date range for which it wants the report to be executed and can find the
root cause. Currently such option is not available and user faces difficulty in troubleshooting.
Inputs
Adding below new field on selection-screen.
TS_GIS_PP_I157_RFC_85890_Production_Receipts To APS-Datamart
Printed: 4/25/2017
Page 5 of 15
Enhancement Technical
Specification
Inside the function module Z_GENERICIDOC_CREATE there is logic to split IDocs in case
the number of segments reaches the limit specified.
Since this FM is being used be several programs for IDoc creation. So instead of disturbing the
function module we are copying this function module in a new FM and removing the logic of split
from there.
TS_GIS_PP_I157_RFC_85890_Production_Receipts To APS-Datamart
Printed: 4/25/2017
Page 6 of 15
Enhancement Technical
Specification
Ls_mseg_data_char = EOF
Append ls_mseg_data_char to gt_mseg_data_char
a. Considerations/ Instructions
b. General Information
Authorization Objects:
TS_GIS_PP_I157_RFC_85890_Production_Receipts To APS-Datamart
Printed: 4/25/2017
Page 7 of 15
Enhancement Technical
Specification
Note on Data Mapping: The layout of the legacy file and the mapping to SAP R/3 fields
is in the Functional Specification.
Inbound Attributes:
Message Type
Process Code
IDOC Extension
User Exit
Outbound Attributes:
Message Type
Process Code
Output Mode
IDOC Extension
User Exit
Responsible Party for Error Processing
TS_GIS_PP_I157_RFC_85890_Production_Receipts To APS-Datamart
Printed: 4/25/2017
Page 8 of 15
Enhancement Technical
Specification
a. File Formats
TS_GIS_PP_I157_RFC_85890_Production_Receipts To APS-Datamart
Printed: 4/25/2017
Page 9 of 15
Enhancement Technical
Specification
4 Job Creation/Scheduling
Name of Job
SAP Job Profile Batch
Real-Time
Frequency Every ___ Minutes
Every ___ Hours
Daily
Weekly
Monthly
Other
Can this job run during Yes (Without impacting the SAP system response)
peak hours? No
Please give a brief For example: this job will schedule the monthly run for MRP
description of the job's
function
On which client will the job
execute
What is the estimated
elapsed runtime of the job?
What is the earliest start
time of the job?
Does the job have a Yes: ________________________
deadline? No
Does the job have a Yes: ________________________
predecessor? No
Does the job have a Yes: ________________________
successor? No
ABAP program(s) to be List program names and variants
included in the job:
Does the job use an external Yes: (file/directory )
file as input? No
Does the job use an external Yes: (file/directory)
file as output? No
If the job uses an external Yes:
file as input or output, are What are they?
there system requirements
No
of the operating system?
Expected Output
What is the printer/spooler
for the output?
Sequencing requirements: Describe any job sequencing requirements, for example:
Run job Job-Name1 before this job and after Job-Name4
TS_GIS_PP_I157_RFC_85890_Production_Receipts To APS-Datamart
Printed: 4/25/2017
Page 10 of 15
Enhancement Technical
Specification
5 Application Controls
Detail any programming, error handling and logging standards, which will be utilized in
the development
6.3 Notifications
6.4 Reconciliation
TS_GIS_PP_I157_RFC_85890_Production_Receipts To APS-Datamart
Printed: 4/25/2017
Page 11 of 15
Interface Technical
Specification
a. Data Requirements
Business Requirement Tested Data Object Required for Unit Testing Type (Master data, Transaction Data, Description of Testing Dependency to Business Requirement
Historical Data)
Step Action / Input Data Expected Results Actual Results / Comments Pass/ Action Taken if Step Fails Defect #
Fail