Title: Business Scenario: SD-BIL (Billing)

System extension: 002 EDI outbound invoices

Version: 1.0

SAP-Product/Release:
Maintained by:
Filing:

Responsible Person Date/Signature

[Name, Department] [MMM-DD-YYYY]

Edition

Review

Review

Review

Approval

Page 1 of 14
History of changes

Page 2 of 14
Table of contents

1 BPML MERCK GLOBAL..........................................................................................................4

1.1 SD-BIL (BILLING)..............................................................................................................4
1.1.1 Designation and general description of the system extension................................4
1.1.2 Limitation of the functional scope...........................................................................4
1.1.3 Definitions, designations and shortcuts..................................................................4
1.1.4 Process Functional Description..............................................................................4
1.1.4.1 Purpose of the enhancement..........................................................................4
1.1.4.2 Process Flow chart..........................................................................................4
1.1.5 Solution..................................................................................................................4
1.1.5.1 Report............................................................................................................. 4
1.1.5.2 Interface.......................................................................................................... 4
1.1.5.3 Enhancement (transaction Module Pool)......................................................7
1.1.5.4 Enhancement (User Exit)................................................................................7
1.1.6 Authorization check................................................................................................8
1.1.7 Jobs....................................................................................................................... 8
1.2 ADDITIONAL REQUIREMENTS..............................................................................................8
1.2.1 Additional technical requirements...........................................................................8
1.2.2 Hardware environment...........................................................................................8
1.2.3 Network..................................................................................................................8
1.2.4 Application.............................................................................................................. 9
1.2.5 Development class.................................................................................................9
1.2.6 Performance Aspects.............................................................................................9
1.2.7 Reorganization.......................................................................................................9
2 TECHNICAL ANALYSIS....................................................................................................10
2.1 LIST OF OBJECTS............................................................................................................10
2.2 TECHNICAL DESCRIPTION.................................................................................................11
2.2.1 Description of the objects.....................................................................................11
2.2.1.1 Program.........................................................................................................11
2.2.1.2 Function group ..........................................................................................11
2.2.1.3 Table .........................................................................................................11
2.2.1.4 Transaction...................................................................................................12
2.2.1.5 Other object types.........................................................................................12
2.2.1.6 Interfaces to external systems.......................................................................12
2.2.1.7 Job Details....................................................................................................14

Page 3 of 14
1 BPML Merck Global

1.1 SD-BIL (Billing)

1.1.1 Designation and general description of the system extension

Tempo provides a global EDI outbound interface for sending invoices electronically to
customers. Since the local US CMG need some additional fields in the Tempo standard IDOC
INVOIC01, these fields have to be made available in the corresponding IDOC structure.

1.1.2 Limitation of the functional scope

Since the IDOC is globally used and changes might affect running interfaces, the changes are
relevant for regression testing.

1.1.3 Definitions, designations and shortcuts

Term/short cut Definition / Explanation Source

N/A

1.1.4 Process Functional Description

1.1.4.1 Purpose of the enhancement

The purpose of this FS is to describe the enhancements of SAP standard IDOC type INVOIC01
(EDI outbound interface for invoices) with US-specific qualifiers.

1.1.4.2 Process Flow chart

See global EDI outbound interface for invoices.

1.1.5 Solution

1.1.5.1 Report
N/A

1.1.5.2 Interface
Different interface flows
See global EDI outbound interface for invoices

Page 4 of 14
Information per flows (field contents and filed name reference)
The processing of the IDOC will be done in a specific program include with a local development
package, which will be provided by Central Team / AO. As example see the following include:

In order to differentiate the Idecs for different countries, it is important, that the Logical Message
Variant EDIDC-MESCOD is a specific code for US, e.g. NA2.

The following table shows the fields that should be added as new qualifiers to IDOC INVOIC01:

# Table Short Data Length Dec New Segment Qua Comments

Name- Description Type IDOC lifie
Field ext. US r

Y/N
1 T606Z- Licence CHAR 10 0 Y E1EDK02 800 Licence Number
GENNR Number from from GTS (T606Z-
GTS GENNR for
T606Z-KUNNR =
ship-to in the
invoice VBDKR-
KUNWE)
2 EMBK- Licence DATS 8 0 Y E1EDK02 801 Licence Expiration
GENDA Expiration Data from GTS
Data from (EMBK-GENDA)
GTS for selected licence
number and ship-to
customer
3 DEA Number Determine

Page 5 of 14
# Table Short Data Length Dec New Segment Qua Comments
Name- Description Type IDOC lifie
Field ext. US r

Y/N
of the ship- customer number
to-party of ship-to-party on
Derived from invoice item level
(from VBPA-
KUNNR with
Name3 parameters VBPA-
KNA1-
VBELN = VBRK-
NAME3
VBELN, VBPA-
Or POSNR=VBRP-
Or POSNR and
PARVW = WE) and
determine for this
ADDR1_ Search term customer the field
DATA- 2 name 3 [KNA1-
SORT2 NAME3] or - if
empty - the field
search term2
[ADDR1_DATA-
SORT2 only
relevant when sold-
to and ship-to are
the same customer
number].
4 MEAN- NDC- CHAR 18 0 Y E1EDP1 999 NDC11 # (new
EAN11 number 9 IDOC extension
ZV)
(field
IDTNR)
Determine MEAN-
EAN11 by MEAN-
MATNR = VBRP-
MATNR and
EANTP = newly
created
customizing key
for NDC11, see
URS
R21_REQ_BS_DH
-
MAT_BP_BUPR_
MAINTE_020
IMG Logistics
General
Material Master
Settings for Key
Fields
International
Article Numbers
(EANs) Define
Attributes of
EANs/UPCs
5 MCHA- Batch Expiry DATS 8 0 Y E1EDP0 045 Batch expiry date
VFDAT Date 3 (new IDOC
extension ZV)

Go to table VBRP
and fill
VBELN=VBRK-

Page 6 of 14
 # Table Short Data Length Dec New Segment Qua Comments
Name- Description Type IDOC lifie
Field ext. US r

Y/N
VBELN,
MATNR=VBRK-
MATNR and
POSNR=XX
(where XX is the
sequential number
of the item) to get
WERKS and
CHARG.
Then go to table
MCHA with VBRP-
MATNR, VBRP-
WERKS and
VBRP-CHARG to
get MCHA-VFDAT

IDOC Output of
this field has to be
independent of
customer master
fields YVCUKNVV-
YYV_DRU_CHAR
G and
YVCUKNVV-
YYV_DRU_DATE
S (Merck
Additional data),
that control printing
batch number and
expiry date on
invoice form.

Conditions /triggering event

See global EDI outbound interface for invoices

1.1.5.3 Enhancement (transaction Module Pool)

User interaction logic
Screen layout
Execution option
Expected output

1.1.5.4 Enhancement (User Exit)

Trigger condition

Execution logic

Page 7 of 14
1.1.6 Authorization check

1.1.7 Jobs

Item Job Description Responsible

A

1.2 Additional requirements

1.2.1 Additional technical requirements

Technical Requirements <XXXX_REQ_BS_<CR-ID>_>

NNN Description
010 [Description of the requirement 010]
020

1.2.2 Hardware environment

Requirement-ID(s) F - ID Settings / Description / Reference

XXXX_REQ_BS_<[level2- CMG#_.
shortcut>_BP_<level3-
shortcut[_level4-shortcut]>_NNN
XXXX_REQ_BS_<[level2-
shortcut>_BP_<level3-
shortcut[_level4-shortcut]>_NNN+x
XXXX_REQ_BS_<CR-ID>_NNN CMG#_.
CMG#_.

1.2.3 Network

Requirement-ID(s) F - ID Settings / Description / Reference

XXXX_REQ_BS_<[level2- CMG#_.
shortcut>_BP_<level3-
shortcut[_level4-shortcut]>_NNN
XXXX_REQ_BS_<[level2-
shortcut>_BP_<level3-
shortcut[_level4-shortcut]>_NNN+x
XXXX_REQ_BS_<CR-ID>_NNN CMG#_.
CMG#_.

Page 8 of 14
1.2.4 Application

Requirement-ID(s) F - ID Settings / Description / Reference

XXXX_REQ_BS_<[level2- CMG#_.
shortcut>_BP_<level3-
shortcut[_level4-shortcut]>_NNN
XXXX_REQ_BS_<[level2-
shortcut>_BP_<level3-
shortcut[_level4-shortcut]>_NNN+x
XXXX_REQ_BS_<CR-ID>_NNN CMG#_.
CMG#_.

1.2.5 Development class

Development Designation
class
Z_V_US_ALL Dev package

1.2.6 Performance Aspects

1.2.7 Reorganization

Page 9 of 14
2 Technical Analysis

2.1 List of objects

The objects mentioned in the following table have to be generated in addition to the SAP standard or modified within the SAP standard.
Please find a detailed description of main objects in following chapters.
Requirement-ID(s) F - ID Object Name Object NEW/ Short Description
Type* MOD
ZXEDFU02 REPS MOD Include ZXEDFU02
ZV_ZXEDFU02_06 PROG NEW New Qualifiers in INVOIC01 for us

*: 4-digit shortcuts from correction and transport system

Page 10 of 14
 2.2 Technical description

2.2.1 Description of the objects

2.2.1.1 Program
N/A

2.2.1.1.1 Processing logic

Input
N/A

Processing
Usage of the global template.

Output
N/A

Graph

2.2.1.2 Function group

N/A

2.2.1.2.1 Function module

N/A

Input

Processing

Output

Graph

2.2.1.3 Table
N/A

Fieldname Designation Key Data Element Domain Check table*

* Optional

Page 11 of 14
2.2.1.3.1 Maintenance Interface

2.2.1.3.2 Technical Settings

2.2.1.4 Transaction
N/A

2.2.1.4.1 Corresponding program

2.2.1.4.2 Type

2.2.1.4.3 Details

2.2.1.5 Other object types

2.2.1.6 Interfaces to external systems

Item Interface Input in /
Output from
SAP
A EDI OUTBOUND INTERFACE Output from
SAP

2.2.1.6.1 Interface A
Tempo provides a global EDI outbound interface for sending invoices electronically to
customers. Since the local US CMG need some additional fields in the Tempo standard IDOC
INVOIC01, these fields have to be made available in the corresponding IDOC structure
The purpose is to describe the enhancements of SAP standard IDOC type INVOIC01 (EDI
outbound interface for invoices) with US-specific qualifiers (EDIDC-MESCOD= NA2).

2.2.1.6.1.1 Processing logic

Program ZXEDFU02
Function module EXIT_SAPLVEDF_002 -> Include ZXEDFU02
EDIDC-MESCOD= NA2 condition trigger for the new qualifiers
New Include program created under name ZV_ZXEDFU02_06

Program ZV_ZXEDFU02_06
To get the License number data from GTS using RFC with function module
Y_V_GTS_GET_PRD_LEGAL_INFO_F01 IS USED
Get the License number and License expiration date
1.License Number EXLIC is inserted as BELNR in Segment E1EDK02 under Qualifier 800
2.License expiration date DATBI is inserted as DATUM in Segment E1EDK02 under Qualifier
801

Page 12 of 14
3. DEA Number Segment E1EDKA1 NAME3 for PARVW = WE
A. Get KUNNR from table VBPA where VBELN = VBRK-VBELN and PARVW =WE, Pass this
KUNNR to KNA1 and get NAME3
Pass this NAME3 in E1EDKA1 as NAME3 for PARVW = WE
B. If this NAME3 is Initial then check KUNNR (when PARVW = AG)
Is same as KUNNR ((when PARVW = WE). select ADRNR from KNA1 based on this KUNNR,
pass ADRNR to ADRC table and get the field SORT2
Pass this SORT2 in E1EDKA1 as NAME3 for PARVW = WE

4. NDC Number Segment E1EDP19 - Qualifier 999

Get EAN11 from MEAN where MEAN- MATNR VBRP-MATNR AND EANTP = Z7
Pass this EAN11 to E1EDP19 as IDTNR against qualifier 999

5. Batch Expiry Date Segment E1EDP03 -Qualifier 045

Select VFDAT from MCHA WHERE MCHA-MATNR, MCHA- WERKS, MCHA-CHARG
Are respectively matching with VBRP-MATNR, VBRP-WERKS, VBRP-CHARG
Pass this VFDAT to E1EDP03 as DATUM against qualifier 045

2.2.1.6.1.2 Systems involved

Dominant system:
Subordinated system 1:

2.2.1.6.1.3 Interface Type

Bi-directional online-interface
One-directional online-interface
Bi-directional batch-interface
One-directional batch-interface
Other Description: EDI outbound Invoice_

2.2.1.6.1.4 Data to be transferred

From TEMPO to subsystem X:
Followings are the qualifiers to be added in IDOC INVOIC01
Pos. Table- Fieldname Data- Length Description
name type 1)
E1EDK02 BELNR CHAR 10 License Number
(Qualf 800)
E1EDK02 DATUM DATS 8 License Expiration Data from
(Qualf 801) GTS
E1EDKA1- NAME3 CHAR 35 NAME3
(PARVW =
WE)
E1EDP19 IDTNR CHAR 18 NDC Number
(Qualf 999)

Page 13 of 14
Pos. Table- Fieldname Data- Length Description
name type 1)
E1EDP03 DATUM CHAR 8 Batch Expiry Date
(Qualf 045)
1)
4-digit shortcuts from Data Dictionary (DDIC)

From subsystem X to TEMPO:

Pos. Table- Fieldname Data Length Description
name type

2.2.1.6.1.5 IDocs

Source format: [designation]

IDOC - INVOIC01

Description of mapping

Target format IDoc [designation]

2.2.1.7 Job Details

The following job steps have to be implemented:
Step no Program name Report variant User
1 Program name1 Report variant1 userid2

Page 14 of 14