FACT Project

24 June 2013

_________________________________________________________________________________________________________________

FACT Project
IDD243 Technical Specification
INTTRA OutBound_Interface
Prepared by:
Approved by:

Bipin H Gandhi (IBM)

___________________________

___________________________________________________________________________________________________________________

FACT Project Use Only

Page 1 of 15

FACT Project

24 June 2013

_________________________________________________________________________________________________________________

Document Attributes
Project name
Project ID
Document ID
Area of Validity
Responsible
Storage Location

FACT
<future use>
IDD243_TS
Global
<>
Toolset

Document Control
Date Issued:

01.08.2011

Version
No.
0.1

24.10.2011

0.1

Author initials

Control
initials

Approval
initials

Bipin H Gandhi

CONBAV

CONBAV

CONAFM

CONAFM

CONBAV

Reason
for
Change:
Initial Version
TPR 26308
TPR 26308

Security Classification
FACT project usage

___________________________________________________________________________________________________________________

FACT Project Use Only

Page 2 of 15

FACT Project

24 June 2013

_________________________________________________________________________________________________________________

Content
1.

INTRODUCTION..........................................................................................................4

2.

OVERVIEW-DESCRIPTION......................................................................................5

3.

3 DETAIL INFORMATION.........................................................................................6

3.2 Scope (TO)...................................................................................................................................6

3.2.1 Country Information ............................................................................................................6
3.2.2 Run Mode..............................................................................................................................7
3.2.3 Data Volume ........................................................................................................................7
3.2.4 Security/Authorisation..........................................................................................................7
3.2.5 Dependencies .......................................................................................................................7

4.

4 DIFFERENT TYPES OF ENHANCEMENTS (TO)...............................................8

4.1 User Exits (TO)............................................................................................................................8

N/A................................................................................................................................................8
N/A................................................................................................................................................8
4.2 Function Exits (TO) N.A.............................................................................................................8
4.3 Field Exits (TO) N.A....................................................................................................................8
4.4 Menu Exits (TO) N.A...................................................................................................................8
4.5 Screen Exits (TO) N.A.................................................................................................................8
4.6 Table Exits (TO) N.A...................................................................................................................8
4.8 Custom Transaction / Module Pool (TO) N.A...........................................................................8
4.9 Workflow Developments (TO) N.A............................................................................................9
4.10 Additional Enhancement Specifications (TO) N.A..................................................................9
4.11 Data Dictionary Objects (TO) N.A..........................................................................................9
5 Error handling (FO).....................................................................................................................10

5.

6 DETAILED LOGIC & PSEUDO CODE (TO)......................................................11

6.

7 ISSUES.......................................................................................................................13

7.1 Issue List....................................................................................................................................13

7.

8 ADDITIONAL INFORMATION............................................................................14

8.

9 TECHNICAL SPECIFICATION CHECKLIST (TO)..........................................15

___________________________________________________________________________________________________________________

FACT Project Use Only

Page 3 of 15

FACT Project

24 June 2013

_________________________________________________________________________________________________________________

Introduction
General Information
Description of Activity

INTTRA OutBound Interface

Business Area

ATR

SAP R/3 Version

ECC 6.0

Location / Site

Global Design

Primary Contact Specification SAP

Bipin H Gandhi

Phone number
Email address

[email protected]

Secondary Contact Specification SAP

Phone number
Email address

___________________________________________________________________________________________________________________

FACT Project Use Only

Page 4 of 15

FACT Project

24 June 2013

_________________________________________________________________________________________________________________

Overview-Description
This Interface is part of the overall FACT-INTTRA EIPP Integration design.
INTTRA is launching EIPP (Electronic Invoice Presentation and Payments) - a direct EDI solution
pertaining to eInvoicing, Dispute Logging & epayment. AP Moller Maersk has agreed to
participate in this project, for the start to interface to our key client Khune & Nagel in USA
The purpose of this interface is to trigger the creation of a dispute case for particular invoices.
This FS will cover the Dispute creation/re-dispute Interface from INTTRA to FACT (AR and
FSCM).

___________________________________________________________________________________________________________________

FACT Project Use Only

Page 5 of 15

FACT Project

24 June 2013

_________________________________________________________________________________________________________________

3 Detail Information
INTTRA Dispute Interface (INTTRA to SAP):

Once the customer creates a dispute case in INTTRA, INTTRA will trigger a message, then the
document should be marked as disputed in FACT and a Dispute case should be created in FSCM (the
dunning block D should be updated in accounting automatically), if the document is already
disputed and closed, then the case should get re-disputed.

3.2 Scope (TO)1

3.2.1 Country Information
Where this development will be run
Global Development will be run at all sites:
Local Development, will be run at the following site(s):
Language considerations
No language considerations
Master data related considerations:
Translation requirements
No translation requirements Development will be used in English only
Translation required:
Currency and Unit of Measure

Comments

___________________________________________________________________________________________________________________

FACT Project Use Only

Page 6 of 15

FACT Project

24 June 2013

_________________________________________________________________________________________________________________

3.2.2 Run Mode

Development will be run in the following ways
On-line by end user From within SAP transaction(s):
On-line Via a development-specific menu path.
In background Scheduled at regular intervals/time:
In background Triggered by a certain event: SAP to INTTRA
Other:
Comments Specific variations

3.2.3 Data Volume

Legacy System

Frequency/Time

Volume per day

Comments

3.2.4 Security/Authorisation
How should access to run the development be restricted
No specific restrictions
Restriction on authorization on development specific transaction code only
Restrictions based on certain criteria
Other:
Comments

3.2.5 Dependencies
N.A.

___________________________________________________________________________________________________________________

FACT Project Use Only

Page 7 of 15

FACT Project

24 June 2013

_________________________________________________________________________________________________________________

4 Different Types of Enhancements

(TO)
4.1 User Exits (TO)
Name of Exit / Business Add-In / Business
Transaction Event
Project
Enhancement
Component(s)
SAP Program
Function Module
Transactions impacted
Include(s)
Copy Control

N/A
FACT - INTTRA
BTE
N/A
N/A
N/A
N/A
N/A

4.2 Function Exits (TO) N.A.

4.3 Field Exits (TO) N.A.
4.4 Menu Exits (TO) N.A.
4.5 Screen Exits (TO) N.A.
4.6 Table Exits (TO) N.A.

4.7

Copy control routine N.A.

4.8 Custom Transaction / Module Pool (TO) N.A.

___________________________________________________________________________________________________________________

FACT Project Use Only

Page 8 of 15

FACT Project

24 June 2013

_________________________________________________________________________________________________________________

4.9 Workflow Developments (TO) N.A

4.10 Additional Enhancement Specifications (TO) N.A.
4.11 Data Dictionary Objects (TO)

N.A.

Table Name
Short text
Delivery Class
Table maintenance allowed
Data class
Size category
Buffering
Table Locking
Authorisation Group
Function Group
Maintenance Type
Fields
Field
Name

Data
Element

Domain

Type

Leng
th

Check Table

Key
Field

Foreign
Key

Comments

Comments

Search Help
N.A.
Lock Objects
N.A.
Lock Object details
N.A.
Lock Parameter details
N.A.

___________________________________________________________________________________________________________________

FACT Project Use Only

Page 9 of 15

FACT Project

24 June 2013

_________________________________________________________________________________________________________________

5 Error handling (FO)

Error Handling Detail: N.A.

Restart/Recovery: N.A.

Error Messages: N.A.

Message no

Message Text

Possible reason

Resolution

___________________________________________________________________________________________________________________

FACT Project Use Only

Page 10 of 15

FACT Project

24 June 2013

_________________________________________________________________________________________________________________

6 Detailed Logic & Pseudo code (TO)

Program Information
S.N
o

Object

Object Name

Project

INTTRA

Function Group

/FACTGLB/GTATR_DISPUTECASE

Custom Table

N/A
N/A
6

Transport
N/A

Table Maintenance
Gen.

Parameter Transaction
Code

N/A

9
Program Name
(Include)

FM:
/FACTGLB/GTA_INTTRA_OUTPUTCASE

Method Used in DMD system

/FACTGLB/CL_IM_GTO_CHGSTAT
IF_EX_SCMG_STORE_S~WAS_SAVED
Logic in BADI :

If INTTRA_DIS is Flagged and status is 60 or 70 then only call the FM

/FACTGLB/GTA_INTTRA_OUTPUTCASE to process the data and post the IDOC to INTRA

Relevant Function Modules:

___________________________________________________________________________________________________________________

FACT Project Use Only

Page 11 of 15

FACT Project

24 June 2013

_________________________________________________________________________________________________________________

1. MASTER_IDOC_DISTRIBUTE : Application interface to the ALE layer on outbound processing

side

2. MMODEL_INT_VALID_GET : Read distribution model for message types

3. OWN_LOGICAL_SYSTEM_GET : Specify Name of Current Logged-on System (client in R/3
System)

Pseudo Code in Function Module:

Call of sub-routine ' F_LOGICAL_SYSTEM '
Call of function module OWN_LOGICAL_SYSTEM_GET ( Specify Name of Current Loggedon System (client in R/3 System) )
Call of function module MMODEL_INT_VALID_GET ( Read distribution model for message
types )
Call of sub-routine ' F_FILL_EDIDD '
Call of function module MASTER_IDOC_DISTRIBUTE ( Application interface to the ALE
layer on outbound processing side )
Begin of change TPR 26308
1.
2.

Get the receivers from the message type by using ALE_MESTYPE_GET_RECEIVER.

Triggure the outbound idoc from IF_EX_SCMG_STORE_S~WAS_SAVED.

End of change TPR 26308

___________________________________________________________________________________________________________________

FACT Project Use Only

Page 12 of 15

FACT Project

24 June 2013

_________________________________________________________________________________________________________________

7 Issues
7.1 Issue List
Issue
#

Issue Description

Resolution Issue Owner Planned

resolution
date

Status
(O)pen,
(R)resolved,
(C)losed

1.
2.

___________________________________________________________________________________________________________________

FACT Project Use Only

Page 13 of 15

FACT Project

24 June 2013

_________________________________________________________________________________________________________________

8 Additional Information

___________________________________________________________________________________________________________________

FACT Project Use Only

Page 14 of 15

FACT Project

24 June 2013

_________________________________________________________________________________________________________________

9 Technical Specification Checklist (TO)

Checklist
1. Program/Include Information has been entered

Yes / No
N/A

2. Overview description of the enhancement requirement

N/A

3. Detailed description of the to-be process

YES

4. Limits/scope of the enhancement. Specify the country information,

run mode, data volume, authorisation information etc.

YES

5. For each different type of enhancement developed, a SAP data

relationship diagram and detailed data processing logic has been
documented

N/A

6. Error handling has been documented

N/A

7. Detailed Logic & Pseudo code has been documented

YES

8. Issue List Has Been entered.

NO

9. Any additional information

NO

___________________________________________________________________________________________________________________

FACT Project Use Only

Page 15 of 15