SAP Business One 8.

81
Business Logic 1

Dipan Shah Roll-Out Services, Small Business GTM Sales SAP (UK) Ltd November 2010

SAP Business One 8.81 Expert Empowerment Session

Objectives

In this session you will learn about the enhancements in the business logic of SAP Business One 8.81 compared to SAP Business One 8.8.

The enhancements you will learn about are:

 Recurring

activities of Sales Orders

 Reopening  Project  User

codes

Administration Enhancements

SAP 2010 / Page 2

SAP Business One 8.81

Expert Empowerment Session

Agenda

 Recurring  Reopen

Activities

Order for Redelivery Project Information

 Extended  User

Administration Enhancements

SAP 2010 / Page 3

SAP Business One 8.81

Expert Empowerment Session

1.1 Recurring Activities

Enhancements:


Ability to create recurring activities for phone calls, meetings and tasks Edit single activities or recurring activities Back/Next button to step to the single instances of a recurring activity Exposed new fields to SDK DI API Week numbers display in calendar

 

 

Benefits:
 

Easier management of recurring meetings Combine easy handling of recurring activities with ability to track each single activity Platform for further enhancements, e.g. MS Outlook integration

Motivation: Better Customer Management with Less Effort

SAP 2010 / Page 4

SAP Business One 8.81

Expert Empowerment Session

1.2 Recurring Activities

- Availability

Recurring activities are only available for phone call, meeting and task only (similar to MS Outlook)

Default frequency of recurrence is set to None

SAP 2010 / Page 5

SAP Business One 8.81

Expert Empowerment Session

1.3 Recurring Activities

- Frequency of recurrence

Recurrence allow users to specify the frequency and range For weekly, monthly and annually recurrence, Repeat On is calculated from the header start date For weekly, user is able to select more than 1 day

 

No End Date is the default option Start date is defaulted from the header

SAP 2010 / Page 6

SAP Business One 8.81

Expert Empowerment Session

1.4 Recurring Activities

- Editing recurring activities

Editing an activity  If activity is a recurrence, any change prompts the user to save changes to this single instance or all instances of the activity


Saving changes as a single instance creates a new record in the DB with a link to the parent activity

Note: The follow up button is no longer available for recurrence activities

SAP 2010 / Page 7

SAP Business One 8.81

Expert Empowerment Session

1.5 Recurring Activities

- Searching for recurring activities

Find function in Activity  Triggered via the Find icon in the menu bar


The search results display recurring activities as a single activity with the frequency of recurrence

SAP 2010 / Page 8

SAP Business One 8.81

Expert Empowerment Session

1.6 Recurring Activities

- Instances of recurring activities
Displaying recurring activity  Tool tip on the list button
  

List button displays all recurrence of the activity List is limited to the 50 records from the current date Back / Forward buttons available to browse to more instances

SAP 2010 / Page 9

SAP Business One 8.81

Expert Empowerment Session

1.7 Recurring Activities

- Calendar view


Every instance of the recurring activity is displayed on the calendar Display calendar week if calendar is viewed in months Double click on any day to open up an Activity (just like MS Outlook)

SAP 2010 / Page 10

SAP Business One 8.81

Expert Empowerment Session

1.8 Recurring Activities

- Related modules


In related modules all unmodified instances of the recurring activity are displayed as a single activity E.g. Service module  a new line is shown for each closed instance and any modified instances the next activity execution date is displayed Grid display is sorted by activity number in ascending order


SAP 2010 / Page 11

SAP Business One 8.81

Expert Empowerment Session

2.1 Reopen Order for Redelivery

Business Scenario:


Initial Sales Process: Sales Order

Qty: 10

Items are returned for redelivery Reopen the original sales/purchase order to process a subsequent delivery

Delivery 1
Qty: 10

Sales Order: Status: Closed Open Qty: 0

Enhancements:

Return (based on delivery) Delivery 1 Return

Qty: 3 Sales Order: Status: Open Open Qty: 3

Reopen sales or purchase order when returning goods Increase open quantity of item in sales or purchase order according to the quantity in the return New behavior can be switched on or off

Subsequent delivery of open quantity: Sales Order Delivery 2

Qty: 3 Sales Order: Status: Closed Open Qty: 0

Benefits:
 

Reduce the need to have duplicate orders Easier and more transparent handling of subsequent delivery when goods are returned

Motivation: Streamlined Processes

SAP 2010 / Page 12

SAP Business One 8.81

Expert Empowerment Session

2.2 Reopen Order for Redelivery

- Document settings

Enable in Document Settings for sales and purchase orders separately:  Document Sales Order  Document Purchase Order

Choose whether the function is automatic or user decision

SAP 2010 / Page 13

SAP Business One 8.81

Expert Empowerment Session

2.3 Reopen Order for Redelivery

- Marketing Document
 Provides the option for users to reopen the items on the based document when creating a Return document  The Change Log tracks the information  Applies also to a Credit Memo based on an Invoice which was originally based on a sales order or delivery that was based on a sales order  This solution is not relevant for Draft Returns

SAP 2010 / Page 14

SAP Business One 8.81

Expert Empowerment Session

2.4 Reopen Order for Redelivery

- Document Generation Wizard
 Provides the option for users to reopen the items on the based document when creating a Return via the DGW (Document Generation Wizard)

SAP 2010 / Page 15

SAP Business One 8.81

Expert Empowerment Session

3.1 Extended Project Information

Enhancements:


Extended project information to major types of master data and settings Extended project information to major business transactions and journal entries Project information for revenue, expense and inventory accounts

Benefits:


Broader range of information can be used to plan, manage and calculate projects More accurate and transparent project management

Motivation: Transparent and Complete Project Handling

SAP 2010 / Page 16

SAP Business One 8.81

Expert Empowerment Session

3.2 Extended Project Information

- Setup


Block or warn where Project field in a transaction is empty against a GL account that has the Project field set

Identify a default Project for the GL account in the master record Examples where default project used:  Period-End Closing  Conversion Differences

SAP 2010 / Page 17

SAP Business One 8.81

Expert Empowerment Session

3.3 Extended Project Information

- Activation and Forms affected


The posting date is compared with Valid From and Valid To dates if the posting date is not in the valid range, the transaction is not created and an appropriate error message provided Active setting ensures the project is listed in the choose from list

Additional transactions where Projects have been included

Financials  Transaction Templates  Recurring Postings  Marketing Documents  Freight definition  Freight on row  Freight on header  Freight on header (Brazil)  Purchasing-AP  Landed Costs


Inventory management  Initial Quantities  Inventory posting  Inventory revaluation  Banking  Payment  Deposit- Check  Deposit- Credit card  Post-dated Credit Voucher Deposit  Production  Production Order  Bill of Material

SAP Business One 8.81 Expert Empowerment Session

SAP 2010 / Page 18

3.4.1 Project Code

- UI Enhancements
 Field descriptions aligned to:  BP Project project field related to BP e.g. in BP master data, AP/AR marketing doc header  Project all other project fields e.g. AP/AR marketing doc rows  Field values display aligned to always showing the Project code  Project selection method aligned in all project fields List of Projects screen pops up for selection of project

SAP 2010 / Page 19

SAP Business One 8.81

Expert Empowerment Session

3.4.2 Project Code

- JE Related


Project field available in:  Posting Template



Recurring Postings

If a project has been set in a GL account master data, it is displayed here as default when the GL account is chosen Where JE/JV created using either the posting template or the recurring posting, the project value is copied into the transaction rows

SAP 2010 / Page 20

SAP Business One 8.81

Expert Empowerment Session

3.4.3 Project Code

- Freight
 

Project field added to Freight definition Freight 1 Project, Freight 2 Project and Freight 3 Project fields added to the Marketing document rows Project field added in Marketing document freight header Project fields at both header level and row level are populated with default values defined in setup Where JE is created from the Marketing document, the Project values are transferred to the posting If Project value in the header is different to the row level, the JE splits the posting according to the Project

 

SAP 2010 / Page 21

SAP Business One 8.81

Expert Empowerment Session

3.4.4 Project Code

- AP/Landed Costs
 Project added in Landed costs  The values are copied from row items of Good receipt PO;  The value of Project is copied to the JE rows of inventory account, custom allocation account , custom expense account, and landed cost allocation account. (Only valid for continuous stock system) Note: 1- In non-continuous stock system, project will not apply to JE, since there will not be any JE behind inventory transaction 2- Same applies to Distribution rule

SAP 2010 / Page 22

SAP Business One 8.81

Expert Empowerment Session

3.4.5 Project Code

- Inventory transactions


Project field available in the following Inventory transactions:

i. ii. iii.

Inventory Initial Quantity (Opening Balances) Inventory Posting Inventory Revaluation JE rows of specified item inventory account and open inventory account JE rows of inventory account, inv. Offset-Dec. and inv. Offset-Inc. account JE rows of specified inventory account and G/L increase/decrease account

Project posted to the relevant JE:

i.

ii.

iii.

Note: Only valid for continuous stock system

SAP 2010 / Page 23

SAP Business One 8.81

Expert Empowerment Session

3.4.6 Project Code

- Banking transactions (1/2)
 

Project value on header is used for all JE postings Project values on row level:
 

Used to filter and sort transactions Do NOT affect JE postings

SAP 2010 / Page 24

SAP Business One 8.81

Expert Empowerment Session

3.4.7 Project Code

- Banking transactions (2/2)


Deposit Check and Credit Card:  Project value received from original incoming payment header


Project posted to the (interim) check or credit card receiving account Project can be manually entered for commissions Used for analysis of interim accounts

 

SAP 2010 / Page 25

SAP Business One 8.81

Expert Empowerment Session

3.4.8 Project Code

- Production
 

BOM: Project value at header level is copied to rows by default BOM header level project copied into PO header and BOM row level projects copied into PO rows

 PO: The header project value is copied to rows of Receipt from Production; the row value is copied to relevant item rows of Issue for Production, in both cases of manual issue and backflush  The header value is copied to JE rows of WIP and WIP inventory variance accounts when Production Order is closed, if production variance exists

SAP 2010 / Page 26

SAP Business One 8.81

Expert Empowerment Session

4.1 User Administration Enhancements

Enhancements:


Personalized user experience: Added Language, Font and Font size Extended and harmonized field length of User Name; Sales Employee Name; HR First Middle and Last Name Tool-Tip added to show long names which are not completely visible on the screen Exposed new length to DI API

Benefits:


Administrator can assign the language, font and size to the users Ability to assign profile to user with language, font and size (instead saving for each client) Ability to enter and see long names

Motivation: Personalized User Experience

SAP 2010 / Page 27

SAP Business One 8.81

Expert Empowerment Session

4.2 User Enhancements

 Administration->Setup->General->Users>User Name (155 characters)

 Administration->Setup->General->Sales Employee Name (155 characters)

 Human Resource->Employee MD->First Name (50 characters)  Human Resource->Employee MD>Middle Name (50 characters)  Human Resource->Employee MD->Last Name (50 characters)  Where name length is greater than display field, tool tip shows the full name when placing mouse over the field

SAP 2010 / Page 28

SAP Business One 8.81

Expert Empowerment Session

4.3 User Enhancements

 Default user settings include:  Language  Font  Font Size  Font preview box is available to show the choice of font and size.  For upgrade, user default language, font, font size is extracted from general settings  For future upgrades, user defaults will not be amended

SAP 2010 / Page 29

SAP Business One 8.81

Expert Empowerment Session

Thank you!
Dipan Shah Roll-Out Services, Small Business GTM Sales SAP (UK) Ltd November 2010

SAP Business One 8.81 Expert Empowerment Session

SAP 2010 / Page 30

SAP Business One 8.81

Expert Empowerment Session

Disclaimer

 The information in this document is proprietary to SAP. No part of this document may be reproduced,
copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG. agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice. accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.

 This document is a preliminary version and not subject to your license agreement or any other

 SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the

 SAP shall have no liability for damages of any kind including without limitation direct, special, indirect,  The statutory liability for personal injury and defective products is not affected. SAP has no control

over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.
SAP Business One 8.81 Expert Empowerment Session

SAP 2010 / Page 31

Copyright 2010 SAP AG 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 AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned and associated logos displayed are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfltigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrckliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen knnen ohne vorherige Ankndigung gendert werden. Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte knnen Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwhnte SAP-Produkte und Services sowie die dazugehrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Lndern weltweit. Alle anderen in diesem Dokument erwhnten Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte knnen lnderspezifische Unterschiede aufweisen. Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen Vereinbarung mit SAP. Dieses Dokument enthlt nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP-Produkts und ist fr SAP nicht bindend, einen bestimmten Geschftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP bernimmt keine Verantwortung fr Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die Richtigkeit oder Vollstndigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewhr, weder ausdrcklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschlielich, hinsichtlich der Gewhrleistung der Marktgngigkeit und der Eignung fr einen bestimmten Zweck sowie fr die Gewhrleistung der Nichtverletzung geltenden Rechts. SAP bernimmt keine Haftung fr Schden jeglicher Art, einschlielich und ohne Einschrnkung fr direkte, spezielle, indirekte oder Folgeschden im Zusammenhang mit der Verwendung dieser Unterlagen. Diese Einschrnkung gilt nicht bei Vorsatz oder grober Fahrlssigkeit. Die gesetzliche Haftung bei Personenschden oder die Produkthaftung bleibt unberhrt. Die Informationen, auf die Sie mglicherweise ber die in diesem Material enthaltenen Hotlinks zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP untersttzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewhrleistungen oder Zusagen ber Internetseiten Dritter ab. Alle Rechte vorbehalten.

SAP 2010 / Page 32

SAP Business One 8.81

Expert Empowerment Session