White Paper GTS R3 Integration

The following list describes configuration and master data objects that must be setup in
GTS to support the integration with an R3 system. If these items are not setup in GTS,
then the R3 transactions will be blocked for subseuent processing.
!ontracts " sales orders cannot be deli#ered
$eli#eries cannot be picked, packed or goods issued
%urchase orders cannot be in#oiced &new as of '.( as a result of integration with
finance)
Object Configuration
vs. Master Data
Type of Block Resolution
!ompany !ode !onfiguration
and *aster $ata
Technically
Incomplete
!reate +T, as business partner
-ssign !! to +T, in configuration
%lant !ode !onfiguration
and *aster $ata
Technically
Incomplete
!reate .egal /nit as business partner
-ssign plant to legal unit in configuration
!ustomer does
not e0ist
*aster $ata Technically
Incomplete
Transfer customer master from R3 system
to GTS1 ck transfer log and fi0 any errors
!ustomer
missing
*aster $ata Technically
Incomplete
-dd the rele#ant business partner&s) to the
transaction. The transaction must contain
this information to fi0 the error.
2endor does
not e0ist
*aster $ata Technically
Incomplete
Transfer #endor master from R3 system to
GTS1 ck transfer log and fi0 any errors
2endor missing *aster $ata Technically
Incomplete
-dd the rele#ant business partner&s) to the
transaction. The transaction must contain
this information to fi0 the error.
*aterial does
not e0ist
*aster $ata Technically
Incomplete
Transfer material master from R3 system
to GTS1 ck transfer log and fi0 any errors
*aterial
missing
*aster $ata Technically
Incomplete
-dd a material to the transaction item&s).
The transaction must contain this
information to fi0 the error.
%artner
+unction does
not e0ist
!onfiguration Technically
Incomplete
-dd partner function&s) to the appropriate
configuration setting
!ountry !ode *aster $ata 3locked
$ocuments
-dd country code to country code table
and assign to proper country code group
*aterial
!lassification
*aster $ata 3locked
$ocuments
-dd proper classification code to GTS
product master for all rele#ant legal
regulations or set 4no control5 flag to
bypass license checks
.icense *aster *aster $ata 3locked
$ocuments
!reate license master with rele#ant data
and run re6determination or manually
assign any license master
S%. 3locked
$ocuments
Release the document from S%. hold
without releasing the blocked partner
7mbargo 3locked Release the document from embargo hold
%age 8 of 3
White Paper GTS R3 Integration
$ocuments without remo#ing the embargo flag for the
country
If the +T, and .egal /nit do not represent the standard GTS data mapping 9 i.e.
company code to +T,, plant code to .egal /nit 9 then early de#elopment work to map
the proper R3 data elements to these GTS organi:ational elements might need to take
place. If this cannot be done in the needed time frame, then the standard GTS mapping
must be setup e#en though it does not represent the actual organi:ation structure.
If a material cannot be added to the R3 transaction and the R3 transaction cannot be
ignored for GTS processing, then a 4dummy5 material number must be added to the
transaction in the interface to GTS. This is accomplished #ia a user e0it &de#elopment
work). In order for this to work, the 4dummy5 material must e0ist as a product master in
GTS associated with the rele#ant R3 feeder system. Therefore, the R3 system must also
setup this material, and then transfer it o#er to GTS.
;hile dummy business partners can be setup in the same manner as a dummy material, it
does not make sense to do this. In reality, an actual partner is truly in#ol#ed in the
transaction and is reuired data in R3. The scenario where a partner might not e0ist in a
transaction sent to GTS is during early procurement acti#ities. Sometimes, a #endor is
not known at the time a purchasing reuest is made. ;hen this happens, the transaction
will be blocked in R3, as well as, GTS. 7#en if GTS was not acti#ated, subseuent
processing in R3 could not take place until a #endor is added. So, the most effecti#e
solution to this issue is to add a partner to the R3 transaction 9 one would ha#e to be
added e#entually.
In addition to the items listed abo#e that need to be setup in GTS, the following
information must also be a#ailable to facilitate the transferring of master data.
If any of the following data is missing, the master data cannot be transferred successfully
to GTS. The errors must be fi0ed in the appropriate systems 9 which could be R3 or GTS
or R3 and GTS. Then master data must be re6transferred to GTS from R3.
Item Master
Data
Object
Configuration
vs. Master
Data
Resolution
!ountry
!ode
!ustomer !onfiguration
and"or *aster
$ata
7nsure country code is defined in T((<1
ensure business partner master contains
country code in address
IS, !ountry
!ode
!ustomer !onfiguration 7nsure IS, country code is defined in
T((< to country code in R3 and GTS
Region !ode !ustomer !onfiguration
and"or *aster
$ata
7nsure region code is defined in T((<S1
ensure business partner master contains
region code in address
%ostal !ode !ustomer !onfiguration
and"or *aster
7nsure business partner master contains
postal code1 ensure R3 and GTS ha#e
%age = of 3
White Paper GTS R3 Integration
$ata same country code rules in T((<
/,* 9 base
or alternate
or weight
*aterial !onfiguration
and"or *aster
$ata
7nsure base, weight and alternate /,*
are defined in T((>
IS, /,*
!ode
*aterial !onfiguration 7nsure IS, /,* code is defined in
T((>I in R3 and GTS and is assigned to
/,* in T((> in both GTS and R3
Key actors to consi!er in "T# Implementation $lan Regar!ing Integration to R%
#ystems
*inimi:e number of en#ironments for testing prior to 4go li#e5 in order to
minimi:e impact on other R3 acti#ities and number of times GTS data setup is to
be setup
.oad all master data and fi0 all errors in each en#ironment prior to acti#ating
!ompliance acti#ities in GTS
$efine and map all +T, and .egal /nits in GTS prior to acti#ating !ompliance
acti#ities in GTS
?a#e all de#elopment work completed for +T, and .egal /nits prior to
acti#ating !ompliance acti#ities
?a#e all country codes defined in GTS and assigned to country groups prior to
acti#ating !ompliance acti#ities
?a#e 4dummy5 material process in place prior to acti#ating !ompliance licensing
acti#ities
!lassify as many materials in GTS as possible up front prior to acti#ating
!ompliance licensing acti#ities
$e#elop a S.- with the people working on R3 initiati#es for supporting them
Include Regression Testing for R3 processes as part of implementation plan
%age 3 of 3