ATLAS_AES_Futrelle_1313_v3.pdf

7/27/2019 ATLAS_AES_Futrelle_1313_v3.pdf

http://slidepdf.com/reader/full/atlasaesfutrelle1313v3pdf 1/17

]

Orange County Convention Center

Orlando, Florida | May 15-18, 2011

Smooth Path to Electronic AES Filing in GTS

Robert Adams: Cooper Industries

Greg Futrelle: EntryPoint Consulting



Real Experience. Real Advantage.

[

2

Bob Adams – Cooper Industries

United States Military Academy: 1983

MBA - Wake Forest University: 2000

11 years active military duty

15 years in the Army Reserve 14 years of experience working with SAP in apparel industry,

including 13 years with Apparel Footwear System and Global

Trade System.

3 years experience with GTS including versions 7.0, 7.2 & 8.0




[

3

Greg Futrelle – EntryPoint Consulting

Since 2004: 12 full GTS implementations, 4 upgrade projectsand several “tuning” workshops

Body of work includes SPL, Embargo, Legal Control, Product

Classification and NAFTA – also 2 ATLAS and 4 AES

implementations, all but one including electronic filing

Experience with GTS 2.0, 7.0, 7.1, 7.2, 8.0

Prior experience as U.S. Export officer for Fortune 100

company

Business background in logistics (multiple modes), warehouseoperations and cross-border trade.

IT background includes SAP Sales/Distribution.

www.entrypointconsulting.com

http://www.entrypointconsulting.com/

http://www.entrypointconsulting.com/




[

4

Learning Points

Upgrading to GTS 8 provides features that more closelyintegrate Compliance functions with Customs activities.

Electronic AES filing with GTS provides greater control over

your U.S. Export documentation in EDIand

print formats andreal savings over freight forwarders or other filing methods.

Reduce project timelines and costs with our tips for integrating

and managing the communications partners involved with AESelectronic filing.




[

5

Agenda

Brief discussion of upgrade to GTS 8 Reasons for upgrading

Our experiences

Tips for your success

Implementing AES smoothly for electronic EEI filing

Our experiences, good and bad

Tips for your success

Handouts

Too much info to fit into these slides




[

6

Upgrade to GTS 8.0

Only one year after upgrading from 7.0 to 7.2 – WHY ?

SPL Enhancements

Screen applicants

External systems partners

Customer contacts

Legal Control

Re-exports

Route-based checks

ITAR BOMs

ITAR projects

Import control for

inbound deliveries

Product Classification

Additional data - append

Customs Processing

Mass maintenance of

multiple items

Docs/Evidence tab sends

license data to AES

AEO authorization (EU)

Electronic Carnetprocessing (EU)


http://slidepdf.com/reader/full/atlasaesfutrelle1313v3pdf 7/17Real Experience. Real Advantage.

[

7

KEYS TO SUCCESS – GTS Upgrade

Keep upgrade separate from other activities if possible

Avoid complications from mixing upgrade with newimplementations or enhancements

Minimizes testing effort and downtime

Update user guides with new or enhanced functionality. Use strong testing partners (actual shipping and compliance

folks if possible) to discover process issues.

Employ “Test” user ids to validate any new roles



[

8

KEYS TO SUCCESS – GTS Upgrade, cont‟d.

Collaborate well with BASIS and ABAP

BASIS should review upgrade documentation in advance.

Remember some SAP notes have „manual‟ steps to apply.

Plan regression tests before upgrade begins

We recommend you develop a “tool kit” of standard GTSregression test scenarios for use any time you upgrade or

apply support packs.

SPL & Embargo

Legal Control Product Classification

NAFTA

ATLAS



[

9

KEYS TO SUCCESS – GTS Upgrade, cont‟d.

Prepare well before beginning

upgrade Release notes help you

understand pending changes in

existing functionality

Read RKT docs to understandnew functions that will be

introduced by upgrade

Try to resolve any existing

system issues prior to starting

Ref: help.sap.com



[

10

Implementing AES – Smoothly !

GTS Customs Processing Work List



[

11

Topics

Begin forms customizations as early as possible toallow time for “tweaking” during integration testing.

Master the “communications loop” with Seeburger,

VANs and U.S. Customs to avoid messages falling

into cracks.

Key trouble spots to avoid

Need some regression testing with existing ATLAS,

NAFTA and Compliance functionality since Customsprocessing touches on each in some way.



[

12

AES: Best Practices - Preparation

Start day one by initiating appropriate government applications

for obtaining authorization to file AES electronically Meet early with decision makers on print output appearance

and details, including business processes to generate output

There will be conflicts on the locations of certain fields, inclusion

of certain data elements and Start early with forms development and tweak as required

during testing

Changes will be required at some point in testing

Estimate 2 week minimum on any form development

Estimate 3-4 weeks on Commercial Invoices in GTS

Decide where and how to maintain SCAC / IATA

We created “SCAC” business partners



[

13

AES: Best Practices - Communications

Saves time.

Develops communications chanels between

each.

Establishes a „natural‟ KBR process.

Collaborate ! Get it right – together.

Validate the entire “loop” together rather than asking eachto validate their own segment.



[

14

AES configuration is like a golf swing…

Partner Function Group

Legal Reg activated

Document Type

Post Processing Framework (PPF) Message Type & Schema

Process Determination

Activity Sequence

Default Rule Settings Incompletion Schema

multiple things to remember at once.

Avoid trouble by understanding these before beginning



[

15

Example of Small Detail with Huge Impact

Must configure CUII in customs codes lists before criteria appears

on License Type config. But it must be in License Type config

before the values can populate on the Documents/Evidence tab of

the declaration



[

16

Key Learnings

UPGRADE

Know in advance what might change (release notes)

Segregate upgrade activities, if possible, from other projects

AES IMPLEMENTATION

Plan parallel tasks in case one area of the project plan becomes

delayed


http://slidepdf.com/reader/full/atlasaesfutrelle1313v3pdf 17/17R l E i R l Ad

[

] Thank you for participating.

SESSION CODE: 1313

Please remember to complete and return your

evaluation form following this session.

For ongoing education in this area of focus, visit www.asug.com.

ATLAS_AES_Futrelle_1313_v3.pdf

Documents

Transcript of ATLAS_AES_Futrelle_1313_v3.pdf