MASAR - TS - ONG - REP000028 - Transactions Summary Report - V5.0

Project: Masar
Technical Specification (TS)
ONG
Work Stream
REP000028
RICEFW Number
MASAR_TS_ONG _REP000028_
Insert Tile of Spec Transactions Summary Report _V5.0
14/07/2023
Creation Date
MASAR_TS_ONG _REP000028_ Transactions Summary Report _V5.0

Table of contents
Development Summary (M) – Mandatory at High Level..............................................................................4

1. Scope Summary (M)............................................................................................................................5
1.1 Development Summary (M) - Mandatory at High Level.............................................................5
1.2 Development Objects per System (M – If applicable)................................................................5
1.3 Dependency on Other Development or Interface (M – if applicable)........................................5
1.4 Transport Information................................................................................................................5
2. Development Scope.............................................................................................................................6
2.1 Generic Solution Details (M – where applicable).......................................................................6
2.1.1 Authorization (M – for all custom objects)........................................................................6
2.1.2 Message Class and Messages (M – if applicable)...............................................................6
2.1.3 Selection Screen (M – if you are adding/changing existing screens).................................6
2.1.4 Output Layout Details / Sample Formats (M – where applicable).....................................6
2.1.5 Technical Design (M)..........................................................................................................6
2.1.6 Run Mode (M)....................................................................................................................7
2.1.7 Error/Exceptions Handling (M)..........................................................................................7
2.1.8 BADI...................................................................................................................................7
2.1.9 Customer-Exits (CMOD).....................................................................................................8
2.1.10 Enhancement spots...........................................................................................................9
2.1.11 User-Exit Routines.............................................................................................................9
2.1.12 Copy Routines....................................................................................................................9
2.1.13 Function Module / RFC / BAPI (M – where applicable)....................................................10
2.1.14 SAP PI – ABAP Proxy Development (M – if applicable)....................................................11
2.1.15 SAP CPI Development (if applicable)................................................................................11
2.1.16 IDOC Development..........................................................................................................12
2.1.16.1 General....................................................................................................................12
2.1.16.2 IDoc Customizing.....................................................................................................12
2.1.16.3 Extension.................................................................................................................13
2.1.16.4 IDoc Type.................................................................................................................13
2.1.16.5 Message Type..........................................................................................................13

2.1.16.6 Logical System.........................................................................................................13
2.1.16.7 Process Code...........................................................................................................13
2.1.16.8 Distribution Model..................................................................................................14
2.1.16.9 File Port...................................................................................................................14
2.1.16.10 XML File port...........................................................................................................14
2.1.16.11 XML HTTP................................................................................................................14
2.1.16.12 Partner profile.........................................................................................................15
2.1.16.13 Inbound/outbound Parameters...............................................................................15
2.1.16.14 Message Control.....................................................................................................15
2.1.17 Bespoke Table ( M – if applicable)...................................................................................16
2.1.17.1 Structures / Table Types..........................................................................................17
2.1.17.2 Data Elements.........................................................................................................17
2.1.17.3 Domain....................................................................................................................17
2.1.17.4 Transaction (for table maintenance).......................................................................17
2.1.18 Search helps.....................................................................................................................18
2.1.19 Lock Objects.....................................................................................................................18
2.1.20 Number Range Objects....................................................................................................18
2.1.21 Class.................................................................................................................................19
3 Unit Testing…………………………………………………………………………………………………...........................27
3.1 .1 Input Data…………………………………………………………………………………………………...........................27
3.1.2 Test Scenario………………………………………………………………………………………………...........................27
3.1.3 Positive unit test………………………………………………………………………………………………......................28
3.1.4 Negative Unit Test………………………………………………………………………………………...........................28

Development Summary (M) – Mandatory at High Level
Development Details:
Development ID: REP000028 Release: Stage2
Title:
Transactions Summary Report
Contact Parties:
Technical Consultant: Sainath Functional Consultant: Tejendra
Contact Tel No: 8892693068 Contact Tel No:
[email protected] [email protected]
Email Address: om Email Address: om
Document Status:
Document Status : Final
Comments :
Development Complexity:
Development
Complexity: Medium
Change History
Version Date Author Description of Change
1.0 28/01/2022 Sainath Initial version
2.0 13/09/2022 Suresh / Kumar Changes for INC' WC00093
3.0 27/09/2022 Saurav Changes for INC' 95490
4.0 21/11/2022 Saurav Changes for INC'118232
5.0 14/07/2023 Varsha Changes for INC'364045

1. Scope Summary (M)
1.1 Development Summary (M) - Mandatory at High Level

As per business requirement a custom report will be developed to analyze the Aviation Meter Reconciliation
And display the
Ref. Document
Aspect Trade ID
Aspect Parcel ID
Operation Date
Activity Type
Activity Type Description
Product
Product Grade
Blending
Line Flush
JIFF Transfers
Inter Tank Transfer
Shipment ID
Load/Discharge Plant Description
Source Tank Description
Destination Tank Description
Destination Tank Description
Following input fields will be used to generate the output.
Operation Period
Nomination Key
Company Code
Material
Plant

New report developed based on the business requirement, selection screen build
as per the above inputs and business
Selection screen of the report:
1.2 Development Objects per System (M – If applicable)

S.No System Package Development Description New, Change
or Delete
Object
1 D4A ZENOC_OGP ZDOGPR_TRANSACTION_DETAILS Import, Export, New

Blending & Transfer
report.
1.3 Dependency on Other Development or Interface (M – if applicable)

NA
Item # Pre Req or Post Req? Dependency type, spec, code, Comments
unit or link test

1.4 Transport Information
No System Transport Number
1 D4A D4AK902891
D4AK922531
2 D4A D4AK943631
3 D4A D4AK948496
4 D4A D4AK949951
5 D4A D4AK957507

2. Development Scope
2.1 Generic Solution Details (M – where applicable)

2.1.1 Authorization (M – for all custom objects)
S. No. Authorization/Restriction Object
1 Transaction Code ZOGP03
2 Program ZDOGPR_TRANSACTION_DETAILS
Program Authorization Group
3 Table / t001w
Table Authorization Group
4 Custom Authorization Group NA
5 File Access NA
File Name / Program
2.1.2 Message Class and Messages (M – if applicable)

NA
S.No Message Class Message Short Text Long Text

Number
2.1.3 Selection Screen (M – if you are adding/changing existing screens)
2.1.4 Output Layout Details / Sample Formats (M – where applicable)

2.1.5 Technical Design (M)
New report developed based on the business requirement, selection screen build
as per the above inputs and business logic follow as below
1. Based on the selection screen inputs, get all the data from zogs_i6_data and display meter
reading in appropriate status bucket.
2. Select ticket data for given period from oij_el_ticket into table @data(lt_ticket).
3. Select data from oij_el_tkt_i_o2 into table @data(lt_tkt_i_o2)
4. Select for product grade name makt into table @data(lt_makt).
5. Select for product from mara into table @data(lt_mara).
6. Select for product name from t023t into table @data(lt_t023t).
7. Select for location from oifspbl into table @data(lt_location).
8. Select data from matdoc into table @data(lt_matdoc2).
9. Discharge location select data from toij_el_mvscen into table @data(lt_mvscen).
10. get the company code for sales
11. Select data from vbfa into table @data(lt_vbfa_zaspe).

12. Call function module md_convert_material_unit.

Changes for WC00093
1. Replaced date field erdat to budat from oij_el_ticket_i.
2. Commented idate from oijnomi in internal table (lt_oijnomi2).
3. Added a calcuation for quantity in LBS

4. Calculation for Variation % in lto , ls_final-actqty_lbs = ls_final-actqty_lbs * -1.
5. Commented Alv for qty.
6. Added a description for WERKS_D (Destination Plant).
7. Added a description for NAME_D (Destination Plant Description).
8. Added alv for Qty.
Changes for INC' 95490

1. Changed the table for Scheduled qty from OIJNOMSUBITEMS to OIJNOMI.
2. Read oijnomi1 table to get the expected schedule Quantity.

3. Convert UOM into required UOM.
4. Deleted the outcome where Actual quantity data is initial.
Changes for INC'118232
1. commented below code for the actual quantity deletion.

Changes for INC'364045
1. Select data from oij_el_ticket_i for Ticket process return code no. 98 also.
2. Select scheduled qty from oijnomi incase of scheduled qty is blank in oijnomsubitems
table.
2.1.6 Run Mode (M)

Foreground
2.1.7 Error/Exceptions Handling (M)

NA
2.1.8 BADI
NA
SAP Transaction
<Specify here SAP transaction in
which this enhancement is
called.>
Implementation Name
Definition Name
Multiple Use (Y / N)
Filter (Y / N)
If Yes – then field and value

<Repeat this block for each method>
Method Name
Input / Output Data
Business Logic
Error Handling
2.1.9 Customer-Exits (CMOD)

NA
SAP Transaction
<Specify here SAP transaction in

which this enhancement is
called.>
SMOD Name Publish and Subscribe / Process
CMOD project Name
<Repeat this block for each component>
Component
Input / Output Data
Business Logic
Error Handling

<Depending on the type of component i.e. Function module, Screen, Menu or table include relevant sub sections
should be used from this document>
2.1.10 Enhancement implementation

Development Object NA
Input / Output Data NA
Business Logic
Error Handling NA
Enhancement name(s) NA
Development Object
Input / Output Data
Business Logic
Error Handling
Enhancement spot name(s)

2.1.11 User-Exit Routines
NA
Name of the Routine E.g. USEREXIT_DELETE_DOCUMENT
Input / Output Data
Business Logic
Error Handling
2.1.12 Copy Routines

Configuration Steps
Name of the Routine
Input / Output Data NA
Error Handling NA
2.1.13 Function Module / RFC / BAPI (M – where applicable)

NA
Function Module Name <Provide here the Function Module Name>
Function Module Text <Provide here the Function Module description text>
Type of Function Module (Normal / RFC / Update)
Function Group
Business Object
Authorization

Import , Export, Changing Parameters
Field Name Reference Default Value Import/ Export/ Comments

Type Changing
Parameter
<Mandatory, Optional, Call by Value, Any

other information>
Table Parameters
Field Name Reference Type Comments
<Mandatory, Optional, Any other information>
Exceptions
Exceptions Comments
Short Text
2.1.14 IDOC Development

NA
2.1.14.1 General
Overall Function Triggering

When is the IDoc Triggered
When is the IDoc created
Batch or On-line
2.1.14.2 IDoc Customizing
Additional segment(s)
Segment Name
2.1.14.3 Extension
Extension Name
Linked basic Type
Parent Segment
Mandatory Yes/No
Minimum Number
Maximum Number
2.1.14.4 IDoc Type
IDoc Type name
2.1.14.5 Message Type
Message Type Name
Basic IDoc Type

Extension
2.1.14.6 Logical System
NA
Logical System Name
2.1.14.7 Process Code
NA
Process Code
Basic IDOC Type
Message Type
Function Module <If it’s a new function module the a function module section in this document
should be filled>
2.1.14.8 Distribution Model
NA
Model View
Sender/Client
Receiver/Server
Message type
2.1.14.9 File Port
NA
Port Name
Directory
File Name
Function Module

2.1.14.10 XML File port
NA
Outbound File
Port Name
Directory
File Name
Function Module
Send DTD Yes / No
Convert Special Character Yes / No
Outbound Trigger
Automatic Start Yes / No
RFC Destination `
File Name(Logical / Physical)
2.1.14.11 XML HTTP
NA
Port Name
RFC Destination
Content type
SOAP Protocol Yes / No
2.1.14.12 Partner profile
NA
Partner Number
Partner Type

2.1.14.13 Inbound/outbound Parameters
NA
Output Mode
Port
Package Size
Yes / No
Process Immediately
Yes / No
Collect IDOCs
2.1.14.14 Message Control
NA
Application
Message (output) Type
Logical Message Type
Process Code
Condition Record
2.1.15 Bespoke Table ( M – if applicable)

NA

<Repeat the section if there more than one objects>
Table Name
Short text
Data Class Master/ Transactional data
Maintenance Online maintenance desired: (Y / N)
Transaction <Transaction to which the table maintenance dialog is attached>
Authorization group for table
Table size Expected Number of records in Production
Buffering (Y / N)
If Y – Full / Generic / Single record
Log Data Changes (Y / N)
Client independent table (Y / N)
<Specify here a search help needs to be attached at table header level>
Field Key Data Elemt. Short text Check Table Comments, F1 help, special
name Or display, …
type/length

2.1.15.1 Structures / Table Types
Table Type name
Structure name
Field name Key Data Elemt. Short text Check Comments, F1 help,
Or Table special display, …
type/length

2.1.15.2 Data Elements
NA
S.No Data Domain Description(s) Comments

Element
1
2.1.15.3 Domain
NA
S.No Domain Field Field Value table/Fixed Values Comments

Type Length
1
2.1.15.4 Transaction (for table maintenance)
NA
2.1.16 Search helps

NA
Search Help Name
Short text
Search type
Data Source
Search Fields
Output and Selectable fields

2.1.17 Lock Objects
NA
Lock Object
Short text
Lock Mode
Primary Tables
Secondary Tables
Lock Parameters
2.1.18 NumberRange Objects

NA
Number range object
Short text
To Year Flag
Number Length domain
Warning %
Main Memory buffering

2.1.19 Class
NA
Class Name
Class Text
Superclass
Instantiation
2.1.20 Class Attributes

NA
Name Reference Initial Value Comments

Type
2.1.21 Class Methods

NA
<Repeat the section if there more than one objects.>
Method Name <Provide here the Method Name>
Method Text <Provide here the Method description>
Level <Instance/Static>
Visibility <Public/Protected/Private>

Import , Export, Changing Parameters
Field Name Reference Default Value Import/ Export/ Comments

Type Changing
Parameter
<Mandatory, Optional, Call by Value, Any

other information>
Exceptions
Exceptions Short Text Comments
2.1.22 Class Interface

NA
Name Description Comments
2.1.23 Class Events

NA
Name Type Description Comments

3. Testing
3.1.1 Input Data

1. Selection of Bucket while creation of Item
2. Selection of Item Type while creating the Item
3. Name of the Item.
3.1.2 Test Scenario

<Test Condition – A phrase that briefly describes the condition/functionality to be tested. Test Conditions
should be numbered sequentially. The number should be indicated with the description. (i.e.: 1. Validate
Material Number Screen Field). A Test Condition should comprise one unique test, not multiple tests that
are similar. For example, a correct test condition would include validating one selection screen field, not
validating all the selection screen fields and then listing them as steps of the condition. Each Test
condition should appear in its own table row.
Step 1 – Create an Item in the NWBC/Fiori App
1.1 Select the Bucket
1.2 Select the Item Type
1.3 Enter the Name
Step 2 – Validation in Item

1.4 Change the Status to Active or Management Screen In, An Error message should appear asking
for attaching the document
1.5 Attach the Document and now change the Status to Active or Management Screen in, System
should allow to change status and save the Decision Point.
Step 3 – Validation in Decision Point
1.6 The system should restrict the user to Open Decision Point - Gate 1 of Item Type Z001 - Project
with gate-keeping by SP&PM, if the Item Status is not Active or Management Screen In.
1.7 The system should allow the change in the certain status of a Decision Point only if the requisite
document is attached at the Decision Point.
1.8 In order to change the status of Decision Point as Passthrough (SP&PM), Passthrough (Segment)
or Passthrough (I&CS), the user needs to mandatorily provide the justification

3.1.3 Positive Unit Test
Step T-Code Step Description Expected Results

1 NWBC As mentioned in section 10.2 Result meeting the validation
will pass
2 Click here to enter text.
3.1.4 Negative Unit Test
T- Step Description
Step Expected Results
Code
1 NWBC As mentioned in section 10.2 Result not meeting the
validation will pass
2 Click here to enter text.


MASAR - TS - ONG - REP000028 - Transactions Summary Report - V5.0

Uploaded by

Copyright:

Available Formats

MASAR - TS - ONG - REP000028 - Transactions Summary Report - V5.0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MASAR - TS - ONG - REP000028 - Transactions Summary Report - V5.0

Uploaded by

Copyright:

Available Formats

Project: Masar

Technical Specification (TS)

MASAR_TS_ONG _REP000028_ Transactions Summary Report _V5.0

Development Summary (M) – Mandatory at High Level..............................................................................4

MASAR_TS_ONG _REP000028_ Transactions Summary Report _V5.0

3.1 .1 Input Data…………………………………………………………………………………………………...........................27

3.1.2 Test Scenario………………………………………………………………………………………………...........................27

3.1.3 Positive unit test………………………………………………………………………………………………......................28

3.1.4 Negative Unit Test………………………………………………………………………………………...........................28

MASAR_TS_ONG _REP000028_ Transactions Summary Report _V5.0

Contact Tel No: 8892693068 Contact Tel No:

Version Date Author Description of Change

1.0 28/01/2022 Sainath Initial version

2.0 13/09/2022 Suresh / Kumar Changes for INC' WC00093

3.0 27/09/2022 Saurav Changes for INC' 95490

4.0 21/11/2022 Saurav Changes for INC'118232

5.0 14/07/2023 Varsha Changes for INC'364045

MASAR_TS_ONG _REP000028_ Transactions Summary Report _V5.0

1.1 Development Summary (M) - Mandatory at High Level

And display the

Following input fields will be used to generate the output.

MASAR_TS_ONG _REP000028_ Transactions Summary Report _V5.0

Selection screen of the report:

1.2 Development Objects per System (M – If applicable)

1 D4A ZENOC_OGP ZDOGPR_TRANSACTION_DETAILS Import, Export, New

1.3 Dependency on Other Development or Interface (M – if applicable)

MASAR_TS_ONG _REP000028_ Transactions Summary Report _V5.0

MASAR_TS_ONG _REP000028_ Transactions Summary Report _V5.0

2.1 Generic Solution Details (M – where applicable)

2.1.2 Message Class and Messages (M – if applicable)

S.No Message Class Message Short Text Long Text

2.1.3 Selection Screen (M – if you are adding/changing existing screens)

2.1.4 Output Layout Details / Sample Formats (M – where applicable)

MASAR_TS_ONG _REP000028_ Transactions Summary Report _V5.0

11. Select data from vbfa into table @data(lt_vbfa_zaspe).

MASAR_TS_ONG _REP000028_ Transactions Summary Report _V5.0

3. Added a calcuation for quantity in LBS

Changes for INC' 95490

2. Read oijnomi1 table to get the expected schedule Quantity.

Changes for INC'118232

1. commented below code for the actual quantity deletion.

MASAR_TS_ONG _REP000028_ Transactions Summary Report _V5.0

2.1.6 Run Mode (M)

2.1.7 Error/Exceptions Handling (M)

If Yes – then field and value

MASAR_TS_ONG _REP000028_ Transactions Summary Report _V5.0

Input / Output Data

2.1.9 Customer-Exits (CMOD)

<Specify here SAP transaction in

SMOD Name Publish and Subscribe / Process

CMOD project Name

<Repeat this block for each component>

Input / Output Data

MASAR_TS_ONG _REP000028_ Transactions Summary Report _V5.0

2.1.10 Enhancement implementation

Input / Output Data NA

Input / Output Data

Enhancement spot name(s)

MASAR_TS_ONG _REP000028_ Transactions Summary Report _V5.0