asapio cloud integrator for sap fieldglass• providing all required sap master data in sap...

46
ASAPIO Cloud Integrator for SAP Fieldglass Integrated vendor management with SAP ERP and SAP S/4HANA Product Overview April 2020

Upload: others

Post on 26-Apr-2020

25 views

Category:

Documents


1 download

TRANSCRIPT

ASAPIO Cloud Integrator for SAP FieldglassIntegrated vendor management with SAP ERP and SAP S/4HANA

Product Overview

April 2020

Agenda

1. Product Overview and Benefits

2. Packages and Scope Options

3. Maintenance & Support Model

4. Implementation Approach and Consulting Efforts

5. General features, FAQ and Roadmap

6. Additional Info: Process Flows

ASAPIO is an SAP silver partner and provides services and software for SAP customers

▪ Founded in 2003 and owned by 3 former SAP employees, today we are a growing team of over 40 SAP experts

▪ Serving all industries and SAP customers, including large and international companies

▪ Headquarter in Munich, various offices in Germany and a nearshore center in Voronesh/Russia

ASAPIO – Your SAP Partner for Cloud Integration and Procurement Solutions

Software & Service Portfolio:

▪ ASAPIO Cloud Integrator is our SAP certified add-on to connect SAP on-

prem systems to the cloud

▪ Design, implementation and support services for S/4HANA, SAP

Fieldglass, SAP Ariba, SAP PLM and SAP technologies including

Workflows, ABAP, SAP Fiori or SAP Cloud Platform developments

▪ Integration of SAP Ariba, SAP Fieldglass and other cloud solutions

▪ Event messaging integration with SAP on-prem systems

ASAPIO Cloud Integrator connects SAP on-prem systems to the cloud

❑ ASAPIO Cloud Integrator installs as add-on to SAP NetWeaver ABAP systems

❑ Brings native cloud interfaces to SAP systems, does not require middleware systems

❑ Supports multi-backend SAP landscapes and multi-cloud connectivity

SAP Applications Event Messaging 3rd Party Apps + Platforms

SAP Enterprise

Messaging®

AI VERGABEMANAGER®

ASAPIOCloud Integrator

Add-OnSAP S/4HANA

on-premSAP ERP any SAP

NetWeaver ABAP System

SAP Data Hub®

5

• providing all required SAP master data in SAP

Fieldglass allows best user experience

• full transactional integration means process

compliance with your SAP systems

• Secure and proven technical architecture allows for

minimum efforts during implementation and

operations

• ASAPIO Cloud Integrator is a packaged solution,

reducing project risk and speeding up implementation

time

Top reasons to integrate SAP Fieldglass with SAP ERP:

Business Case: Why Integrating SAP Fieldglass with SAP on-prem systems?

ASAPIO Cloud-Integrator is the only ready-to-run solution on the market for SAP

Fieldglass integration:

• ACI installs as SAP Add-On on any supported SAP ERP or SAP S/4HANA system

• No separate system, no middleware required

• Multi-backend SAP landscapes supported

• Pre-packaged integration scenarios, for end-to-end process integration (enhanceable)

• No downtime required for implementation

• ASAPIO supports you in activating the solution (as part of our setup services package)

• Maintenance & service available, including product updates

6

Productized approach for SAP Fieldglass integration

ASAPIOCloud Integrator

Add-OnSAP S/4HANA

on-prem

SAP Business Suite

+ SAP ERP

any SAP NetWeaver

ABAP system

SAP Fieldglass integration is built into S/4HANA core system for:

▪ S/4HANA Single Tenant Edition

▪ S/4HANA Cloud Edition

▪ S/4HANA On-Prem (supported releases)

7

S/4HANA standard integration capabilities and ASAPIO Cloud Integrator

ASAPIO Cloud Integrator for:

▪ SAP ERP

▪ SAP S/4HANA on-prem, e.g. for

▪ Outbound integration to SAP Fieldglass

▪ Plant maintenance integration

▪ MSOW + Worker Up-/Download

▪ any SAP NetWeaver ABAP system, e.g. for master data integration with SAP MDG, SAP IDM and others

▪ Multi backend and multi cloud connectivity

optional mandatory

ASAPIOCloud Integrator

Add-OnSAP S/4HANA

on-prem

SAP Business Suite

+ SAP ERP

any SAP NetWeaver

ABAP system

mandatory

ASAPIO Cloud Integrator is SAP® Certified – Powered by SAP NetWeaver®

• Benefits of certified Add-Ons:

• Deployment on SAP systems through SAP Add-On Installation Tool (SAINT)

• Packaged Add-On using SAP Add-On Assembly Kit

• Dedicated Software Component and Namespace

8

ASAPIO Cloud Integrator is SAP Certified – Powered by SAP NetWeaver

Find more details in theSAP Certified Solutions Directory:

www.sap.com/csd

Available packages and supported processes forSAP Fieldglass Integration

9

ASAPIO Cloud Integratorfor SAP Fieldglass

10

Packages for SAP Fieldglass

ASAPIO Cloud Integratorfor SAP Fieldglass

Basic scope:✓ Master data✓ Invoice integration

ASAPIO Cloud Integratorfor SAP Fieldglass

Additional scope:✓ PR/PO integration✓ Timesheets/SES

integration

Additional scope:✓ Process can be initiated

from SAP system✓ PM order integration

Optional: Workers + Master SOW (MSOW) Integration

FullCore Medium

11

Core Package Integration Scope

ASAPIO Cloud Integrator

SAP Fieldglass

SAP S/4HANASAP ERP

PRInvoice/

Credit MemoServices

Entry SheetPOContract

Service Procurement + Contingent Work

Work Order

SoWTimeSheet

Invoice /Auto-invoice

Master Data

Expense Sheet

Payment Requests for SoW

Job Posting

Master-SOW

op

tio

nal

Master Data

Worker

Employee Record

op

tio

nal

SAP on-prem systems

12

Medium Package Integration Scope

ASAPIO Cloud Integrator

SAP Fieldglass

SAP S/4HANASAP ERP

PRInvoice/

Credit MemoServices

Entry SheetPOContract

Service Procurement + Contingent Work

Work Order

SoWTimeSheet

Invoice /Auto-invoice

Master Data

Expense Sheet

Payment Requests for SoW

Job Posting

Master-SOW

op

tio

nal

Master Data

Worker

Employee Record

op

tio

nal

SAP on-prem systems

13

SAP Fieldglass Master Data Integration Scope

Scope Item Scope options Core Medium Full

Mas

ter

dat

a

Business units3 options: SAP organisational units, SAP purchasing organisations,

SAP company codes✓ ✓ ✓

Cost objectsSAP cost objects (code + description): Cost Center, Internal Order, WBS,

PM Order, Network✓ ✓ ✓

Legal entity SAP company codes ✓ ✓ ✓

GL accounts SAP GL accounts (codes and descriptions) ✓ ✓ ✓

Locations 2 options: SAP storage location, HSE work area ✓ ✓ ✓

Sites SAP plant codes ✓ ✓ ✓

Task code Assignment of company code to GL account codes ✓ ✓ ✓

Users and roles SAP user ids and role mapping ✓ ✓ ✓

Supplier

onboardingSAP supplier (classified for transfer to FG) ✓ ✓ ✓

Op

t.

Workers SAP employee master record including position optional

SAP Fieldglass Process Integration Scope

14

Scope Item Scope options (assumptions and restrictions apply) Core Medium Full

Bu

sin

ess

Pro

cess

es

Invoice Creation and revision ✓ ✓ ✓

PR / PO

Contingent Work (WO), from Fieldglass → SAP − ✓ ✓

Service Procurement (SOW), from Fieldglass → SAP − ✓ ✓

Service Procurement (SOW), from SAP → Fieldglass − − ✓

Support for Limit PR/PO − ✓ ✓

Support for Service PR/PO − − ✓

Service entry sheetCreation and revision of SAP SES from Fieldglass Timesheets, Expense Sheets,

Fees or Events (depending on process)− ✓ ✓

Plant maintenance

order

Process starts in SAP with PM order or PS network activity

(PR results from PM03 operation or PS network activity)

Revision possible only through new PM order item.

− − ✓

Op

t. Master SOW

(MSOW)SAP service contract, creation and revision, upload to Fieldglass optional

ASAPIO Cloud Integrator:Configuration within your SAP systems

15

Built-in to SAP Customizing Implementation guide

ASAPIO Cloud Integrator:Built-in Monitoring and Analytics

16

Application Architecture of ASAPIO Cloud Integrator

HTTP(S) request

Pull/Push

17

Cloud

+ many other and multiple solutions possible

SAP System

ACI Add-On

Data processing(read/write)

Change Pointer

Data/Message formatting

Error Handling

Workflow Log

Communication(solution connectors)

Connector

Database

SQL or BAPI

Configuration and monitoring framework

SAP ApplicationLayer

(e.g. SAP MM, QM, SD, …)

SAP ICM (internetcommunication)

SAP Secure storage(authorization data)

EventData

Scope Assumptions and Restrictions

19

1. Scope assumptions for ‘Contingent work’ requires ‘Medium’ package

Integration Point Scope Assumptions and Restrictions

Process Contingent Work

PR - Process starts in Fieldglass by creating a Job Posting, Assignment and the Work Order(WO)

- WO will create one limit PR (with item type ‘D’) in SAP. Pre-requisite (1) required

PO - One PR will result in one PO

- Conversion will happen through PO auto conversion (via SAP Report RM06BB30)

- Revision of the WO in Fieldglass can either update the PO directly or create a delta PR and subsequently, a PO update.

- PO can be closed (e.g. with ‘final invoice’ and ‘delivery completed’ flag) and reopened from Fieldglass.

Service Entry Sheet - SES creation will be based on time sheets and expense sheets

- SES uses summarization functionality to sum up the hours

- Revision functionality can only be used, if SAP is configured in a way that allows service entry sheets be revoked when an invoice with

reference to this SES has been posted already. Pre-requisite (2) required.

Invoice - Invoices will be posted directly by ACI using SAP standard BAPI

- To utilize the 'Paid Invoice' Upload, Pre-requisite (3) required.

Scope Restrictions - PRs cannot be manually converted into POs

- PR direct update is only supported for budget changes in Fieldglass, but not for changes of cost allocation.

- automatic budget reduction (in case of closed POs, where budget was not fully used) in SAP is not supported (because Fieldglass interface

does not provide the original amount of the PO)

- Posting invoices through third-party applications (incl. SAP OpenText) is not supported

20

2. Scope assumptions for ‘Service procurement for unplanned work’ requires ‘Medium’ package

Integration Point Scope Assumptions and Restrictions

Process Service procurement for unplanned work

PR - Process starts in Fieldglass by creating a SOW

- SOW will create one limit PR (with item type ‘D’) in SAP. Pre-requisite (1) required

PO - One PR will result in one PO

- Conversion will happen through PO auto conversion (via SAP Report RM06BB30)

- Revision of the SOW in Fieldglass can either update the PO directly or create a delta PR and subsequently, a PO update.

- PO can be closed (e.g. with ‘final invoice’ and ‘delivery completed’ flag) and reopened from Fieldglass.

- provide the original amount of the PO)

Service Entry Sheet - Unplanned SOWs use ‘Fee Payments’ in Fieldglass for the billing process

- One SES can contain multiple lines. This depends on the Fieldglass setup of the Fees.

Invoice - Invoices will be posted directly by ACI using SAP standard BAPI

- To utilize the 'Paid Invoice' Upload, Pre-requisite (3) required.

Scope Restrictions - PRs cannot be manually converted into POs

- PR direct update is only supported for budget changes in Fieldglass, but not for changes of cost allocation.

- automatic budget reduction (in case of closed POs, where budget was not fully used) in SAP is not supported (because Fieldglass interface

does not provide the original amount of the PO)

- Posting invoices through third-party applications (incl. SAP OpenText) not supported

21

3. Scope assumptions for ‘Service procurement for planned work’requires ‘Full’ package

Integration Point Scope Assumptions and Restrictions

Process Service procurement for planned work

PR - Upload of service PR to Fieldglass as SOW

- Process starts in SAP with a service PR (item type = ‘D’)

- One PR results in one SOW

- Requires SAP contract (which needs to be referenced in an existing Fieldglass MSOW) OR a template reference

- Once uploaded to Fieldglass, revisions are only possible on the Fieldglass SOW

- Service lines will reflect as SOW ‘Events’ in Fieldglass

PO - One PR will result in one PO

- Conversion will happen through PO auto conversion (via SAP Report RM06BB30)

- PO can be closed (e.g. with ‘final invoice’ and ‘delivery completed’ flag) and reopened from Fieldglass.

Service Entry Sheet - Planned services are SOW ‘Events’ in Fieldglass

- One SES will be created in SAP for each SOW Event that is marked as complete in Fieldglass

- Revision functionality can only be used, if SAP is configured in a way that allows service entry sheets be revoked when an invoice with

reference to this SES has been posted already. Pre-requisite (2) required.

Invoice - Invoices will be posted directly by ACI using SAP standard BAPI

- To utilize the 'Paid Invoice' Upload, Pre-requisite (3) required.

Scope Restrictions - no complex / hierarchical service items supported, only 1 level of services supported in PR for integration

- PRs cannot be manually converted into Pos

- Revision of the SOW in Fieldglass will not update the PO

- PR direct update is only supported for budget changes in Fieldglass, but not for changes of cost allocation.

- automatic budget reduction (in case of closed POs, where budget was not fully used) in SAP is not supported (because Fieldglass interface

does not provide the original amount of the PO)

- Posting invoices through third-party applications (incl. SAP OpenText) not supported

22

4. Scope assumptions for ‘Service procurement for plant maintenance’:requires ‘Full’ package

Integration Point Scope Assumptions and Restrictions

Process Service procurement for plant maintenance

PR - Upload of service PR to Fieldglass as SOW

- Process starts in SAP with PM order or PS network activity (PR results from PM03 operation or PS network activity)

- One PM Order operation results in one PR, which will result in one PO for each PR item

- Requires SAP contract (which needs to be referenced in an existing Fieldglass MSOW) OR a template reference

- Revisions are only possible by creating new operations in PM order.

PO - One PR item will result in one PO

- Conversion will happen through PO auto conversion (via SAP Report RM06BB30)

- PO can be closed (e.g. with ‘final invoice’ and ‘delivery completed’ flag) and reopened from Fieldglass.

Service Entry Sheet - Planned services are SOW ‘Events’ in Fieldglass

- One SES will be created in SAP for each SOW Event that is marked as complete in Fieldglass

- Revision functionality can only be used, if SAP is configured in a way that allows service entry sheets be revoked when an invoice with

reference to this SES has been posted already. Pre-requisite (2) required.

Invoice - Invoices will be posted directly by ACI using SAP standard BAPI

- To utilize the 'Paid Invoice' Upload, Pre-requisite (3) required.

Scope Restrictions - no complex / hierarchical service items supported, only 1 level of services supported in PR for integration

- PRs cannot be manually converted into Pos

- Revision of the SOW in Fieldglass is not supported, and will not update the PO

- PR direct update is only supported for budget changes in Fieldglass, but not for changes of cost allocation.

- automatic budget reduction (in case of closed POs, where budget was not fully used) in SAP is not supported (because Fieldglass interface

does not provide the original amount of the PO)

- Posting invoices through third-party applications (incl. SAP OpenText) not supported

Pre-requisites for ‘Medium’ and ‘Full’ packages:

1. Business Function 'LOG_MM_CI_2' active in SAP system

2. Feature 'RevGR desp. IR' for movement type 102 is active (transaction OMBZ) in SAP system

3. Payment advice functionality in automatic payment run (transaction F110) is enabled in SAP system

4. Integration of SAP Plant Maintenance Order / Order confirmation is out of scope of ‘Medium’ package

SAP system pre-requisites for installation:

SAP ERP and S/4HANA is supported, with the following minimum component versions:

23

System Pre-Requisites

SAP Component Release SP Package Description

SAP_BASIS 731 0002 SAPKB73102 SAP Basis Component

SAP_ABA 731 0002 SAPKA73102 Cross-Application Component

SAP_APPL 603 - - SAP ECC 6.0 EhP 3: required for Business

Function LOG_MM_CI_2

Maintenance and Support Model

▪ Support includes:

▪ Tickets/Issue resolution (please ask for our detailed Support Terms)

▪ Access to all new Releases

▪ We offer support through various channels:

▪ Ticketing System

▪ E-Mail

▪ Phone

▪ Support languages:

▪ English

▪ German

▪ ASAPIO support is available:

▪ Monday through Friday

▪ 9:00 to 17:00 (CET or CEST)

▪ excluding German public holidays

▪ Yearly fee:

▪ Already included in subscription prices

▪ For upfront license, yearly fee is 20% of license volume

25

Maintenance and Support Model

Channel Contact data

E-Mail [email protected]

Phone +49 (0)89 / 4520 7441 (during service hours)

Ticket System https://asapio.freshdesk.com

Implementation Approach & Consulting Efforts

Set-up services:

For baseline/minimum configuration of the product, ASAPIO guides the customer team through the scope activation and connectivity set-up.

• Delivered remotely

• Limited to a period of up to 4 weeks

• Can also include partner enablement

Implementation Approach and Consulting Efforts

Optional consulting services:

ASAPIO supports the project team during following activities:

• Participation in frequent project meetings

• SAP backend related parts of the Fieldglass integration design (IRD)

• Implementation on SAP backend side

• Enhancements / customizations

• Test system preparation and support of UAT/user acceptance test

• Go-live preparation and go-live

Consulting services for SAP backend integration are usually not part of SAP Fieldglass implementation projects.

To support the necessary activities, ASAPIO recommends a baseline approach and offers following services:

typical effort: 2 days / week + custom developments

fix-price package available

General features, FAQ and Roadmap

28

ASAPIO Cloud Integrator is unique in many ways:

• ACI is an add-on to your SAP systems and operates within your established SAP infrastructure in all aspects

(application management, security, logging etc.). No separate server required.

• ACI has a modular and open architecture: we deliver content packages for data extraction and mapping and

connectors for the different cloud solutions.

• ACI allows to enhance or create custom content (extractors, formatters) and connectors

• ACI uses highly scalable techniques to bring your data into the cloud:

• event based triggers, delta loads / change pointers

• parallel data processing (in multiple SAP work processes), data partitioning

• direct SQL reads or BAPI calls for data selection possible

• ACI supports interface clustering for efficient provisioning to multiple cloud applications

• ACI does not require any middleware

29

Key Benefits Of ACI Architecture

Availability of ACI framework features above depends on ACI connector and ACI content packages

ASAPIO Cloud Integratorvs. Custom-built integration

30

Feature ASAPIO Cloud Integrator

Custom-builtintegration

Ready-to-run in a few weeks: install, choose scope options and we activate the solution(excluding additional developments)

+ project approach

Out-of-the-box interfaces available (depending on package scope) over 60 -

Pre-delivered documentation + -

Packaged add-on for SAP ERP and S/4HANA + additional effort

Reference customers available + -

Out-of-the-box features for data extraction, enhancements, mapping and monitoring + -

Maintenance contract w/ support via phone, E-Mail and ticket system + additional effort

Updates included (with maintenance contract) + additional effort

Future-proof: ACI also works with SAP Ariba and many other cloud solutions (upgradeable toadditional connectors and content packages)

+ additional effort

Project risk Low High

Implementation efforts Low High

There is usually no benefit of custom built integrations over ASAPIO Cloud Integrator

ASAPIO Cloud Integrator:General Functions

31

• System connections

• Security certificates

• Encryption

Communication

• Source / destination format conversions

• Prefixing of source data

Data Conversion

• Master data extractors

• Customer fields

• Change Analysis / Change Pointer Concept

Data Extraction

• Central monitoring for all cloud integration points

• Cloud messaging and integration services

Monitoring

• Customizing options

• Consideration of customer-specific data

• Default values

• User exits possible

Process configuration

• Logging

• Tracing

• Repeating messages

• Restoring Data

Process security

• ASAPIO Cloud Integrator is an add-on to your existing SAP system

• No separate server needed

• ASAPIO namespace

• Perfect process overview and control through the use of well-known and proven standard SAP technologies, e.g.

change pointers, RFC-ALE communication, workflows and more.

• Secure communication between SAP and the cloud solution via dedicated web services

• Quick and easy deployment of the solution as transport requests, incl. predefined content packages

• Easy customization for custom content possible

32

ASAPIO Cloud Integrator:based on SAP NetWeaver Technology

Should you start integration before or after the SAP

Fieldglass roll-out?

• ACI would speed up SAP Fieldglass implementation and

roll-out activities, we advise to do it before the FG

implementation

Is ACI a middleware?

• No, ACI is not a middleware. ACI is a connectivity add-

on for SAP systems. It extracts, filters and formats SAP

data for the connected cloud solution on the outbound

side. For inbound side, ACI initates the SAP internal

processes for document creation and monitors the

process.

Is ACI ready for big data?

• Yes, ACI supports delta loads and data aggregation. This

allows large amounts of data.

Is ACI available for cloud-to-cloud scenarios?

• Not yet, but routing through an involved SAP ERP or

S/4HANA system might be an option to solve this.

Is there SAP standard integration available for SAP

Fieldglass?

• No, not for SAP ERP, MDG or other NetWeaver ABAP

systems. For S/4HANA, standard integration scenarios

are available, please contact us for details.

33

FAQ / Typical questions

ACI 9.3 Release Schedule 2020

JANUARY

Su Mo Tu We Th Fr Sa1 2 3 4

5 6 7 8 9 10 1112 13 14 15 16 17 1819 20 21 22 23 24 2526 27 28 29 30 31

MAY

Su Mo Tu We Th Fr Sa1 2

3 4 5 6 7 8 910 11 12 13 14 15 1617 18 19 20 21 22 2324 25 26 27 28 29 3031

SEPTEMBER

Su Mo Tu We Th Fr Sa1 2 3 4 5

6 7 8 9 10 11 1213 14 15 16 17 18 1920 21 22 23 24 25 2627 28 29 30

MARCH

Su Mo Tu We Th Fr Sa1 2 3 4 5 6 78 9 10 11 12 13 14

15 16 17 18 19 20 2122 23 24 25 26 27 2829 30 31

JULY

Su Mo Tu We Th Fr Sa1 2 3 4

5 6 7 8 9 10 1112 13 14 15 16 17 1819 20 21 22 23 24 2526 27 28 29 30 31

NOVEMBER

Su Mo Tu We Th Fr Sa1 2 3 4 5 6 78 9 10 11 12 13 14

15 16 17 18 19 20 2122 23 24 25 26 27 2829 30

FEBRUARY

Su Mo Tu We Th Fr Sa1

2 3 4 5 6 7 89 10 11 12 13 14 15

16 17 18 19 20 21 2223 24 25 26 27 28 29

JUNE

Su Mo Tu We Th Fr Sa1 2 3 4 5 6

7 8 9 10 11 12 1314 15 16 17 18 19 2021 22 23 24 25 26 2728 29 30

OCTOBER

Su Mo Tu We Th Fr Sa1 2 3

4 5 6 7 8 9 1011 12 13 14 15 16 1718 19 20 21 22 23 2425 26 27 28 29 30 31

APRIL

Su Mo Tu We Th Fr Sa1 2 3 4

5 6 7 8 9 10 1112 13 14 15 16 17 1819 20 21 22 23 24 2526 27 28 29 30

AUGUST

Su Mo Tu We Th Fr Sa1

2 3 4 5 6 7 89 10 11 12 13 14 15

16 17 18 19 20 21 2223 24 25 26 27 28 2930 31

DECEMBER

Su Mo Tu We Th Fr Sa1 2 3 4 5

6 7 8 9 10 11 1213 14 15 16 17 18 1920 21 22 23 24 25 2627 28 29 30 31

• 2 Major Releases for Core Component + Fieldglass Content and Ariba Content

• 4 weeks prior to Fieldglass Major Release

• 17th April – ACI 9.3 Build2004

• 16th October – ACI 9.3 Build 2010

• 2 Major Releases for CoreComponent + AI Content

• 16th March - ACI 9.3 Build2003

• 16th October - ACI 9.3 Build2010

• 2 Major Releases for Core Component + Event Content (SAP EM, Solace, Kafka)

• 16th March – ACI 9.3 Build2003

• 16th October - ACI 9.3 Build2010

• 3 Minor Releases for Event Content

• 15th May – ACI 9.3 Build 2005

• 17th July – ACI 9.3 Build 2007

• 18th December – ACI 9.3 Build2012

36

ASAPIO Cloud Integrator:Current Roadmap (Version March 16th, 2020)

9.2 9.3 9.3

Q4 2019Framework• Enabling ACI as an official SAP NetWeaver

certified Add-On• Dynamic ACI selection screenFieldglass• ConnectorN integration• New PM Integration scenario

Build 2004Framework• SAP Fiori Mobile App for ACI Monitor• Archiving of ACI Monitoring• Multi-selection for trace deletion in ACI

Monitor• Automatic tracing in case of communication

errorsFieldglass• Switch in User extractor for User ID (SAP User

ID or E-Mail Address)• Readable error messages for PO Closure

Interface• Switch to enable event-driven

communication (for transactional data)

Build 2010Framework• SAP Fiori Desktop App for ACI Monitor • Additional key figures of replication processes

in ACI Monitor• Filter functionality for ALE Change PointerFieldglass• Switch to enable event-driven

communication (for master data)• New variant for Contract/MSOW Integration

to support material/lean service contracts• New variant Approved Time Sheet Interface

to support material/lean service (Creation of Goods Receipt)

• New variant Approved Expense Sheet Interface to support material/lean service (Creation of Goods Receipt)

• New variant Approved SOW Characteristics Interface to support material/lean service (Creation of Goods Receipt)

Contact

ASAPIO GmbH & Co. KGLandsberger Str. 40081241 Munich / Germany

Phone +49 (0)89 4520-744-0Fax +49 (0)89 4520-744-2Email [email protected]://www.asapio.com

Peter Holtkamp

Managing Partner

37

These documents are provided by Asapio GmbH & Co. KG (hereinafter ASAPIO) and are for informational purposes only. ASAPIO assumes no liability or warranty for errors or omissions in this publication. ASAPIO only provides products and services as expressly set forth in the agreement for the respective products and services. None of the information contained herein is to be interpreted as an additional guarantee.

In particular, ASAPIO is under no obligation to follow any of the business operations outlined in this publication or any accompanying presentation, or to develop or publish features hereof.

The information contained in this publication does not constitute a promise, promise or legal obligation to deliver software. All forward-looking statements involve various risks and uncertainties that could cause actual results to differ materially from expectations. The forward-looking statements reflect the point in time when they were made. The reader is advised not to give excessive weight to these statements or to rely on them when making purchasing decisions.

Trademark Information: SAP, SAP SRM, SAP ERP, SAP Business Suite, SAP Ariba, SAP Fieldglass and other SAP product or technology names are the trademarks or registered trademarks of SAP SE in Germany and several other countries.

Disclaimer

38

Integration Scenarios: Flowcharts

Integration scenarios:Statement of Work for SAP Fieldglass

40

41

Integration scenarios:Statement of Work Revision for SAP Fieldglass

Integration scenarios:Workorders for SAP Fieldglass

42

Integration scenarios:Workorder Revision for SAP Fieldglass

43

Integration scenarios:Plant Maintenance for SAP Fieldglass

44

Integration scenarios:MSOW option: Service Master for SAP Fieldglass

45

Integration scenarios:Master data for SAP Fieldglass

46

Integration scenarios:Users and roles for SAP Fieldglass

47