An outline of the GCS Verification system

27. Jan. 2004

Corporate Industrial Sales Division
Corporate Information Systems Company

Fig.1 Basic concept of GCS Verification

Master admin 1) register Global

2) inform Code
System
Code admin

3) distribute
4) register

GCS Copy
R/3 Keep Verified Data Base
Model Partner - Prevent the local codes
Master Master
- Copy the properties from
GCS copy DB to R/3 master

1
Contents

1. System background and objectives

2. System Scope
3. Process Outline
4. Screen image
5. Extent of Impact in R/3, Unix
6. Appendices

2
1. System background and objectives
Background
• In order to improve the accuracy of PSI data and reduce the number of P/O errors a
foolproof unified global code infrastructure needs to be put in effect immediately across the
Matsushita Group.
• In reality, it is currently not possible for each company to conduct real or pseudo-real time
checks against the GCS original master and no concrete solution has yet been put forward .

Strategy
• Furnish each site with a copy of the original GCS trading partner masters.
• Develop and provide a real time check/query function, commonly defined for industry, to
each site. This will be based on a function built for checking material codes, to directly
access the local GCS copy database from SAP.

Objectives
• Complete Industry HQ control of codes used in company systems, specifically, not allowing
local trading partner codes nor local material codes to be registered within Matsushita
Group.
• Replace current manual controls with systematic controls.
• Simplify registration of trading partner data and material data in SAP as much as possible
by applying data registered in GCS.

3
2-1. System scope – System targets
Target master
• The target masters for this validation system is:-
- Model master
- customer and vendor master (except “Non trading partner” type).

Function and data

• The basic function of this system is to check whether a SAP trading partner code /
model code exists in the GCS copy DB.

4
2. System scope
Fig.2 - Basic data distribution flow and development criteria for material code validation
Applicant division GCG Server
(1) Global Code registration GCS Host
on GCS system
REAL TIME Application data
Global Code GCS
GCG BATCH GCS
Server Original
JOB*

Scope of system
Function outline:- (2) Return Global Code
1) Access to the GCS copy database.
2) Validate the code input by user against global Maintenance data
codes in GCS copy.
3) Copy attributes (like description, category and SEMI-REAL
address) from GCS copy automatically when MA ICC GIS Server TIME
valid match found.
4) Activate the “Global Flag” when valid match (3) Update the GCS copy
found.

GCS GCS copy

Overseas company Copy MQ MQ for distribution
SEMI-REAL
(3) Master registration GIS TIME
Connecting
on company side System
GCS Function
Master
Global code
Maintenance Online : Real time (using RFC)
Menu Validation Batch : To be scheduled by sales company (using FTP)
*GCS batch job runs every 2 hours in daytime, JST.
SAP R/3 The job doesn’t run during host machine maintenance, which
takes place overnight, JST.
See “7. Issues: GCS restrictions” for details.

5
3. Process Outline <online>
Fig.3 - Process flow for on-line registration of new master in SAP

SAP R/3 GCS Copy System

Add-on screen
Enter code and essential items
1 e.g.) - Material Type
- Account group - Reference code

GCS Function
Call GCS query function with key
2 data above.
Query GCS copy
RFC 3 database and GCS copy
return results. database
Receive results from
4 GCS query function.

Was connection
5 Output error
Connection failure. No
message and
successful? No display dialogue. Register anyway?
Yes Yes
Does code exist 6 Output message
and return to initial
in valid period?
No screen.
Yes
Set global code and other data can Set “Pending” flag
7 be copied from GCS copy 8 on standard
on screen. screen.

Standard master registration screen

6
3. Process Outline <batch>
Fig.4 - Process flow for code verification process(Batch)

SAP R/3 GCS Copy DB Server

Standard job scheduler
Execute update
1 job according to
schedule.
Schedule 1
(SAP JOB)
00-MM-GCS-MAT-MAS-EXTRACT

Extract master
2 records according
to search criteria.
R/3
Master
Schedule 2
(Cron-Job)
Pass extracted GCS Function /home/iccgcs/SAPtoCCH70.sh

3 records to GCS
validation function. FTP
Match data against
4 GCS copy DB and GCS copy
return results.
Schedule 3 database
(SAP JOB)
00-MM-GCS-MAT-MAS-S&OP-SYNC FTP
Update R/3
5 master with GCS
function results.
R/3
Master

Output log of all

6 changes made. Spool data

7
4. Screen image < Customer - online >
1. Initial screen 2. Normal result (General data - Address 1)
Trading Partner
Name

Trading Partner
Short Name

2. Normal result (General data - Address 3)

2. Normal result (General data - Address 2)

Telephone
Global Flag Expiration Date
number

FAX number

Address

Telex number

8
4. Screen image < Customer - online > (cont’d)
3. Error messages
1) Duplicate 5) DB error (can be registered with “Pending” status)

2) Not found in GCS

6) Other error (can be registered with “Pending” status)

3) Expired

4) (notice only) account group is out of scope of GCS check

9
4. Screen image < Customer - batch >
1. [Extraction] order screen 2. [Extraction] process log in JOB spool

3. [Synchronization] order screen 4. [Synchronization] process log in JOB spool

10
4. Screen image < material - online >
1. Initial screen

2. Result (Basic data 2)

Global Flag
2. Result (Basic data 1)
Description

G-CAT+D-CAT
“01” if [valid from] is
Expiry Date+1
not blank
Status Table
Global 001
Pending 002
Out Of Date 003
No G-Cat/D-Cat 004
11
4. Screen image < material - online > (cont’d)
3. Error messages
1) Not found in GCS(can be registered with “Local” status)

3) Expired(can be registered with “Global” status)

5) Other error (can be registered with “Local” status)

3) G-CAT or D-CAT is blank or not found in GCS

(can be registered with “Global” status)

4) DB error (can be registered with “Local” status)

12
4. Screen image < material - batch >
1. [Extraction] order screen 2. [Extraction] process log in JOB spool

3. [Synchronization] order screen 4. [Synchronization] process log in JOB spool

13
５ . Appendices (1)
GCS restrictions
Service Hours
1) It is available to inquiry and register codes with your PC for 24 hours/day basically. 　
　 * Suspended from 12:00AM, Sunday to 8:00AM, Monday
2) Data is registered officially on GCS Host system about 30 minutes after process time specifying below.
* Data is transmitted from GIS server to GCS Host system 10 times per day.
Therefore, the data, which is inputted from 24:00 to 8:00(JST), will be registered officially at 8:30(JST).
<Process time of data transmission>

Process Process Time difference

Number Time (JST)
Singapore Hamburg New York

1 8:00 7:00 24:00 19:00

2 10:00 9:00 2:00 21:00
3 12:00 11:00 4:00 23:00
4 14:00 13:00 6:00 1:00
5 16:00 15:00 8:00 3:00
6 18:00 17:00 10:00 5:00
7 20:00 19:00 12:00 7:00
8 22:00 21:00 14:00 9:00
9 24:00 23:00 16:00 11:00 This page refer from HP of Global C ode
14 <http://iweb.mei.co.jp/cont/gcdtop/manual/index_tpreg/manual_130.html>
6. Appendices (2)
Effect of GCS restrictions (Service Time)
a) Case of PIA : GCS (Partner) registration or modification always reflect GCS copy DB within 2 hours.
Singapore Time 8:00 9:00 10:00 11:00 12:00 13:00 14:00 15:00 16:00 17:00 18:00

GCS (Part.) GCS (Part.) GCS (Part.) GCS (Part.) GCS (Part.) GCS (Part.)

PIA Registration
Modification
Registration
Modification
Registration
Modification
Registration
Modification
Registration
Modification
Registration
Modification

Japan Time 8:00 9:00 10:00 11:00 12:00 13:00 14:00 15:00 16:00 17:00 18:00 19:00 20:00 21:00 22:00 23:00 24:00

Batch
Batch

Batch

Batch

Batch

Batch

Batch

Batch

Batch
GCS
Host
b) Case of PIE : GCS (Partner) registration or modification reflect GCS copy DB within 2 hours till 15 o’clock. The rest reflect next day.
London Time 8:00 9:00 10:00 11:00 12:00 13:00 14:00 15:00 16:00 17:00 18:00

GCS (Part.) GCS (Part.) GCS (Part.) GCS (Part.) GCS (Part.) Registration Modification
PIE Registration
Modification
Registration
Modification
Registration
Modification
Registration
Modification
->Reflect GCS Copy DB by next day

Japan Time 16:00 17:00 18:00 19:00 20:00 21:00 22:00 23:00 24:00 1:00 2:00 3:00 4:00 5:00 6:00 7:00 8:00

Batch
Batch

Batch

Batch

Batch

Batch
GCS
Host
c) Case of PIC : GCS (Partner) registration or modification reflect GCS copy DB within 2 hours till 11 o’clock. The rest reflect next day.
New York Time 8:00 9:00 10:00 11:00 12:00 13:00 14:00 15:00 16:00 17:00 18:00

GCS (Part.) GCS (Part.)

GCS (Part.) Registration Modification
PIC Registration
Modification
Registration
Modification
->Reflect GCS Copy DB by next day

Japan Time 20:00 21:00 22:00 23:00 24:00 1:00 2:00 3:00 4:00 5:00 6:00 7:00 8:00 9:00 10:00 11:00 12:00

Batch
Batch

Batch

Batch

Batch

Batch
GCS
Host
15