588 Mobile Enablement Services 588_erp607_bb_configguide_en_us.doc
This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA
Overview
Download & View 588 Mobile Enablement Services 588_erp607_bb_configguide_en_us.doc as PDF for free.
More details
- Words: 1,294
- Pages: 7
EHP7 for SAP ERP 6.0 February 2014 English
Mobile Enablement (Service) (588) Building Block Configuration Guide
SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany
SAP Best Practices
Mobile Enablement (Service) (588): Configuration Guide
Copyright © 2014 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.
© SAP SE
Page 4 of 7
SAP Best Practices
Mobile Enablement (Service) (588): Configuration Guide
Icons Icon
Meaning Caution Example Note Recommendation Syntax
Typographic Conventions Type Style
Description
Example text
Words or characters that appear on the screen. These include field names, screen titles, buttons as well as menu names, paths and options. Cross-references to other documentation.
Example text
Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXT
Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.
Example text
Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.
EXAMPLE TEXT
Keys on the keyboard, for example, function keys (such as ENTER key.
Example text
Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.
<Example text>
Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.
© SAP SE
Page 4 of 7
F2)
or the
SAP Best Practices
Mobile Enablement (Service) (588): Configuration Guide
Content Mobile Enablement (Service)........................................................................................................ 5 1
Purpose.................................................................................................................................. 5
2
Preparation............................................................................................................................ 5 2.1
3
Prerequisites................................................................................................................ 5
Configuration.......................................................................................................................... 5 3.1
Maintain Payment Card Type.......................................................................................5
3.2
Define Credit Card Companies....................................................................................5
3.3
Define Assignment Table for Credit Card Clearing.......................................................6
3.4
Set Up Feature TRVPA for Travel Expenses Parameters............................................6
© SAP SE
Page 4 of 7
SAP Best Practices
Mobile Enablement (Service) (588): Configuration Guide
Mobile Enablement (Service) 1 Purpose This configuration guide provides the information you need to set up the configuration of this building block manually. If you do not want to configure manually and prefer an automated installation process using BC Sets and other tools, refer to the Quick Guide.
2 Preparation 2.1 Prerequisites Before you start installing this building block, you must install prerequisite building blocks. For more information, see the Building Block Prerequisite Matrix, located on the documentation package on the Technical Content Library page.
3 Configuration 3.1 Maintain Payment Card Type Use In this activity, you maintain payment card types. If you want to use the Travel Receipt Capture functionality, for example, on a mobile device, it necessary to create a new specific payment card type.
Procedure 1. Access the activity using the following navigation options: IMG Menu
Cross-Application Components → Payment Cards → Basic Settings → Maintain Payment Card Type
Transaction Code
SPRO
2. On the Change View "Definition of Payment Card Type (CRM)": Overview screen, choose New Entries. 3. Make the following entries: Type
Description
Checking Rule
0090
Mobile: Travel Receipt Capture
4. Save your entries.
3.2 Define Credit Card Companies Use © SAP SE
Page 6 of 7
SAP Best Practices
Mobile Enablement (Service) (588): Configuration Guide
In this activity, you maintain the credit card companies. If you want to use the Travel Receipt Capture functionality, for example, on a mobile device, it necessary to create a new specific credit card company.
Procedure 1. Access the activity using the following navigation options: IMG Menu
Financial Accounting (New) → Travel Management → Travel Expenses → Master Data → Credit Card Clearing → Define Credit Card Companies
Transaction Code
SPRO
2. On the Change View "Names of Credit Card Companies": Overview screen, choose New Entries. 3. Make the following entries: ID
Credit Card Company
Type
MB
Mobile Travel Expense
0090
4. Save your entries.
3.3 Define Assignment Table for Credit Card Clearing Use In this activity you assign an expense type to a credit card company. If you want to use the Travel Receipt Capture functionality, for example, on a mobile device, it necessary to assign a new specific credit card company.
Procedure 1. Access the activity using the following navigation options: IMG Menu
Financial Accounting → Travel Management → Travel Expenses → Master Data → Credit Card Clearing → Define Assignment Table for Credit Card Clearing
Transaction Code
SPRO
2. In the Determine Work Area: Entry dialog box, in the Trip Provision Variant field, enter YB and choose Continue. 3. On the Change View "Assignment of Credit Card Transact.to Travel Expense Type" screen, choose New Entries. 4. Make the following entries: Card Company
Transaction Key
Travel Expense Type
Further Processing
Change-ability
MB
TK_AIR
AIR
10
Expense Type Can be Changed Freely
5. Save your entries.
© SAP SE
Page 6 of 7
SAP Best Practices
Mobile Enablement (Service) (588): Configuration Guide
3.4 Set Up Feature TRVPA for Travel Expenses Parameters Use The feature TRVPA determines the basic parameters for Travel Expenses. If you want to use the Travel Receipt Capture functionality, for example, on a mobile device, it necessary to activate the CCC and RBA parameters inside this TRVPA feature.
Procedure 1. Access the activity using the following navigation options: IMG Menu
Financial Accounting → Travel Management → Travel Expenses → Dialog and Travel Expenses Control → Travel Expenses Control → Set Up Feature TRVPA for Travel Expenses Parameters
Transaction Code
SPRO
2. On the Process feature TRVPA: decision tree screen, expand Country Key (MOLGA) 01. 3. Expand the 10 USA node and check that the RBA parameter is not 0. If the RBA parameter is 0, change the value to 1. 4. Check that the CCC parameter is not 0. If the CCC parameter is 0, change the value to 1. 5. Choose Activate.
© SAP SE
Page 6 of 7
Mobile Enablement (Service) (588) Building Block Configuration Guide
SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany
SAP Best Practices
Mobile Enablement (Service) (588): Configuration Guide
Copyright © 2014 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.
© SAP SE
Page 4 of 7
SAP Best Practices
Mobile Enablement (Service) (588): Configuration Guide
Icons Icon
Meaning Caution Example Note Recommendation Syntax
Typographic Conventions Type Style
Description
Example text
Words or characters that appear on the screen. These include field names, screen titles, buttons as well as menu names, paths and options. Cross-references to other documentation.
Example text
Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXT
Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.
Example text
Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.
EXAMPLE TEXT
Keys on the keyboard, for example, function keys (such as ENTER key.
Example text
Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.
<Example text>
Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.
© SAP SE
Page 4 of 7
F2)
or the
SAP Best Practices
Mobile Enablement (Service) (588): Configuration Guide
Content Mobile Enablement (Service)........................................................................................................ 5 1
Purpose.................................................................................................................................. 5
2
Preparation............................................................................................................................ 5 2.1
3
Prerequisites................................................................................................................ 5
Configuration.......................................................................................................................... 5 3.1
Maintain Payment Card Type.......................................................................................5
3.2
Define Credit Card Companies....................................................................................5
3.3
Define Assignment Table for Credit Card Clearing.......................................................6
3.4
Set Up Feature TRVPA for Travel Expenses Parameters............................................6
© SAP SE
Page 4 of 7
SAP Best Practices
Mobile Enablement (Service) (588): Configuration Guide
Mobile Enablement (Service) 1 Purpose This configuration guide provides the information you need to set up the configuration of this building block manually. If you do not want to configure manually and prefer an automated installation process using BC Sets and other tools, refer to the Quick Guide.
2 Preparation 2.1 Prerequisites Before you start installing this building block, you must install prerequisite building blocks. For more information, see the Building Block Prerequisite Matrix, located on the documentation package on the Technical Content Library page.
3 Configuration 3.1 Maintain Payment Card Type Use In this activity, you maintain payment card types. If you want to use the Travel Receipt Capture functionality, for example, on a mobile device, it necessary to create a new specific payment card type.
Procedure 1. Access the activity using the following navigation options: IMG Menu
Cross-Application Components → Payment Cards → Basic Settings → Maintain Payment Card Type
Transaction Code
SPRO
2. On the Change View "Definition of Payment Card Type (CRM)": Overview screen, choose New Entries. 3. Make the following entries: Type
Description
Checking Rule
0090
Mobile: Travel Receipt Capture
4. Save your entries.
3.2 Define Credit Card Companies Use © SAP SE
Page 6 of 7
SAP Best Practices
Mobile Enablement (Service) (588): Configuration Guide
In this activity, you maintain the credit card companies. If you want to use the Travel Receipt Capture functionality, for example, on a mobile device, it necessary to create a new specific credit card company.
Procedure 1. Access the activity using the following navigation options: IMG Menu
Financial Accounting (New) → Travel Management → Travel Expenses → Master Data → Credit Card Clearing → Define Credit Card Companies
Transaction Code
SPRO
2. On the Change View "Names of Credit Card Companies": Overview screen, choose New Entries. 3. Make the following entries: ID
Credit Card Company
Type
MB
Mobile Travel Expense
0090
4. Save your entries.
3.3 Define Assignment Table for Credit Card Clearing Use In this activity you assign an expense type to a credit card company. If you want to use the Travel Receipt Capture functionality, for example, on a mobile device, it necessary to assign a new specific credit card company.
Procedure 1. Access the activity using the following navigation options: IMG Menu
Financial Accounting → Travel Management → Travel Expenses → Master Data → Credit Card Clearing → Define Assignment Table for Credit Card Clearing
Transaction Code
SPRO
2. In the Determine Work Area: Entry dialog box, in the Trip Provision Variant field, enter YB and choose Continue. 3. On the Change View "Assignment of Credit Card Transact.to Travel Expense Type" screen, choose New Entries. 4. Make the following entries: Card Company
Transaction Key
Travel Expense Type
Further Processing
Change-ability
MB
TK_AIR
AIR
10
Expense Type Can be Changed Freely
5. Save your entries.
© SAP SE
Page 6 of 7
SAP Best Practices
Mobile Enablement (Service) (588): Configuration Guide
3.4 Set Up Feature TRVPA for Travel Expenses Parameters Use The feature TRVPA determines the basic parameters for Travel Expenses. If you want to use the Travel Receipt Capture functionality, for example, on a mobile device, it necessary to activate the CCC and RBA parameters inside this TRVPA feature.
Procedure 1. Access the activity using the following navigation options: IMG Menu
Financial Accounting → Travel Management → Travel Expenses → Dialog and Travel Expenses Control → Travel Expenses Control → Set Up Feature TRVPA for Travel Expenses Parameters
Transaction Code
SPRO
2. On the Process feature TRVPA: decision tree screen, expand Country Key (MOLGA) 01. 3. Expand the 10 USA node and check that the RBA parameter is not 0. If the RBA parameter is 0, change the value to 1. 4. Check that the CCC parameter is not 0. If the CCC parameter is 0, change the value to 1. 5. Choose Activate.
© SAP SE
Page 6 of 7
Related Documents
588
December 2019 28
588
December 2019 11
Us Mobile Operators_content Services
November 2019 37
Mobile Banking Services
May 2020 13
Your Bill For Mobile Services
July 2020 11More Documents from "Gabriel Brooks"
Credittransactions8_reyes Vs. Bancom.docx
June 2020 8
Polirev Matrix.docx
June 2020 7
Simpson Tome
December 2019 31