ENHANCEMENT TECHNICAL SPECIFICATION

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

Author Pankaj Kumar

Date 10 November 2016
 Enhancement Technical
Specification

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

Name/Signature Title Review date Review check list

Babu Badvelu ABAP Consultant 10 Nov 2016 RFC_85890_TS_Revi

ew_Check_List.xls

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 ID: I157

Development Title: Production Receipts To APS Datamart
IS Business Transformation
Requesting Team/Workstream FTD

Development Items Technical Identification / Development Consolidation

Development Item Type Development Item Name and Description Category(Cust System / Platform Contacts
om, Standard,
New)

INTERFACE ZMIMFI157_PROD_RECEIPTS_TO_APS Custom DR1/QR1/PR1 Pankaj Kumar

Dependencies / Touch Points

Performance Considerations

Functional Requirement

Enhancement to the program ZMIMFI157_PROD_RECEIPTS_TO_APS.

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.

Interface Technical Design

TS_GIS_PP_I157_RFC_85890_Production_Receipts To APS-Datamart
Printed: 4/25/2017
Page 4 of 15
 Enhancement Technical
Specification

Program Functionality Description, Pseudocode

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.

Field Field Type SELECT- Default

name OPTIONS/PARAMETERS
Date Range Sy-datum Select-options

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

Also inside the interface ZMIMFI157_PROD_RECEIPTS_TO_APS we are adding a new segment

as END OF FILE. To achieve this, new record will be added to the final internal table with content as
EOF.

Ls_mseg_data_char = EOF
Append ls_mseg_data_char to gt_mseg_data_char

a. Considerations/ Instructions

b. General Information

Transaction Codes used:

List all transactions used in your program
SAP Application SAP PP
List SAP module involved Ex. SD Pricing

File Name(s): Size of Record to be used: Expected record volume:

Provide the path of file location Identify the size of record

Authorization Objects:

TS_GIS_PP_I157_RFC_85890_Production_Receipts To APS-Datamart
Printed: 4/25/2017
Page 7 of 15
 Enhancement Technical
Specification

Provide the authorization objects, fields and

values used in this program
Other Security
Describe security issues for data transfer, file
access, reprocessing, etc.

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 Release Version

IDOC Extension

User Exit

Responsible Party for Error Processing

Outbound Attributes:
Message Type
Process Code
Output Mode

IDOC Release Version

IDOC Extension
User Exit
Responsible Party for Error Processing

IDOC Type ZGENERICIDOC

IDOC Extension Type
Message Type ZAPSRECEIPTS
SAP Program/Function Module ZMIMFI157_PROD_RECEIPTS_TO_APS
Name
SAP Interface Program/Function
Module Name
User Exit for IDOC enhancements

TS_GIS_PP_I157_RFC_85890_Production_Receipts To APS-Datamart
Printed: 4/25/2017
Page 8 of 15
 Enhancement Technical
Specification

3 General Mapping Information

Only required if different from Functional Spec mapping.

Field Description Type Length Data Source

name
{e.g. DBMS field name}

a. File Formats

b. Source System to BDC (Inbound Interfaces) / Custom Transactions /

Custom Screens

SAP Screen Name & Number: ________________/_____________

SAP Table SAP Field SAP Field Description SAP SAP Field Source System Source Field Source Field Comments / Data Transformation
Name Name Field Length / Table / File Name Description Requirements / Data Validation
Type Name Requirements

c. Source System to BAPI / Function Module / Method

BAPI / Function Module/Method/Interface: ________________/_____________
SAP Table SAP Field SAP Field Description SAP SAP Field Source System Source Field Source Field Comments / Data Transformation
Name Name Field Length / Table / File Name Description Requirements / Data Validation
Type Name Requirements

d. Source Target Mapping (Inbound Interfaces / Outbound Interfaces /

XML)
Target Table / Target Field Target Field Target Target Source System Source Field Source Field Comments / Data Transformation
File Name Name Description Field Field / Table / File Name Description Requirements / Data Validation
Type Length Name Requirements

e. IDOC / BDOC / ALE Messaging Attachments / XML

f. IDOC / BDOC / ALE Mapping (Inbound / Outbound EDI Interfaces)

IDOC IDOC Field Qualifier Literal X12 Field X12 Static Field X12 Field Comments / Data Transformation
Segment Qualifier Description Description Requirements / Data Validation
Requirements

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.1 Audit Trail

6.2 Error Handling / Correction and Recovery

6.3 Notifications

6.4 Reconciliation

6.5 Data Maintenance Requirements

6.6 Objects and Transport request.

Work Bench Transport Request

Customizing Transport Request
Messages
Program ZMIMFI157_PROD_RECEIPTS_TO_APS
QA Check List

TS_GIS_PP_I157_RFC_85890_Production_Receipts To APS-Datamart
Printed: 4/25/2017
Page 11 of 15
 Interface Technical
Specification

6 Security / Authorization Requirements

Authorization Check ( ) Yes ( ) No
Requested From
Functional Team
If yes, which Auth Group? ______________________________

TS_GIS_FI_E101_RFC_85910_Clearing_Disputecases not to overwrite the case cust ref

Printed: 4/25/2017
Page 12 of 15
 Interface Technical
Specification

7 Technical Unit Testing

List any test cases for
- Base Case Testing
- Boundary Testing
- Exception Testing

a. Data Requirements

TS_GIS_FI_E101_RFC_85910_Clearing_Disputecases not to overwrite the case cust ref

Printed: 4/25/2017
Page 13 of 15
 Interface Technical
Specification

TS_GIS_FI_E101_RFC_85910_Clearing_Disputecases not to overwrite the case cust ref

Printed: 4/25/2017
Page 14 of 15
 Interface Technical
Specification

Business Requirement Tested Data Object Required for Unit Testing Type (Master data, Transaction Data, Description of Testing Dependency to Business Requirement
Historical Data)

b. Unit Test Plan / Expected Results / Actual Results

Step Action / Input Data Expected Results Actual Results / Comments Pass/ Action Taken if Step Fails Defect #
Fail

TS_GIS_FI_E101_RFC_85910_Clearing_Disputecases not to overwrite the case cust ref

Printed: 4/25/2017
Page 15 of 15