A series of new meet-the-expert webinars has been set up for SAP Business ByDesign topics. The sessions address key users at the customer site and are offered by the SAP EnterpriseSupport Academy, SAP’S enablement program for support-related topics.

Topics covered

System infrastructure

• Introduction to technology and architecture of SAP Cloud Solutions
• Setting up a SAP Cloud implementation project at the customer site
• Requesting tenants and tanaging your SAP Cloud tenant landscape
• Best practices: Service Control Work Center
• Communication with SAP Cloud Support

Project implementation and Go-Live

• Migration before and after go live
• Best practices: Organizational Management
• Key-User Tools: Overview of customer-specific analytics

System integration

• Best practices: Intercompany scenarios for service providers

Customer-specific enhancements

• Customer-specific enhancements with SAP Cloud Applications studio
• Key-User Tools: Add customer-specific fields

Most sessions contain demos and the opportunity to discuss questions with our support experts. All sessions will be recorded and made available in our replay library.

How to access

• Use our calendar viewto see which live sessions are scheduled
• Access our replay library to see the available recordings

Learn more about the SAP Enterprise Support Academy

• Visit us at http://support.sap.com/esacademy
• Check out the SAP Enterprise Support Academy infographic

In this blog I would like to quickly show how material cost estimates can be based on lot sizes other than lot size 1. The big advantage is that then also list prices using scales are considered.

In my example I created a production model for product SR_PZ_001. Important to notice is that the BOO (Bill Of Operations) quantity is used as the lot size for material cost estimate quantity. In my example I use 10 each.

For BOM component SR_BDN_001 used to produce SR_PZ_001 I created a price list with scales. Please notice that for quantities larger than 9 each the price is 3 USD instead of 3,90 USD:

When now performing a material cost estimate the BOO quantity of 10 each is used as a basis and via BOM explosion the price for 10 each of component SR_BDN_001 from the list price of 3 USD is considered:

Si  alguien me  puede  ayudar,de que forma puedo  hallar el  subtotal  de la columna  promedio  en  una  tabla  de referencias cruzadas.

Muchas  Gracias =

Hello All,

With this blog, I would like to outline the Process of executing Balance carry forward and Closing year.

To close year, Below Prerequisites must be fulfilled.

- The preceding fiscal year is closed.

- You have performed a depreciation run for the fiscal year.

- You have performed balance carry-forward for the year.

You perform balance carry forward as the last phase of year-end closing, which usually means that you do this in the new fiscal year. The opening balances of the balance sheet accounts need to have been posted at this point.

Balance carry-forward transfer the Balance of G/L account from one year to next year. This will ensure that Net profit/Loss is correctly reported in the balance sheet.

The balance sheet accounts and the profit and loss accounts are carried forward as follows:

• The balances of the balance sheet accounts are carried forward into the next fiscal year. This ensures that the closing balances of the balance sheet accounts in the fiscal year being carried forward are the same as the opening balances in the new fiscal year.  i.e Closing balance of G/L for year FY = Opening balance of G/L for year FY+1

• The balances of the profit and loss accounts are cumulated and transferred to the corresponding balance sheet account for annual net profit or loss. This ensures that closing balances and opening balances of the profit and loss accounts are always zero.

To make the opening balances of G/L accounts available before balance carry forward is completed, you need to perform balance carry forward in two steps:

Step 1: Carry the G/L account balances forward

This accomplishes the following:

• The balances of the balance sheet accounts are carried forward to the same accounts in the new fiscal year.
• The balances of the profit and loss accounts are cumulated and transferred to the income statement closing account. This ensures that the closing and opening balances of the profit and loss accounts are zero.

Once you have completed Step 1, you can continue to make postings to the fiscal year being carried forward. However, be aware that such postings increase the number of journal entries that need to be carried forward because change documents have to be posted in addition to the journal entries themselves. Change documents update the closing balances in the fiscal year being carried forward and the opening balances of the affected G/L accounts in the new fiscal year.

Step 2: Calculate and carry forward profit/loss

This step is the last activity in your balance carry forward process. You perform this step after all postings to the fiscal year to be carried forward have been made.

You can only perform this step once you have completed Step 1 in an update run.

Step 2 posts the balance of the income statement closing account to the balance sheet item Equity either of the annual net profit account or the annual net loss account, depending on whether it is a debit or credit balance at the company level. The balance of the annual net profit account or of the annual net loss account is then carried forward to the new fiscal year.

In order to execute the Balance carry-forward in

Step 1 - Last allowed step for period 012 in year should be 990 – Closing balance or higher (i.e 990 or 991)

Step 2 - Last allowed step for period 012 in year should be 991 – Profit and loss calculation of retained earnings and First allowed step for the period 001 in next year must be 001 – Opening balance.

You can find more information about the different closing steps and its use in the help center document : Closing Steps

After Performing Both the steps in update mode, you can block the period 012 by following below steps

1. General ledger work center
2. Set of books and assigned companies view
3. Click on Open and close period
4. Select the row
5. Click on Close period
6. Click on Save

Now You can close the fiscal year.

1. General ledger work center
2. Set of books and assigned companies view
3. Click on Edit Fiscal Year
4. Select the row
5. Click on Close Year
6. Click on Save

Regards,

Harshal

In this blog, i will try to explain the system posting logic in the determination of Key Date Valuation Amount, Gain/Loss Amounts in a                             Foreign Currency Remeasurement For Cash

We shall see how the the postings are determined based 'Foreign Currency Remeasurement Principles', For the explanation/understanding of the system logic we shall take one example here, we shall take the assignment of 002 - Lower Value as remeasurement principle

Go to Business Configuration work center, In the Fine-Tune Activity, Search for 'Foreign Currency Remeasurement for cash'

For this explanation we have assigned the method as A002 – Lowest Value in the activity 'Edit foreign currency remeasurement methods'

Let’s go to Edit foreign currency remeasurement methods

The assigned Accounting principle & Foreign Currency Remeasurement Methods combination can be seen

Also importantly, we need to maintain the Exchange rate between the foreign currency & the company currency then use foreign currency remeasurement to convert the balances of cash ledger accounts from foreign currencies into the company currency on a specific key date.

Now we shall slightly exchange the exchange rate validity and re-run to check the result again

So now if you compare the previous run and this run the key date exchange rate is changed from 6 to 15 and You use foreign currency remeasurement to convert the balances of cash ledger accounts from foreign currencies into the company currency on a specific key date and post gains and losses, resulting from exchange rate fluctuation.

But here you observe that with 6 % & 15 % exchange rate the key date valuation amount has not changed.

2500 * 6 =  15000 ; this value is correctly displayed in the previous run 2015-06-0*3

2500 * 15 = 37500 ; this value is not showing correctly in the current run 2015- 06-0*6

Reason being that If you see the data selection the Set of Book used is '9011' and for this the accounting principle maintained is '6000 – US-GAAP' ( Go to set of books activity to check this )

Now go to the fine-tune activity 'Foreign Currency Remeasurement Methods for Cash' and select Edit foreign currency remeasurement methods and select the Method as 'A002' and here,You can see Foreign Currency Remeasurement Principle maintained as 002 - Lower Value and now proceed with selection of the tab 'USE OF CASH' here you can see your accounting principle 6000 – US - GAAP which is assigned to the set of book - 9011.

Rule: Foreign Currency Remeasurement Principle maintained as 002 - Lower Value, what does this means

System will compare your ( Historic Valuation Amount & Balance Amount * applicable exchange rate ) and out of these two whichever is lower will be shown under Key Date Valuation Amount i.e., Lower of two values is taken as KEY DATE VALUATION AMOUNT

And out of 15,000 & 37,500, system took 15000

Additional Note: Apart from this key date valuation amount, If you see that system is picking an exchange rate which is not maintained in Edit Exchange Rate.

Pre-requisites to Check : Did you maintained the currency for the Source Currency to Target Currency ? If you have not maintained then system will try to check at least in the order of Target Currency to Source Currency and if the result Yes then the exchange rate is always 1/X, for instance ( 1/6 = 0.166667)

But usually it is always Source Currency to Target Currency Calculation but if No exchange rate is maintained for this combination then only the logic of finding the exchange will be vice-versa i.e., Target Currency to Source Currency when this logic is picked it 1/X.

Hope this post will be helpful to some extent.

Thanks

Lokesh Sharma

Overview

SAP Business ByDesign supports the feature of representing the documents of a process in the form of Business Document Flow. The system stores the data of every step in an operational business process in the form of a document, for example, an opportunity, a sales quote, a sales order, an outbound delivery, or a customer invoice. Since the steps of the business processes are often based on previous steps, the documents are likewise based on one another and thus form a consecutive document chain.

Business Document Flow is a read only representation which gives a view of a set of predecessors and successors of a business transaction document and helps to monitor and analyze entire document chain.

The initial view of the document flow highlights the document from which you start the display. It displays documents preceding or following the highlighted document. This highlighted document is called 'Anchor Object'. To view the overview of a specified business document, click the corresponding ID.

If you click on the anchor symbol of any other document view, then document flow is seen from the respective document perspective.

Document Flow currently provides 2 Views: Standard View and Extended View.

Standard View (Business View) usually refers to the Document Flow view required for a User who would just be interested in the Business process.

Extended View (Technical View) refers to the Document Flow view required for a User who would be interested in the technical documents of the Business Process as well.

Feature Enabled in 1508

Apart from viewing business transaction documents for SAP delivered business objects in document flow, now we also can view the business transaction documents for partner delivered business objects in the form of document flow. Links from SAP documents to partner documents, within partner documents of a solution, partner documents of different solutions can all be viewed easily and also the navigation to the respective document screen is provided. SDK is now enabled for the partners to store the links between the business documents. There are 4 scenarios which could be considered for the same and steps to achieve them by the partners would be provided below.

Scenarios:

A)    Partner BO being an Anchor and having relation with SAP delivered business object.

B)    Connecting link between partner business objects of same solution.

         Link between multiple partner business objects to multiple SAP delivered business objects.

C)   Link between SAP delivered business object and partner business object - SAP Business Object being  anchor.

D)    Connecting link between partner business objects of 2 or more solutions.

Steps to configure Business Document Flow for a Partner Business Objects

• ·        All consuming objects should have an association to BusinessDocumentFlow object. Add an association to the Business Object 'BusinessDocumentFlow' using the key BusinessDocumentFlowKey (alternative key) from the Business Object Node ROOT. And fill the document key in event-before-save.

• ·        Create BC set on BCO BusinessDocumentFlowAnchor to fill in the entries for the respective Business Object. This is to see business document as an anchor object in the document flow screen. Rather to view document flow from anchor object perspective.

Fields:

1.     ID : Identifier (key).

2.     AnchorESName: Anchor Object ES Name. (Mandatory to fill).

3.     AnchorESNamespace: Anchor Object ES Namespace. (Mandatory to fill).

4.     Anchorkey: Specifies the key if it is ID / UUID . UUID is considered as Document Key for Partner Business Objects. (Mandatory to fill).

• ·        Create BC set on BCO BusinessDocumentFlowSpanDefinition to fill in the entries for the respective Business Object with the corresponding list of Business Objects that can be part of the Business Document Flow View.

Fields:

1.     SpanID: Identifier (key).

2.     ProfileType: refers to the Standard or Extended View of the Business Document Flow. (Mandatory to fill)

3.     AnchorESName: is the ES name of the BusinessObject on which the Document Flow is derived. (Mandatory to fill)

4.     AnchorESNamespace: is the ES Namespace of the BusinessObject on which the Document Flow is derived. (Mandatory to fill)

5.     SpanESName:  is the ES Name of the BusinessObject which could be part of the Document Flow, derived on the Anchor BusinessObject. (Mandatory to fill)

6.     SpanESNamespace: is the ES Namespace of the BO which could be part of the Document Flow, derived on the Anchor BusinessObject. (Mandatory to fill)

7.     BDF_invisible: specifies if the particular SPAN BO would be visible or invisible.

• ·        Create BC set on BCO BusinessDocumentFlowBusinessObjectRelationship to fill in the entries for links.

Fields :

1.     B1B2ID: Identifier(Key)

2.     BO1ESName: ES Name of Business Documents that would be part of the link. (Mandatory to fill)

3.     BO1NameSpace: ES Namespace of Business Documents that would be part of the link. (Mandatory to fill)

4.     RoleBO1: Role of the respective Business Document in the corresponding link. Ex: Predecessor / Successor. (Mandatory to fill)

5.     BO2ESName: ES Name of Business Documents that would be part of the link. (Mandatory to fill)

6.     BO2NameSpace: ES Namespace of Business Documents that would be part of the link. (Mandatory to fill)

7.     RoleBO2: Role of the respective Business Document in the corresponding link. Ex: Predecessor / Successor. (Mandatory to fill)

8.     ResponsibleBO: Specifies if the First BO or Second BO would hold the link information. If left BLANK, it would mean that either of the BO  could provide the link information.

9.     BO1key: Specifies if the key for the Document is UUID or ID. If left blank, UUID is considered as the Document Key.

                      10.      BO2key: Specifies if the key for the Document is UUID or ID. If left blank, UUID is considered as the Document Key. 

• ·        BADI BAdiDocumentFlowforGetNeighbours is defined by document flow which is filter based and used to retrieve links/neighbors and corresponding partner business object properties like creation date/ time, Name of the BO and so on.

Interface Method: GET NEIGHBOURS: For link BO1 -> BO2, when BO1/BO2 is responsible for maintaining links, this method needs to be implemented for the corresponding BO defined by the filter (ESName and ESNamespace) to get the neighbors and BO Properties.

Note: In order to view anchor indicator, at least one property must be provided by the partner for the corresponding business object.

This BADI is implemented for all the scenarios mentioned above in the document having the filter values:

A)    Partner BO being an Anchor and having relation with SAP delivered BO

Filter value: ES Name and ES Namespace of the Partner BO

B)    Connecting link between partner business objects of same solution like:

Partner BO (1) (Anchor) to Partner BO(2) of same solution /Multiple Partner BO s to Multiple SAP BO s

Filter Value: ES Name and ES Namespace of the Partner BO(1)

C)    Link between SAP delivered business object to partner business object

Filter Value: ES Name and ES Namespace of the SAP BO

D)   Connecting link between partner business objects of 2 or more solutions. Like : Partner BO(1) Solution1 and Partner BO(2) of Solution2

Filter Value: ES Name and ES Namespace of SAP BO. BADI implemented in both the solutions

Example: Opportunity is created from partner business object of solution A and same opportunity has relation with partner business object of solution B, then both the partners have to implement the BADI having opportunity as filter parameter and provide corresponding partner business object as opportunity’s neighbor in the result.

Details of the import and export parameters of the BADI method get neighbours

Importing Parameter:

GetNeighboursParamentersPDI: This has 3 elements :

1.     DocumentBONode is a table :

2.     TableOfEsnametogetOTC (Optional)

3.     CallType (Optional) : This is a string with below values- GetNeighbors/Nothing and GetBy

Exporting Parameter:

GetBDFReferencesPDI: This is the table of 'Neighbors'.

Elements of the table:

Table of Properties :

1. If AMOUNT is specified CURR CODE should exist

2. If quantity is specified UNIT should exist

3. Property ID should be present for each property.

4. For one property not more than one fields should be provided

5. Special property indicator check, to check if the value and the indicator are in sync.

6. In all Invalid properties scenarios, the invalid properties are deleted.

TableOfPDINeighbors:

Document Flow UI configuration

Document Flow shows a graphical view of the documents involved in a Business Process. This is designed as an embedded component based on Document Flow controller.

Consumption of the embedded component is to be done by the partners only for the partner UI components (OIFs). Because SAP UI components have already consumed the embedded component.

If the partner business object has relation to any of the SAP delivered business objects and partner wants to see his object in SAP UI component, then he can directly implement the BADI to showcase the partner business object in SAP UI component (OIF). No need of using embedded component.

The parent UI Component (host floor plan in other words the embedding UI Component) has to define an Outport with the BusinessDocumentFlow Node ID as parameter and do the simple navigation as shown in screenshots.

Name of UI Component: DocFlow_EC

Path in XRepository (in case of embedded component): SAP_BYD_APPLICATION_UI/Reuse/DocumentFlow

There is an OBN Link in the document flow view which is enabled for all the partner business objects. (Link enablement is for all the BOs except the anchor BO (in blue)). Onclick of this link, it would open a factsheet/readonly view of the respective business object.

Note: There is no possibility to provide port type package generated from the solution. OBN inport must be created.

To navigate to the factsheet, an OBN inport has to be created in the target screen having

• -         Select Operation as 'Open'.
• -         Port Type Package as '/SAP_BYD_UI/SystemPortTypes.PTP.uicomponent'.
• -         Port type reference as 'OpenByKey'.
• -         Keylist, key as parameters.
• -         And the event handler as shown below. For the anchor symbol to be seen on the document view, atleast one property should be provided by the partners for the Partner Business Object.

Summary

With the above feature enabled for the partners, now it is possible to view the processes/several deviations which goes from one document to another document whether it is SAP business document or partner document or partner documents of different solutions at one place by configuring accordingly.

Explicitly, it is possible to view the SAP business documents in the document flow of the partner UI components and also when you open the UI components of SAP, then you would be able to see the partner business documents if they have relation.

For example: If an opportunity is created/ neighbor of a partner Business object, then when you open the document flow of opportunity, you would be able to view the partner document also.

Background

As part of the regular performance analysis and system resource utilization optimization exercise to improve response times of Business ByDesign we would like to inform our users regarding the introduction of new defaults and additional restrictions in usage of background job scheduling functions.

Business ByDesign offers MDRO (Mass Data Run Object) as a way to automate mass processing of a task or business transaction. For example, MDROs are used in business processes in invoice runs, payment authorization runs, balance confirmation runs and outbound logistics confirmation update runs.

(For further details please refer to online help document).

MDROs allow users to schedule processes to run in the background and some MDROs allow running them periodically by specifying a recurrence interval, this recurrence can be set to run yearly, monthly, weekly, daily, hourly or even by the minute.

Please refer screenshot below of typical Job Scheduling UI.

Recent Issues observed with MDRO Scheduling

Every MDRO instance running in the background consumes system resources in direct proportion to the amount of data processed and if these MDROs are scheduled to run very frequently there will be a direct impact on responsiveness of UIs and other activities for the end user.

Our analysis on recent performance issues reported by customers pointed to multiple MDROs being scheduled to run every minute, in most cases there were no valid business reasons for such frequent scheduling, especially in the area of SCM for ATP confirmation runs or MRP runs. These were either scheduled due to lack of awareness of negative effects on performance or due to the fact that users were not aware of any alternatives available to address their business needs.

What is the change in 1508?

In the August 2015 release of Business ByDesign restrictions have now been introduced in ‘By the minute’ recurrence to allow definition to every 15 minutes or at a higher interval. In addition the default recurrence interval has been changed to 30 minutes for ‘by the minute’ and to 4 hours for ‘hourly recurrence patterns.

This restriction will only be applicable for newly scheduled jobs and existing schedules which are still active will NOT be affected – however our recommendation is that such cases are analyzed and rescheduled with actual required frequency. We will initiate clean-up activities in the near future for such scheduled runs in consultation with customers.

If there are genuine cases where customers need job schedules to run within the 15 minute interval, they can contact Business ByDesign Support using the available channels.

What is needed from customers?

If a customer has such background jobs which have been scheduled to run more frequently than actual business needs, it is recommended to change those definitions at the earliest. The changes can be done by logging into the ByDesign system as a key user and following the path Application & User Management Workcenter -> Background Jobs -> All Scheduled Jobs -> Select the corresponding MDRO Job and choose Action ‘Reschedule’. Detailed guidelines are available in the help documentation.

The built-in analytics is one strength of SAP Business ByDesign. For your daily work, there is another great feature: The Excel Add-In. One functionality of it is reporting.

Nevertheless, there might be some confusion about accessing reports and report types. I'd like to share some insight into this miracle.

Not the Excel Add-In

First of all, there is one capability that has nothing to do with the Excel Add-In, but does open them in Excel, like a print out. In case you need a static representation of a report you have opened - just click on Download - Report in Microsoft Excel® in XML Format.

The report will open in Excel, and you will be able to format or add calculations.

Opening a Browser Report in the Excel Add In

A more interactive representation is either to use a report in Excel via Add-In. In the report view of each work center, you first select the report and then View With > Microsoft Excel. Important: The Excel Add-In should already be installed on your machine.

Alternatives to access reports that are also available as browser-based ones are those:

• When viewing the report in the browser, choose Navigate To > Microsoft Excel
  
  
  
  
• In the Excel Add-In, choose the ribbon SAP BUSINESS BYDESIGN (this is how it will appear - all upper case), Insert Report, will add a report to your Excel workbook.
  
  

In all these cases, your personally defined views and selections will be available in both - the browser and Excel.

Workbooks

Also more comprehensive representations, such as whole workbooks, can be used with the add-in. There are three types of workbooks.

• Public workbook - A workbook that is either predelivered with the solution or that has been defined by your key user analytics.
• Personal workbooks - A personal workbook is either a workbook created and saved by you, or a modification of a public workbook that you have stored in the solution.

Your personal workbooks will appear in the report list of the home work center. You might have already discovered it, but there is an additional button:

• Design workbooks - When creating the Excel Add-In, SAP's developer felt that there must be an authoring view for the key user analytics as well. This is comparable to the work center Business Analytics and can be used to define a report, before publishing it.
  Publishing is easily - just change your design workbook to Public Workbook (before, make a Personal Workbook a Design Workbook).

A Workbook is another great way to use ByDesign's Analytics. You can either store it in the solution, on your hard disk or sent via e-mail. The recipient is either able to see the data you have derived or is able to refresh - in case he has sufficiant access rights.

You can open workbooks either from the Work Center Home (there also your personal ones) or from the report lists of other work centers (public workbooks). When you are already in Excel, the SAP Business BYdesign ribbon will give you a button Open.

Introduction  : Based on the standard business process, SAP has defined  and delivered the creation of task (like (notification, approval task, escalation) ) under different circumstances   For example, if the authorization of the business user is changed, then user will get a notification informing that the authorizations are changed. If the user has subscribed for email then email would also be sent.

Apart from standard tasks, there can be some customer specific scenarios, wherein customers may want to define notifications or email to be sent based on their own conditions / criteria.

This requirement is now delivered as a new feature called “Workflow Rules”.

“Workflow Rules” can be defined by the key user at the customer end using

    Application User Management (Work center)->Workflow Rules (Work center view)

Workflow Rules contain the following steps:

1. Events when they should be triggered,
2. Condition which must be met for the rule to be executed
3. The operation that needs to be performed by the rule

Currently supported operations by the workflow rules are:

• Sending Email
• Sending Notification
• Field Update –Business object Field values  can be changed using this option
• Action execution – Business object action can be configured using this option

Problem Description : As per current implementation of our Purchase Order approval scenario, on submit (or Order) of purchase order, based on the approval process definition for purchase order, approval task will be created and assigned to the responsible. But once the purchase order is approved then there is no standard notification sent to the creator of the purchase order, informing that it is approved and the user can proceed further. Due to this there may be a delay in the further business processes.

Solution : Using the newly released feature of 1508 - Workflow Rules, key user can create a new rule based on the status change of Purchase Order. Based
on this a task/email (as configured in the rule) will be generated and sent to the person.

Solution in detail : 

1.  Navigate to the workcenter view to create a new Workflow Rule

From Application and User Management Workcenter, Navigate to Workflow Rules

This will display all the workflow rules maintained in the system

To achieve the above scenario, a new rule has to be created for this notification.

2. Click on "New" to create a new Workflow Rule

Customer has to choose the particular business object for which the notification has to be triggered.

Timing :  Timing has two options:

On Create only - Rule will be evaluated only on creation of the Business Object (very first save).

On Every Save -  Rule will be evaluated on every save of the Business Object ( only when the condition is met)

3.  Click on “Next” to create Conditions for the Workflow Rule

Workflow condition editor is same like Approval Process condition editor. To add a new condition, click on “Add Group”.Conditions within the group will be considered as “AND” in the condition expression.

For the Purchase order approved notification solution, maintain the condition as follows

4. Click on “Next” to create action type for the Workflow Rule

In Actions, customer has to define the rule type whether he needs notification or email for the business process.

Based on the rule type, relevant data needs to be maintained.

Notification Workflow rule:

  For notification rule type, customer can provide details as when the notification task should expire or cancelled.

Also in Notification based rule type, only four place holders allowed in the subject

Email workflow rule type:

In case of e-mail notification, there is no restriction for the place holders, but it is recommended to keep them as minimal for performance reasons

Template file which should be used for the email body needs to be uploaded in HTML format. The template can contain placeholders, which will be     expanded to actual value when the email is sent .

.

Sample Template for Email:

5. Add Recipient determination to determine the responsible

The recipient determination needs to be maintained for both the rule types.

Recipient determination can be SAP delivered determinations or else customer can specify the direct recipient.

6. Click on "Next" to review the Workflow details
In Review, all the details of the rule are shown for review. Once all the details are confirmed, then the rule can be activated by using
“Activate” button. Then finish the workflow rule definition by clicking on the “Finish” button.

Newly created workflow rule can be seen in the workflow rules list OWL

Customer can edit / delete the workflow rule during the business. Activated workflow rules can be deactivated by using the action
“Deactivate”

Lets see the Workflow Rule in action:

7. Approve a purchase order which is sent for approval.

As per the defined workflow rule, once the purchase order is approved, the creator of purchase order will get a notification.

Apart from email and notifications, Field update and action executions are also possible with work flow rules if the underlying business object has
enabled them.

Field Update: User can modify the attribute value of the business object instance using field update.Fields which are marked as editable in the workflow of
business object are displayed in here.

If the rule condition is met for the object instance then the field value will be updated as given in the workflow rule.

Field Action:  Business object actions can be exposed for workflow rules.

If the workflow condition is met, then the action will be called for the business object instance.

Summary: Apart from standard tasks, there can be some customer specific scenarios, wherein customers may want to define notifications or email
to be sent based on their own conditions.

This will be achieved with Workflow Rule. Along with the other notifications, workflow notification will also be sent to the User.

Prerequisites:

• Workflow Rules can be created only for business object that has been enabled by SAP .
• If there is a need to enhance existing workflow rule or need new workflow rule, then raise this as requirement using the known
  channels to request new features.

In this blog, we'd like to introduce you to one of  the things that is new or has been changed in the August 2015 version of SAP Business ByDesign.

Of course, you can find more information in the What's New in SAP Business ByDesign documentation, which is available online or as a pdf.

Today, we're going to talk about Custom Workflow Tasks.

You can create, edit and activate rules for flexible notification. Notifications are sent to business users to inform them when items have changed under various conditions, and to notify them of tasks to complete as a result of such changes.

Are you familiar with the What's New video in SAP Business ByDesign? You can have a look at it here

Want to read more, Check out this blog:

http://scn.sap.com/community/business-bydesign/blog/2015/07/27/how-to-create-workflow-rule-to-send-email-and-notifications

In this blog, we'd like to introduce you to one of the things that is new or has been changed in the August 2015 version of SAP Business ByDesign.

Of course, you can find more information in the What's New in SAP Business ByDesign documentation, which is available online or as a pdf.

Today, we're going to talk about Ocean Reef Theme.

SAP Business Bydesign has taken a whole new outlook with the new theme, Ocean reef. The new theme has a pleasant appearance with ocean inspired colors.

You can customize the getting started image.

To change the image, click on Adapt, select Company Settings. Under Getting Started Image tab, and upload the image.

Are you familiar with the What's New video in SAP Business ByDesign? You can have a look at it here

In this blog, we'd like to introduce you to one of  the things that is new or has been changed in the August 2015 version of SAP Business ByDesign.

Of course, you can find more information in the What's New in SAP Business ByDesign documentation, which is available online or as a pdf.

Today, we're going to talk about Service order with reference to Customer Contract.

You can now reference a contract in a service order. When an item is created, you can specify the relevant contract.

1.    Go to Service Orders work center > Service Order Processing view

2.     Click New, then choose Service Order to open the New Service Order quick activity.

3.     Under Services and Spare Parts, in the Contract Item column, you can give a reference to the relevant contract by entering the Contract Item ID.

If you cannot see Contract Item column, you have to add it by personalizing your screen. To do so, click Adapt >  Enter Adaptation Mode. In adaptation mode, Go to this screen. Click on Adapt > Edit Screen. Under “Fields”, select “Contract Item”. Publish your changes.

Are you familiar with the What's New video in SAP Business ByDesign? You can have a look at it here

In this blog, we'd like to introduce you to one of the things that is new or has been changed in the August 2015 version of SAP Business ByDesign.

Of course, you can find more information in the What's New in SAP Business ByDesign documentation, which is available online or as a pdf.

Today, we're going to talk about Sales Kits in Over the Counter Sales.

You can now create a sales kit in over-the-counter sales scenario.

1. Go to Over-the-Counter Sales work center > Over-the-Counter Sales view

2. Click New > Over-the-Counter Sales

3. Enter Account add sales kit  in items

The kit opens up to show all the kit items.

Are you familiar with the What's New video in SAP Business ByDesign? You can have a look at it here.

In this blog, we'd like to introduce you to one of the things that is new or has been changed in the August 2015 version of SAP Business ByDesign.

Of course, you can find more information in the What's New in SAP Business ByDesign documentation, which is available online or as a pdf.

Today, we're going to talk about Discount List based on Account Hierarchy.

You can now maintain discount list for every level or group in the customer hierarchy. To do so,

1. Go to Product and Service Portfolio work center > Pricing view > Discount Lists subview

2. Customer Hierarchy Specific Discount List” and “Customer Hierarchy Specific Discount Product Category” are the new additions.

Are you familiar with the What's New video in SAP Business ByDesign? You can have a look at it here.

In this blog, we'd like to introduce you to some of the things that are new in the August 2015 version of SAP Business ByDesign.

Of course, you can find more information in the What's New in SAP Business ByDesign documentation, which is available online or as a pdf.

You can also read more about some of the highlighted topics here.

Here is what we've presented so far:

• Ocean Reef Theme
• Workflow Rules
• Sales Kits in Over the Counter Sales
• Discount List based on Account Hierarchy
• Service Order with reference to Customer Contract
• ERS Supplier Invoice without Purchase Order
• MDRO Restrictions
• PDI Enablement of Document Flow

Are you familiar with the What's New video in SAP Business ByDesign? You can have a look at it here.

We’ll add blogs about other topics as we bring them to you. Stay tuned!

Hi All,

Until 1502 version of ByDesign we had a design limitation via which the cancellation of 3PL requests were not communicated to the warehouse providers automatically. The end users had to communicate this cancellation via manual channels to their relevant warehouse providers.

To incorporate the facility of automatically communicating cancellation of 3PL warehouse requests, what we have introduced from 1505 release is that if you cancel 3PL Request a new XML message will be triggered to your warehouse provider with the updated information of delivery quantity for the requested product as Zero.  You can find a snippet of the XML tag  below on how the information will look like when a cancellation of 3pl request is initiated.

We are still working on updating our documentation in the front end. However I believe this information will be helpful for every one to further streamline their 3PL process.  Please get back to me if you have any more queries on the same.

Regards

Anand

For all who are still struggling about starting a ISV partnership with SAP for ByD, C4C an actual webinar explaining the details of the program is now available on PartnerEdge portal.

Summary about the webinar:

Introduction to the SAP Cloud solution partner program available for SAP Business ByDesign and SAP Cloud for Customer ISVs. During the session you will learn the details and intention of the program, the related engagement process and services delivered to participating partnerns. The program was designed for partners who are interested in building extensions for SAP Cloud solutions like SAP Business ByDesign and SAP Cloud for Customer or integrating their own solutions to these SAP products. Also the related agreement and the conditions will be explained.

Link to the recording and presentation:

SAP PartnerEdge

A new service will be available mid of August 2015 for ISV partners.

As the pre-condition for posting a solution on SAP Store is a quality check by SAP, an affordable and quick service for all lightweights, mashups and integration solutions (only for integration projects supported by SAP development) towards ByD and C4C will be offered now, called Solution Review. This can help the ISVs to more easily decide on if they want to publish their soluiton on SAP Store or not.

The details about the service are available on the Business Center:

https://wiki.sme.sap.com/wiki/x/iAW9D

Dear PartnerEdge Partners,

There are 3  sessions beginning from August 25^th 2015, you are welcomed to register for these sessions using the registration links below,

1. Webinar: August 2015 Release updates for SAP Business ByDesign - SCM & HR

Overview of 1508 delta for SAP Business ByDesign, supply chain management (SCM) and human resources (HR).

TIME

16:30 (GMT 5.5) - Chennai, Kolkata, Mumbai, New Delhi

AGENDA

• Kits in over-the-counter sales
• Time recording – Error handling
• Split of save actions in the time administration time sheet

Registration Link:

https://partneredge.sap.com/en/library/education/products/entManage/byd/e_oe_te_arus_18786.html 

2. Webinar: August 2015 Release updates for SAP Business ByDesign – SRM and PRO

Overview of 1508 delta for SAP Business ByDesign, supplier resource management (SRM) and projects (PRO).

TIME

16:30 (GMT 5.5) - Chennai, Kolkata, Mumbai, New Delhi

AGENDA

• Evaluated receipt settlement (ERP) supplier invoices without purchase order
• Business Add-In (BADI) for scanned invoice language texts
• A2X service for purchasing contracts and goods and service acknowledgement
• Intrastat item work list
• Custom workflow tasks
• Mass simulation result of advanced approval value limits
• Purchase order header, item and supplier invoice approval app
• New approval condition process type for purchase order header approval

Registration Link:

https://partneredge.sap.com/en/library/education/products/entManage/byd/e_oe_te_rusb_18791.html

3. Webinar: August 2015 Release Updates for SAP Business ByDesign – CRM, Cross & Financials

Overview of 1508 delta for ByDesign CRM, Cross & Financials

TIME

16:30 (GMT 5.5) - Chennai, Kolkata, Mumbai, New Delhi

AGENDA

• Discount based on account hierarchy
• Service orders with reference to customer contracts
• HTML email templates for service request and service
• Workflow notifications
• Pre delivery inspection (PDI) enabled document flow
• Integration for payment advice

Registration Link:

https://partneredge.sap.com/en/library/education/products/entManage/byd/e_oe_te_crcf_18792.html

Note that you have to use the PartnerEdge user account to login firstly.

Thanks,

Adie