GDEVWR0008023 Material Master Interface (GLOBE To BEST) FS - TS - 12 - 17082005 - Updated

Development Specification
Development references
Development I
GDEVWR0008023
Brief development descriptio
Material master interface (GLOBE to BEST)
Gap ID
FITGAP0022951
Business Process Level 3 or 4
Process Purchase Order
Functional Owner
Benny Jiang, Carsten Link
Technical Owner
George Du Plessis
Author
Benny Jiang, Carsten Link

GDEVWR0002666
GDEVWR0001930
GDEVWR0002318
GDEVWR0007019
GDEVWR0002203
Reference Documents
Workstream
GLOBE Template
Process Stream
Ensuring Supply
mySAP component /module
R3
Type of development
Messaging
Template Version
1.5
Global / Market
US
Status
Work in Progress
Read the General Guidelines
337992532.doc
Page 1 of 45
Created: 21.07.2005
Printed: 27.05.2005 09:07
Version Contro
Revision History:
Section
Version
Reference No.
Description of change (including the

reason for the change)
ALL
FS
Initial version
1.0
1.0
1.1
Reference
Change
Request
Changed
By
Date
Benny
Jiang
Benny
Jiang
Carsten
Link
April-92005
May-132005
1.2
Add requirements to include raw and

packaging materials
Add changes after workshop
TS
1.3
1.0
Initial
Shilpa
Reddy
July-42005
UTP
1.1
1.2
1.3
1.0
Initial
Shilpa
Reddy
July-42005
1.1
1.2
1.3
FS Functional Specification
TS Technical Specification
UTP Unit Test Plan
337992532.doc
Page 2 of 45
Created: 21.07.2005
Printed: 27.05.2005 09:07
Sign-off
Approved by
Custom Development Team Lead (Interfaces only)
(TO)
Process Team Lead (FO)
Complimentary Application Team Lead
AD Development Coordinator (2 names: On+Off-Site)
Developer (FO)
QA Reviewer (TO)
CD-Middleware (MW)
ALE Configuration Team
Approved by (Applicable for Messaging Only)
Cross Application Team Lead (TOM)
Custom Development Team Lead (where
development required)(TO)
Messaging Configurer (TOM)
QA Reviewer (TOM/TOD)
337992532.doc
Name
George du
Plessis
Vangie
Argonza
George du
Plessis
Carsten Link
Signature
Date
Page 3 of 45
Created: 21.07.2005
Printed: 27.05.2005 09:07
Legend
IMPORTANT: All paragraphs titles have been marked with a 'code', defining which
stakeholder is responsible for completing the paragraph. Please find below explanation
of the codes, as well as their roles in the process flow
FO
Functional Owner
TO
Technical Owner AD Development Coordinator (On-site and OffSite). The TO consists of the AD Development Coordinator as well as
the Developer.
QA
QA reviewer (for messaging: both Messaging and AD)
SO
Security Owner
DEV
Developer. Covers also some TO activities on his behalf.
MWTO
Middleware Technical Owner
MWQA
Middleware QA Reviewer
MWDEV
Middleware Developer
TOM
Technical Owner Messaging Messaging Coordinator
TOD
Technical Owner Development AD Development Coordinator
Co mplete
Functional
Sections
Initia l
Walkthrough +
QA
FS Workshop
FS Final QA +
Sign-Off
Co mplete
Technival
Sections
TS QA
FO
TO
FO + TO
TO
TO
QA + MWQA
Details on the development process can be found in : Developement Process
For Messaging Only:

An assigned TOM and TOD are working very closely for the entire development lifecycle. For sections
where TO is responsible to complete, the responsibility in general will fall with the TOM being responsible
for the overall technical solution. TOD is responsible in documenting any coding logic
Complete
Functional
Sections
Initial
Walkthrough +
QA
FS Workshop
FS Final QA +
Sign -Off
FO
TO
FO + TO
TO
Complete
Complete
Technical
section
Technival
Sections
(messaging)
TS QA
Complete
TO
Technical section
QA + MWQA
(development)
FO
337992532.doc
TOM,TOD
FO,TOM,TOD
TOM,TOD
Page 4 of 45
TOM,TOD
QA + MWQA
Created: 21.07.2005
Printed: 27.05.2005 09:07
Table of contents
1
Management Summary (FO).....................................................................................
Process Flow / Context (FO)....................................................................................
Functional Requirements (FO).................................................................................

3.1 DESCRIPTION OF THE DEVELOPMENT (FO).......................................................................................
3.2 HOW THE DEVELOPMENT WILL WORK (FO).....................................................................................
3.3 SAP GENERAL REQUIREMENTS (FO).............................................................................................
3.4 ASSUMPTIONS/DEPENDENCIES/CONSTRAINTS (FO)........................................................................
3.5 QUALITY ASSURANCE REMARKS/SIGN-OFF OF SECTION (TO).........................................................
Overall Development Design (TO).........................................................................

4.1 COMPLEXITY, ESTIMATES AND DEADLINES.....................................................................................
4.2 BRIEF TECHNICAL OVERVIEW........................................................................................................
4.3 ODC READINESS CHECKLIST........................................................................................................
4.4 MANDATORY - DEVELOPMENT QA CHECKLIST.............................................................................
Appendix C-1 : Interface (Between SAP and External Systems).......................

5.1 SYSTEMS DIAGRAM (FO)..............................................................................................................
5.2 BUSINESS DATA TO BE INTERFACED (FO).......................................................................................
5.3 INTERFACE REQUIREMENTS (FO)..................................................................................................
5.4 ERROR HANDLING (FO).................................................................................................................
5.5 TECHNICAL DETAILS (TO).............................................................................................................
5.6 TECHNICAL DETAILS ON ABAP-DEVELOPMENT FOR THE INTERFACE (TO).......................................
5.7 QUALITY ASSURANCE REMARKS/SIGN-OFF OF SECTION (TO + QA)...............................................
Appendix C-2: Middleware.....................................................................................

6.1 FILE IN (FO + TO)........................................................................................................................
6.2 FILE OUT (FO + TO)....................................................................................................................
6.3 MIDDLEWARE MESSAGE ROUTING RULES (FO + TO).....................................................................
6.4 MIDDLEWARE FLOW DIAGRAM (TO)...............................................................................................
6.5 ERROR HANDLING (MWTO)..........................................................................................................
6.6 ADAPTER DETAILS (MWTO)..........................................................................................................
6.7 MIDDLEWARE INTERFACE VALUES (MWTO)....................................................................................
6.8 MAPPING (MWTO).......................................................................................................................
6.9 MIDDLEWARE CONFIGURATION (MWTO)........................................................................................
6.10 QUAL. ASSURANCE REMARKS/SIGN-OFF OF SECTION (TO + MWQA).............................................
Appendix M: MANDATORY - Security (TO + FO +SO).........................................

7.1 TRANSACTION CODES (TO)...........................................................................................................
7.2 AUTHORISATION OBJECTS (FO + SO)............................................................................................
7.3 DEVELOPMENT-SPECIFIC TEST-USERS CREATED (SO).....................................................................
Appendix N: MANDATORY - Testing.....................................................................

8.1 FUNCTIONAL TEST CASES (FO).....................................................................................................
8.2 TECHNICAL TEST CASES (TO).......................................................................................................
Appendix O: MANDATORY - Object documentation- (DEV)...............................
337992532.doc
Page 5 of 45
Created: 21.07.2005
Printed: 27.05.2005 09:07
9.1 SAP DEVELOPMENT OBJECTS (DEV)...........................................ERROR! BOOKMARK NOT DEFINED.

9.2 NON-SAP DEVELOPMENT OBJECTS (DEV + MWDEV)................ERROR! BOOKMARK NOT DEFINED.
337992532.doc
Page 6 of 45
Created: 21.07.2005
Printed: 27.05.2005 09:07
Management Summary (FO
For the back office phase on the NUSA project an interface between GLOBE an BEST is needed
for material master information.
GLOBE is the leading system for master data. Thus, an interface is required to transfer material
master for finished goods, semi-finished goods, raw and packaging materials from GLOBE to
BEST.
The scope of this functional specification is to outline the requirements to create an IDoc to send
material master (FG, SFG, RM, PM) from GLOBE to the middleware. It has been decided that
the sending system will be the Supply Operation System (SOS) in GLOBE.
337992532.doc
Page 7 of 45
Created: 21.07.2005
Printed: 27.05.2005 09:07
R/3
Process Flow / Context (FO)
Material
Master
IDoc
MW
337992532.doc
Page 8 of 45
Created: 21.07.2005
Printed: 27.05.2005 09:07
3 Functional Requirements (FO)

3.1
Description of the development (FO)
The development should extract Material Master data from R/3 SOS box and prepare an IDoc. This IDoc
should be transported through the GLOBE Middleware (without change) to the BEST middleware IAC. All
conversion will happen either in IAC or BEST itself.
BDCPV
As we only want to sent relevant information for NUSA, certain Filters in the extraction program
generating the IDOC have to be put in.
Following are the rules that need to be put in.
IDOCs for Materials should only be sent to BEST if the plant-specific status is Z2, Z3, Z4, Z5 or Z6.
We do not want to send a material that has plant specific status Z1. We also only want to send materials
with material type FERT, HALB, ROH and ZPCK. An additional criteria is also the plant code. We only
want to send materials for plants that belong to NUSA company Code US16. As a further criteria we only
want to send the materials when the accounting view for the relevant plant has been created.
So if a material gets extended to a new plant and accounting view is not maintained for this new
plant we do not want to send it to BEST.
As a summary the following will be used filters to ensure onlu the relevant material are send to BEST:
Plant status (MARC-MSTAE):
Material Type (MARA-MTART):
Plants (MARC-WERKS):
Z2,Z3,Z4,Z5,Z6
FERT, HALB, ROH, ZPCK
all plants relevant for US16 (see attachment for details.
plants _27may.txt
This is status as of May27, major DCs and Factories Plants

should be able to be maintained in a custom table to be flexible
for upcoming changes in the plant area.
Currently Sales Org., Purchasing Org and Distribution Channel are not part of the filters. This might
change after integrated testing.
337992532.doc
Page 9 of 45
Created: 21.07.2005
Printed: 27.05.2005 09:07
3.2
How the development will work (FO)
Where this development will be run (FO)

Geographically
Global Development, will be run in all markets
Local Development, will be run in the following market(s: Nestle USA
Environments Components
MDR
HR
R/3 Core
Financial System (Distributed Architecture only)
Commercial System (Distributed Architecture only)
Manufacturing System (Distributed Architecture only)
SEM (Distributed Architecture only)
Global ATP (Distributed Architecture only)
Restitution System (Distributed Architecture only)
CRM
APO
DP (Distributed Architecture only)
PPDS/SNP (Distributed Architecture only)
R&D
EBP
WPS
Othe:
How the development will be run (FO)

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
Batch process extracting all delta Master Material additions and/or updates since last development run. Run at
12:00AM. Needs to be determined how often we have to run when testin End-2-End
Development must buerun only when detection of Material Master creation and/or updates and/or deletions for
Nestle USA market.
In background - Triggered by a certain event
Othe:
Comments Specific Variations
Security(FO)
How should access to run the development be restricted.
No specific restrictions
Restriction on authorization on development-specific transaction code onl
Restrictions based on certain criteri.:
Othe:
Comments:
Normally run by background job. If urgent requirements exist to replicate immediately, this has to be requested from
the GC.
337992532.doc
Page 10 of 45
Created: 21.07.2005
Printed: 27.05.2005 09:07
3.3
SAP General Requirements (FO)
Data Volume (FO)

Country/Marke
USA
Frequenc
1 file per day to be determined it
will be corresponding to the number of
times the job runs
Volume per ru
Only delta transactions (new addition or
modification). Expected to have less than 1000
transactions per run on average (a very high level
estimate)
Comments:
If there is no data to produce the corresponding IDoc for a specific day, do not send empty IDoc. Only send IDoc
when theres data.
Language considerations (FO)

Language considerations
No language considerations
Master Data Related consideration:
Translation requirements
No translation requirements Development will be used in English only
Translation required:
Comments
Currency and Units of Measure (FO)

Currency and units of measure will be sent to the middleware without conversion. It is expected that the conversion
will not take place in GLOBE, but rather in IAC or BEST.
3.4
Assumptions/Dependencies/Constraints FO)
1) The generated IDoc will contain all fields in GLOBE without any conversion. It is expected that the conversion
and filtering of fields will take place in the middleware or BEST.
2) The sending system will be SOS box.
3) Interface will be run once per day as a background job scheduled at 12:00am server time. (Will be revaluated
when testing E2E)
4) It is possible to run the interface manually, by requesting the GC to schedule the job immediately
5) Classification IDOC (CLFMAS) is not send out
6) Qm view idoc is not sent out (QMMAT)
7) We always send out the full IDOC
8) All relevant conversions will be handled either in IAC (legacy middleware) or BEST (legacy SAP)
337992532.doc
Page 11 of 45
Created: 21.07.2005
Printed: 27.05.2005 09:07
3.5 Quality Assurance Remarks/Sign-Off of Section (TO)

QA Reviewer
QA Date
George du Plessis
Subject
Yes
No
N/A
Comments
General Information
Development ID is correct
Reference documents provided
Market has been clearly specified
Document contents
'Management Summary' complete and clear
Process Flow / Context complete and clear
Description of development complete and clear
'How the development will work' complete
Data volumes have been provided
Currency and UoM details have been specified
Language requirements have been specified
Security requirements have been specified
All assumptions have been documented
Security Spreadsheet has been completed
All Test Cases have been described in Appendix N
Overall: Functional Section Approved

Technical expertise on functional design
Performance :
Security :
Others :
Comments
337992532.doc
Page 12 of 45
Created: 21.07.2005
Printed: 27.05.2005 09:07
4 Overall Development Design (TO)

This development should extract Material Master data along with Classification details for
the materials from R/3 SOS box and prepare an IDoc.
This IDoc should be transported through the GLOBE Middleware (without change) to the
BEST middleware IAC. All conversion will happen either in IAC or BEST itself.
This development will require extension of the Idoc basic type MATMAS05. The
extension is to accommodate the Classification details of the material. The Classification details
can referred to the IDOC CLFMAS01.
Any change in the material master fields will trigger the Idoc through change pointers. The
complete Idoc needs to be sent incase of any new material is added or change in material data.
A new message type will be created for this IDOC.
Filters are set up in the distribution model for this new message type for the conditions.
Plant status (MARC-MSTAE):
Z2,Z3,Z4,Z5,Z6
all plants relevant for US16.
This is to send only the desired US material details to the BEST system.
Apart from that, for the Classification details, only those materials with the condition KLART =
001, should have classification details sent to BEST system.
4.1 Complexity, Estimates and Deadlines

Complexity
Estimat
Expected Delivery Dat
4.2
Medium
20 days
20-July 2005
Brief Technical Overvie
1) Idoc Extension:
An extension of the Idoc basic type MATMAS05 would be required in order to accommodate
the Classification details. But since there is already an extended IDOC:
/AMS/XAMX_MATMAS05 existing, the custom IDOC for this development will be a copy of
the same IDOC: /AMS/XAMX_MATMAS05 (ref: GDEVWR0002666 for more details on this
extension) instead of MATMAS05.
For this IDOC the classification details of the material will be attached. Basic Idoc for
Classification is CLFMAS01.
Suggested extension, segment type and fields:
Extension: /AMS/XUSX_MATMAS05
Segment type: /AMS/RUS_E1OCLFM as child segment of E1MARAM
Segment Fields Same Fields as in E1OCLFM of CLFMAS01
Segment type: /AMS/RUS_E1AUSPM as child segment of /AMS/RUS_E1OCLFM
/AMS/RUS_E1KSSKM as child segment of /AMS/RUS_E1OCLFM
/AMS/RUS_E1DATEM as child segment of /AMS/RUS_E1OCLFM
Segment Fields: Same fields as in E1AUSPM, E1KSSKM, E1DATEM of CLFMAS01
337992532.doc
Page 13 of 45
Created: 21.07.2005
Printed: 27.05.2005 09:07
User Exit
Additional fields need to be populated in the user exit EXIT_SAPLMV01_002.
Message Type
A new message type /AMS/RUS_MATMAS will be created for this development.
Change Pointers will be activated for message type /AMS/RUS_MATMAS using transaction
BD50.
Logic to populate the entire IDOC whenever there is a change in material data or new material
created:
1. Use the program rbdsemat program (BD11 transaction) to generate the complete Idoc
for the material that has been traced by the change pointers. This material can be found in
the BDCP table.
2. In the User exit- The logic for getting the Classification details for this material should be
written. The FM, CLA1_CREATE_CLFMAS, can be used for getting the classification
details. The Classification details will be extracted based on KLART (Material Class) =
001. Access the Logical system name from the table /AMS/XAMT_LOGSYS for the
message type /AMS/RUS_MATMAS. Add this logical system for the segment
'/AMS/XAM_LOGSYS' in the above created extension.
Distribution model and Partner Profile configuration requests are attached below:
Partner Profile
GDEVWR0008023....
4.3 ODC Readiness Checklist

Subject
General Information
Overall Technical Design completed
Final estimate provided
Work Order details specified in Nestool
Yes
No
N/A
Comments
Security
Functional specification checked by Security
Transaction code(s) defined
Authorisation objects(s) defined
Appendix M sent to Security team
For interfaces
Adapter requirements considered
Interface catalog updated
Testing
Test cases provided
Test data available
337992532.doc
Page 14 of 45
Created: 21.07.2005
Printed: 27.05.2005 09:07
4.4
MANDATORY - Development QA checklis
337992532.doc
Page 15 of 45
Created: 21.07.2005
Printed: 27.05.2005 09:07
5 Appendix C-1 : Interface (Between SAP and External

Systems)
5.1
Systems Diagram (FO)
GLOBE SAP
SOS BOX
AMS
Middleware
IAC (Legacy
Middleware)
BEST SAP
System
5.2 Business Data to be interfaced (FO)
Data Field
(Business Name)
Refer to the attached file for
IDoc structure based on an
existing IDoc type
/AMS/XAMX_MATMAS05
Business Rule
SAP Technical Field, if known
AMSXAMX_MATMAS0
5_d.htm
The interface should extract Material Master data only for finished products, semi-finished
products, raw and packaging material.
We need to extend/create and IDOC that does transfer also the Classification View (CLFMAS). This needs to be
included to be able to transfer the spend category classification of GLOBE to the product hierarchy of BEST.
CLFMAS segments need to be incorporated into IDOC.
The IDOC should be sent out in EDI format, if possible!
337992532.doc
Page 16 of 45
Created: 21.07.2005
Printed: 27.05.2005 09:07
337992532.doc
Page 17 of 45
Created: 21.07.2005
Printed: 27.05.2005 09:07
5.3
Interface Requirements (FO)
The source sytem is R/3 SOS box for Nestle USA market. The relevant fields are all the fields indicated in section 7.2.
Any mapping and data conversion must be done in IAC or BEST. The IDOC will be routed through the GLOBE
middleware unchanged.
5.3.1.1 Trigger (FO)

Background process scheduled to run daily at 12:00am (to be updated!!!1), extracting any deltas for new additions
and/or updates in Material Master relevant fields. Only the deltas for material type FERT and HALB, ROH and
ZPCK in Nestle USA plants is in scope for this functional specification.
IDOCs for Materials should only be sent to BEST if the plant-specific status is Z2, Z3, Z4, Z5 or Z6.
We do not want to send a material that has plant specific status Z1. We also only want to send materials
with material type FERT, HALB, ROH and ZPCK. An additional criteria is also the plant code. We only
want to send materials for plants that belong to NUSA company Code US16. As a further criteria we only
want to send the materials when the accounting view for the relevant plant has been created.
So if a material gets extended to a new plant and accounting view is not maintained for this new
plant we do not want to send it to BEST.
As a summary:
plant status (MARC-MSTAE):
Z2,Z3,Z4,Z5,Z6
all plants relevant for US16 (see attachment for details.
plants _27may.txt
This is status as of May27, major DCs ddd and Factories Plants

should be able to be maintained in a custom table to be flexible
for upcoming changes in the plant area.
Currently Sales Org., Purchasing Org and Distribution Channel are not part of the filters. This might
change after integrated testing.
Basically the job will loop trough the change pointer table BDCPV and create the IDOC if needed.
For the extraction of the classification data into the custom segment in the IDOC, data should be read from Table
AUSP with the key OBJEK, which represents the material including leading zeros. We only want the material
classification, so therefore we only select the class type KLART = 001.
It is currently in discussion if we should move all levels of the material classification into the IDOC. As of now
please move all levels into the IDOC.
Example Data for Classification:
337992532.doc
Page 18 of 45
Created: 21.07.2005
Printed: 27.05.2005 09:07
Select with OBJEK representing material with leading zeros (000000000043002616)

Result is something like this:
MANDT
103
103
103
OBJEK
000000000043002616
000000000043002616
000000000043002616
ATINN
0000003769
0000003921
0000003924
ATZHL
001
001
001
MAFID
O
O
O
KLART
001
001
001
ADZHL
0000
0000
0000
ATWRT
R1400000000
R1410200000
R1410000000
Material Classes:
ZPSC_RAW_SPENDCAT
ZPSC_PACK_SPENDCAT
Characteristics for Raw Class:
ZPSC_RAW_LEVEL1
ZPSC_RAW_LEVEL2
ZPSC_RAW_LEVEL3
ZPSC_RAW_LEVEL4
ZPSC_RAW_LEVEL5
Characteristics for Packing Class:
ZPSC_PACKAGING_LEVEL1
RAW_clas s .xls
337992532.doc
Packing_Clas s .xls
Page 19 of 45
Created: 21.07.2005
Printed: 27.05.2005 09:07
Receiving System (FO)

Receiving system is GLOBE middleware. It will be routed without changes to IAC and then to BEST.
5.3.1.2
Trigger (FO)
The data input would be triggered by a local scheduler, which will first look for the existence of the file pr.txt. If the
file is not found, it will check for it every hour
Volumes, Timing and Media (FO)

Country/Marke
USA
Frequenc
1 file per day (depending on the
testing)
Volume per ru
<1000 trans. per day on avg.
Comments
This is just a high level estimates.
File Layout Requirements (FO)

Refer to section 7.2, file layout should be the same as IDoc type /AMS/XAMX_MATMAS05
The mapping document to be used for the development of the IAC maps is attached below.
"Material
Interface_GLOBE to BEST Legacy Data Map (GDEVWR0008023).xls "
Control & Reconciliation Requirements (FO)

Needs to be updated!!!!!!!!!
Duplication handling (FO)

No special handling for duplicates needed.
Sequencing Requirements (FO)

Normal IDOC sequencing is ok , no special requirements.
File Retention Requirements (FO + TO)

No special requirements.
5.4
Error handling (FO)
The error handling for the outbound IDOC follows the GLOBE procedure where the relevant resolution group will have
to resolve .
Message adaptor will catch exceptions for sending applications. All exceptions will be reported to a centralized
notification and management facility.
337992532.doc
Page 20 of 45
Created: 21.07.2005
Printed: 27.05.2005 09:07
Failure for data transformation via middleware due to an illegal map or data
Failure to transmit from middleware to receiving applications
Possible error handling techniques include retries, email notifications to human users for inclusion in workflow, return
status from middleware call, or find workaround/do nothing until fault can be recreated.
Error
How error message should be

reported
Error message
Incomplete file
337992532.doc
Corrective Actions
Resend file with complete data
Page 21 of 45
Created: 21.07.2005
Printed: 27.05.2005 09:07
5.5 Technical Details (TO)

Globe Solution Lanscape Signature (MANDATORY) (TO)
Interface communicated to the ODC or BTC Interface Architect
"Scrap (5).s hs "
Interface Solution type (TO)

Idoc Type: /AMS/RUSX_MATMAS05
Idoc Interface
Interface Type
Message Type: /AMS/RUS_MATMAS
ABAP / Batch Interface

RFC Interface
Middleware Mapping
Required?
YES
Middleware Transmission
Required?
YES
Plug-In Interface Details
Plug-In Interface on SAP Side?
YES Specify
Plug-In Interface on MW Side?
YES Specify
Idoc
EDIFACT
Message Based
File Type of Input file
EANCOM
Other:
File Based
Idoc
EDIFACT
Message Based
File Type of Output file
EANCOM
Other:
File Based
Idoc Modifications (TO)

SAP Idoc Type:
SAP Idoc Segment:
SAP Idoc Extension
Field
(Business Name)
COPY OF THE SEGMENT
E1OCLFM of CLFMAS01
Basic Idoc
SAP Idoc Type:
337992532.doc
/AMS/RUSX_MATMAS05
/AMS/RUS_E1OCLFM
Y
Required Pos
Idoc field
(M/O
Field Name
Data Element
Format (Length)
/AMS/RUSX_MATMAS05
Page 22 of 45
Created: 21.07.2005
Printed: 27.05.2005 09:07
SAP Idoc Segment:

SAP Idoc Extension
Field
(Business Name)
COPY OF THE SEGMENT
AUSPM of CLFMAS01
Basic Idoc
SAP Idoc Type:
SAP Idoc Segment:
SAP Idoc Extension
Field
(Business Name)
COPY OF THE SEGMENT
DATEM of CLFMAS01
Basic Idoc
SAP Idoc Type:
SAP Idoc Segment:
SAP Idoc Extension
Field
(Business Name)
COPY OF THE SEGMENT
KSSKM of CLFMAS01
Basic Idoc
/AMS/RUS_AUSPM
Y
Required Pos
Idoc field
(M/O
Field Name
Data Element
Format (Length)
Data Element
Format (Length)
Data Element
Format (Length)
/AMS/RUSX_MATMAS05
/AMS/RUS_DATEM
Y
Required Pos
Idoc field
(M/O
Field Name
/AMS/RUSX_MATMAS05
/AMS/RUS_KSSKM
Y
Required Pos
Idoc field
(M/O
Field Name
(Logical) File Name details (TO)
ALE/EDI Configuration (TO)

xxx
Source System & Client or Logical System name
RD2DVR3103
Partner Profile
USENBEST01
Target System & Client or Logical System Name

Distribution Model
Message Type
Basic IDoc Type
IDoc Extension
Business Object / Methods
Process Code / Function Module
USENBEST01
/AMS/RUS_MATMAS
MATMAS05
/AMS/RUSX_MATMAS05
RD2DVR3103
Note: Since Material Master data being transferred(outbound) no process code required
Assignment of FM to Logical message and IDoc type
Function Module
FctTyp
BasicTyp
Log mess type
Obj type
Directn
Extension
MsgCode
Characteristics of inbound function modules
Function Module
Input type
Inbound process codes
Process Code
337992532.doc
MsgFunct
Dialog allowed
Process Code description
Page 23 of 45
Created: 21.07.2005
Printed: 27.05.2005 09:07
Link type and serialisation type of message type

Message type
Serialisation object type
Object type link
Workflow event linkages to be activated

Object type
Event
Receiver type
337992532.doc
Page 24 of 45
Created: 21.07.2005
Printed: 27.05.2005 09:07
SAP Data Mapping table (FO +TO)
5.5.1.1
Message to File Mapping (FO +TO)
IDoc Field Reference

IDoc Segment Field
Nam
Format
(Length
Req.
(M/O
The text file should

have the same
structure as IDoc
type
/AMS/XAMX_MAT
MAS05, which
details can be found
in section 7.2
SAP Field
Business
Name
Conversion
Rule /
Referenc
SAP Translation
Requirements
External Application File Layout

Positio
Field
(Business
Name)
Header Record
Technical nam
Format
(Length
Req (M/O
Additional Notes :
The mapping of existing IDoc type /AMS/XAMX_MATMAS05 to an external file in middleware is not part of this functional specification.
This will be done in the IAC (legacy middleware)
5.5.1.2
Conversion Rules (FO +TO)
No conversion required at the source data.

337992532.doc
Page 25 of 45
Created: 21.07.2005
Printed: 27.05.2005 09:07
Conversion Rule
5.5.1.3
Conversion Logi
Custom Tables (TO
NA
337992532.doc
Page 26 of 45
Created: 21.07.2005
Printed: 27.05.2005 09:07
5.6 Technical Details on ABAP-Development for the Interface (TO)

SAP Data Relationship Diagram (TO)
NA
Data Processing (TO)

Settings to be done for this object:
"Settings to be done
for this object.doc"
Create a FM: /AMS/RUS_MATERIAL_MASTER, to fill in all the Material Data for the
materials that are identified by the Change pointer.
LOGIC:
1) Setting the DATE and TIME:
Set the CREATION_DATE_HIGH and CREATION_DATE_TIME to current time
and date to access the change pointers and get the materials that are changed or
created accordingly before the current date and time.
2) READING THE CHANGE POINTERS:
Call the FM: CHANGE_POINTERS_READ
Pass the parameters Current date, current time, Message type
/AMS/RUS_MATMAS) and read_not_processed_pointers as X.
Get all the Change pointer contents into an internal table i_Change_pointer (of
type bdcp).
If the i_Change_pointer is empty, then do not process any empty idoc. Stop the
processing.
Call Function module K_WERKS_OF_BUKRS_FIND, exporting Company

code US16 and getting the itab_001w contents into I_WERKS internal table. This
gives all the Plants associated to a particular Company code US16. This is done,
to filter out all the materials not belonging to US16.
Select all the materials from MARC table which belong to the Plants in
I_WERKS table.
Check if the material that is getting changed/created or updated ( field i_rmclfmatnr), is present in the materials selected from MARC table.
337992532.doc
Page 27 of 45
If the Material is present, then continue with the next step, else delete that material
from I_changpointer table as IDOC is not to be created for the same.
3) FILING THE SELECTION SCREEN FOR PROGRAM RBDSEMAT (BD11

Transaction):
Create an Internal table i_selection (type rsparams) to fill in the selection screen
details.
For all the records in the internal table i_change_pointer, extract the material
number i.e. field cdobjid.
Fill this material in the selection screen field MATSEL of the program rbdsemat.
Fill in the Message type (/AMS/RUS_MATMAS) in the field MESTYP of the

program rbdsemat.
Populate these details in the internal table i_selection accordingly.
Submit this internal table to the program rbdsemat to create the entire Material
IDOC.
Create a FM: /AMS/RUS_MAT_CLASSIFICATION, to fill in all the Classification Data for

the materials that are identified by the Change pointer.
This Function module is triggered whenever the User Exit EXIT_SAPLMV01_002 is called.
For this Populate the table /GLB/RGTUSEREXIT creating a new entry giving the User exit
identifier and the function module /AMS/RUS_MAT_CLASSIFICATION name.
LOGIC:
1) Check if the Segment name is E1MARAM.
Only for this segment the FM /AMS/RUS_MAT_CLASSIFICATION should be
Triggered, as the Classification segments are child segments for E1MARAM.
2) Reading the IDOC_DATA table
Read the IDOC_DATA internal table where the segnam = E1MARAM.
If the segment name is found, Move the contents to a workarea i.e:

struct_e1maram (type e1maram) = idoc_data-sdata
Extract the matnr (material number): struct_e1maram-matnr.
Access the table AUSP where OBJEK = STRUCT_E1MARAM-MATNR and

KLART = 001 into an internal table i_ausp.
337992532.doc
Page 28 of 45
If the record is found, then Call the FM 'CLA1_CREATE_CLFMAS'

EXPORTING
object
= i_ausp-objek (material number)
class_type
= i_ausp-klart (001)
type_of_classification = i_ausp-mafid
TABLES
t_idoc_data
= i_idoc_data.
Append the internal table I_IDOC_DATA (which has all the classification
details for a particular material number), to IDOC_DATA.
Modify the segment names to the custom segment names while appending it to
IDOC_DATA.
E.g.: IF i_idoc_data-segnam = 'E1OCLFM' then
idoc_data-segnam = '/AMS/RUS_E1OCLFM'.
Since the Logical system is a mandatory field, get the logical system (field
Logical_System) name from the table /AMS/XAMT_LOGSYS where the
message type is /AMS/RUS_MATMAS. If the record is found, append the
segment name = '/AMS/XAM_LOGSYS' and the value contained in field
Logical_System to SDATA in the IDOC_DATA table.
Create a FM: /AMS/RUS_EDIMAT_PATHNAME, to download the IDOC that is created

above to the application server.
The path used for this is: /zdata/RD2/us/usenbest01/glb/ppomatma01
The other details are: Interface ID: PPOMATMA01
Parameter: USENBEST01
Logic:
1) For the message type = /AMS/RUS_MATMAS, call the function module
/NESGLB/X_INTERFACE_START_PROC exporting:
bukrs
= us16
intid
= usenbest01
parnum
= ppomatma01
and importing the
physical_filename
= v_pathname
header
= wa_header
If the Call is not successful, then set the status to 3-Failure, else set the status to 2
(success)
2) Call the Function module: /NESGLB/X_INTERFACE_END_PROC, toclose the
interface, exporting header
= wa_header
status
= v_status
recct
= Dummy value
trans
= Dummy value
errct
= Dummy value
337992532.doc
Page 29 of 45
Create a FM /AMS/RUS_MATERIAL_UDPATE_BDCP: This is called for the USER EXIT

EXIT_SAPLCLFM_002. This is to create an entry in the table BDCPV for the custom message
type /AMS/RUS_MATMAS, whenever a change is done to a material classification details.
LOGIC:
1) Call Function module K_WERKS_OF_BUKRS_FIND, exporting Company code US16

and getting the itab_001w contents into I_WERKS internal table. This gives all the
Plants associated to a particular Company code US16.
2) Select all the materials from MARC table which belong to the Plants in I_WERKS table.
3) Check if the material that is getting changed/created or updated ( field i_rmclf-matnr), is
present in the materials selected from MARC table.
4) If the material is not present, then ignore that material. But if the above check was
successful, then fill the record for the internal table as below:
i_cp_data-tabname = Table name-MARA
i_cp_data-tabkey = i_rmclf-matnr (Material Number)
i_cp_data-cdobjcl = CLASSIF- Object Class
I_cp_data-cdchgid = U (update mode)
5) Calling the function module as below, to write the changes directly to the
BDCPV/BDCP/BDCPS table for the custom message type, for all the Materials whose
classification data was changed
CALL FUNCTION 'CHANGE_POINTERS_CREATE_DIRECT'
EXPORTING
message_type
= /AMS/RUS_MATMAs
"Custom message type
TABLES
t_cp_data
= i_cp_data
5.7 Quality Assurance Remarks/Sign-Off of Section (TO + QA)

QA Reviewer
QA Date
George du Plessis / Harsha Jadhav
/ July 20, 2005
Subject
Yes
No
N/A
Comments
Functional Section
Systems Diagram provided
Business Data and rules provided
Sending System has been specified
Receiving System has been specified
Data Volumes and Timing details provided
File layout requirements provided
Control and reconciliation requirements provided
337992532.doc
Page 30 of 45
Duplication handling requirements provided

Sequencing requirements provided
File retention requirements provided
Technical Details
Interface solution type specified
IDoc modifications specified
(Logical) file name details provided
ALE/EDI Configuration specified
SAP data Mapping provided
SAP data relationship diagram provided
ABAP development details have been provided
GSL signature for interfaces provided to BTC
Interfaces Architect
Comments
337992532.doc
Page 31 of 45
6 Appendix C-2: Middleware

There are two middleware involved in the interface.
GLOBE Middleware: No mapping
BEST Middleware: a.k.a. IAC. Mapping maintained on IAC.
SAP program generates data in Idoc format and downloads it to the EDI port (File port) to an
pre defined zdata directory, from where Globe middleware will route the file to IAC middleware.
IAC middleware will read the file in EDI format and convert it the required Idoc format and posts
it the BEST system. There is no data transformation required in Globe Middleware hence for
Globe MW it is an Bypass transaction.
Mercator Transaction ID
011052
Purpose of the Map
NA
Sending Application/System
SAP SOS Box
Receiving Application/System
IAC Middleware
Middleware Hub Version
6.7
Configuration Requirements
Standard V1.5 configuration in the AIX system
Org ID : US16
External Partner : USENBEST01
Interface Id : PPOMATMA01
Zdata path : /zdata/RD2/us/usenbest01/glb/ppomatma01/arc
6.1 File In (FO + TO)

The Middleware accept IDOC file generated by SAP System.
See section 5.5.1.1 for the file details.
6.2
File Out (FO + TO
No changes will be done to the file received. The fille will simply be forwarded to the IAC system.
This will be a text file sent by the Middleware to the receiving system.
The structure of the file will have no headers nor any footers. One record for each Material Master layout detail in
section 5.5.1.1
No duplicates allowed.
6.3
Middleware Message Routing Rules (FO + TO
Sending Syste
Routing Rule
Destination Syste
SAP SOS Box (SID : 011035)
No specific routing, always send
IAC Middleware (DID : 002201)
337992532.doc
Page 32 of 45
data to IAC Middleware
337992532.doc
Page 33 of 45
MW Data Mapping table (TO + FO

Not applicable.
6.3.1.1
Message to File Mappin
Additional note
6.3.1.2
Message to Message Mappin
Not applicable.
6.3.1.3
Conversion Rule
6.3.1.4
Look Up Table
6.4
Middleware Flow Diagram (TO)

GLOBE Middleware Bypass
SAP R/3
FI BOX
(BOX
CHANG
E
ACCEP
337992532.doc
TED BY
GC
MAY 18,
2005)
IDOC
IDOC format
Flat File
IAC
Mappin
g to
BEST
format
Page 34 of 45
BEST
R/3
Created: 21.07.2005
Printed: 27.05.2005 09:07
6.5
Error handling (MWTO
-NAError
How error message should be

reported
Error message
Corrective Actions
6.6 Adapter Details (MWTO)

SAP Adapter Details (MWTO
GAF Adapter
Legacy/Complementary Application Adapter Details (MWTO)

IAC Adapter
337992532.doc
Page 35 of 45
Created: 21.07.2005
Printed: 27.05.2005 09:07
6.7 Middleware interface values (MWTO)

Source ID
Transaction ID
Delivery ID
Application ID
User Serial key
6.8
011035
011052
002201
NA
NA
Mapping (MWTO
-NAInput / Output card descriptio

6.8.1.1
Input card
6.8.1.2
Output card
Functional map descriptio
Special map feature

337992532.doc
Page 36 of 45
Created: 21.07.2005
Printed: 27.05.2005 09:07
6.8.1.3
PUT function
6.8.1.4
FAIL function
6.9 Middleware configuration (MWTO)

Broker/ MQ-Hub configuration file
OutTransactionMap.dat
AD|US16|USENBEST01|PPOMATMA01|011052|1|
Interfaces.cnf
AD|011035|011052|1|Y|AD|002201|N|0110052|B|
337992532.doc
Page 37 of 45
Created: 21.07.2005
Printed: 27.05.2005 09:07
iView Detailed Solution Design Specification
6.10 Qual. Assurance Remarks/Sign-Off of Section (TO + MWQA)

QA Reviewer
QA Date
Usman Basha
20/07/2005
Subject
Yes
No
N/A
Comments
Functional Section
Priority/Criticality data specified

Sequencing requirement in the MW have been
defined/error handling
Technical Details
All mapping information provided
All routing information provided
Maximum message size specified

Serialization and Batch processing
requirements specified
File in structure and location defined
File out structure and location defined
Data Mapping table is consistent with ALE
objects and complimentary application
file/message structure
Middleware Conversion rules are clearly
detailed
All structures and known values defined in
Lookup tables (exact structure of the lookup
files should have been defined). Name should
be included as well.
Adapter details have been specified and
validated by the Middleware Team
Comments
337992532.doc
Page 38 of 45
Created: 21.07.2005
Printed: 27.05.2005 09:07
7
7.1
Appendix M: MANDATORY - Security (TO + FO +SO

Transaction code (TO)
Transaction Code
7.2
Description
Authorisation object (FO + SO)
No authorization objects requested by the (FO)

If No - Expertise of (TO) :
Authorization objects
Object
Fields
7.3
Text
Field Description
Field Values checked in development
Development-specific test-users create (SO)
Positive testing
User-ID
WR0000xxxPOS
Object Values Checked
Negative testing
User-ID
WR0000xxxNEG
337992532.doc
Object Values Checked
Page 39 of 45
Created: 21.07.2005
Printed: 27.05.2005 09:07
8 Appendix N: MANDATORY - Testing

8.1
Functional Test Cases (FO
Positive Tests
Test Case
PT1
PT2
Test Case Description

Perform a change on a US material
a. Delete a US material.
b. Add a US material.
c. Change a US material.
Verify the information about finished goods in
SAP database for specific
Run standard SAP transaction to download a
number of US materials.
Expected Result
US Material IDOCs generated
CD Comments
A US Material IDOC for each material is created.
Run transaction BD21, with message type

/AMS/XAM_MATMAS
Negative test
Test Case
NT1
NT2
337992532.doc
Test Case Description

Perform a change on a non-US material
Run standard SAP transaction to download a
number of US materials
Expected Result
No US Material IDOCs are generated for the non-US materials
No US Material IDOCs are generated.
Page 40 of 45
Created: 21.07.2005
Printed: 27.05.2005 09:07
CD Comments
8.2
Technical Test Cases (TO
Test Case
P1
Description
Test for
change in the
US material
Steps
Goto MM02 in
RD7 server,
change a
existing US
material
details.
Then go to
BD21 and run
the Message
type
/AMS/XUS_M
ATMAS.
(Objec trun in
SOS box)
Test Data
Chose any existing
material belonging to
US.
Eg: 12000146
Expected Result
An Idoc should be
created. If it has
material Class (i.e
KLART 001), then
the classification
details will also be
populated alongwith
the material master
data.
Actual Result/Remarks
An Idoc should be
created. If it has
material Class (i.e
KLART 001), then
the classification
populated alongwith
the material master
data.
No test data
Tes t1.doc
s teps .doc
P2
337992532.doc
Test for
creating a
new US
material
Goto MM01
and create a
new material
belonging to
US. Then go to
BD21 and run
the Message
type
/AMS/XUS_M
ATMAS.
(Objec trun in
SOS box)
Create a new Material

using MM01
Page 41 of 45
Created: 21.07.2005
Printed: 27.05.2005 09:07
Executed By/Date
24.08.2005
Shilpa Reddy
Test Case
P3
N1
337992532.doc
Description
Test for
change in the
US material:
Bunch of
materials
Change
Material not
belonging to
a US16 Plant
Steps
Goto MM02 in
RD7 server,
change the
below existing
US material
details.
Then go to
BD21 and run
the Message
type
/AMS/XUS_M
ATMAS.
(Objec trun in
SOS box)
PLEASE
FOLLOW THE
STEPS AS IN
P1.
Run BD21 for
the Message
type
/AMS/XUS_M
ATMAS.
(Objec trun in
SOS box).
Follow the steps
as in P1
FERT
HALB
ROH
ROH
Test Data
12000138
44002517
44002520
44051404
Material:
44051391 or
44051350
Page 42 of 45
Expected Result
An Idoc should be
created for all the
materials. If it has
material Class (i.e
KLART 001), then
the classification
populated alongwith
the material master
data.
Actual Result/Remarks
Tes t1.doc
No idoc should be
generated
24.08.2005
Shilpa Reddy
res ult.doc
Created: 21.07.2005
Printed: 27.05.2005 09:07
Executed By/Date
24.08.2005
Shilpa Reddy
Appendix O: MANDATORY - Object documentation-(DEV)
9.1 SAP Development Objects (DEV)

Object type
Function group
Function Modules
Function Modules
Function Modules
Message Type
Extension
Segments
Segments
Segments
Segments
Function Module
Object Name
/AMS/RUSFC_MATERIAL
/AMS/RUS_MATEDI_PATHNAME
/AMS/RUS_MATERIAL_MASTER
/AMS/RUS_MAT_CLASSIFICATION
/AMS/RUS_MATMAS
/AMS/RUSX_MATMAS05
/AMS/RUS_E1OCLFM
/AMS/RUS_E1KSSKM
/AMS/RUS_E1AUSPM
/AMS/RUS_E1DATEM
/AMS/RUS_MATERIAL_UDPATE_BDCP
9.2 General Information (DEV)

Development Type
Transaction Code
Development Class
Message Class
337992532.doc
Interface
NA
/AMS/GFAMFC
NA
Page 43 of 45
Created: 21.07.2005
Printed: 27.05.2005 09:07
9.3 Setting Information (DEV)

Environment
Development
Mono
Split
Description
Setting Information
CTS Transport
1) RD2K976796
DEV_TEST
Package
DEV_TEST
Package
Package
LCD_FIC_CD
GDEVWR0008023 Material
Interface for NUSA
Dev Test (For imports only
into RD2.172, RDI, RD7, &
RDH)
LCD_FIC_CD
GDEVWR0008023 Nusa
Config Details
RDH)
/AMS/GFAMFC
RD2
RD2
/AMS/GFAMFC
3) RD2K978071
RD2
RD2
/AMS/GFAMFC
2) RD2K978549
DEV_TEST
LCD_FIC_CD
GDEVWR0008023 Material
Interface for NUSA
RDH)
RD2
RD2
Configuration Required
CTS No. for Custom Tables
Dependency on other GDEVWR
Custom Tables
337992532.doc
Page 44 of 45
Created: 21.07.2005
Printed: 27.05.2005 09:07
QA
RT
PreProd
Prod
9.4 Interface Information (DEV)

Environment
Development
Mono
Split
Description
Interfaces
ALE Configuration
NA
Logical System
Partner Profile
Distribution Model
Change Pointer Set Up
NA
Physical Directories
NA
Batch Job Creation
NA
NA
Migration of Maps
GLOBE Standard Control NA
Tables (Flat Files)
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
9.5 Non-SAP Development Objects (DEV + MWDEV) NA
337992532.doc
Page 45 of 45
Created: 21.07.2005
Printed: 27.05.2005 09:07
QA
RT
PreProd
Prod

GDEVWR0008023 Material Master Interface (GLOBE To BEST) FS - TS - 12 - 17082005 - Updated

Uploaded by

Document Information

Original Description:

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

GDEVWR0008023 Material Master Interface (GLOBE To BEST) FS - TS - 12 - 17082005 - Updated

Uploaded by

Copyright:

Available Formats

Development Specification

Brief development descriptio

Material master interface (GLOBE to BEST)

Business Process Level 3 or 4

Process Purchase Order

Benny Jiang, Carsten Link

Benny Jiang, Carsten Link

mySAP component /module

Read the General Guidelines

Description of change (including the

Add requirements to include raw and

QA reviewer (for messaging: both Messaging and AD)

Developer. Covers also some TO activities on his behalf.

Middleware Technical Owner

Technical Owner Messaging Messaging Coordinator

Technical Owner Development AD Development Coordinator

Details on the development process can be found in : Developement Process

For Messaging Only:

Management Summary (FO).....................................................................................

Process Flow / Context (FO)....................................................................................

Functional Requirements (FO).................................................................................

Overall Development Design (TO).........................................................................

Appendix C-1 : Interface (Between SAP and External Systems).......................

Appendix C-2: Middleware.....................................................................................

Appendix M: MANDATORY - Security (TO + FO +SO).........................................

Appendix N: MANDATORY - Testing.....................................................................

Appendix O: MANDATORY - Object documentation- (DEV)...............................

9.1 SAP DEVELOPMENT OBJECTS (DEV)...........................................ERROR! BOOKMARK NOT DEFINED.

Management Summary (FO

Process Flow / Context (FO)

3 Functional Requirements (FO)

Description of the development (FO)

This is status as of May27, major DCs and Factories Plants

How the development will work (FO)

Where this development will be run (FO)

How the development will be run (FO)

SAP General Requirements (FO)

Data Volume (FO)

Language considerations (FO)

Currency and Units of Measure (FO)

3.5 Quality Assurance Remarks/Sign-Off of Section (TO)

Overall: Functional Section Approved

4 Overall Development Design (TO)

4.1 Complexity, Estimates and Deadlines

Brief Technical Overvie

4.3 ODC Readiness Checklist

MANDATORY - Development QA checklis

5 Appendix C-1 : Interface (Between SAP and External

Systems Diagram (FO)

5.2 Business Data to be interfaced (FO)

SAP Technical Field, if known

Interface Requirements (FO)

5.3.1.1 Trigger (FO)

This is status as of May27, major DCs ddd and Factories Plants

Select with OBJEK representing material with leading zeros (000000000043002616)

Receiving System (FO)

Volumes, Timing and Media (FO)

File Layout Requirements (FO)

Control & Reconciliation Requirements (FO)

Duplication handling (FO)

Sequencing Requirements (FO)

File Retention Requirements (FO + TO)