Conditional Scheduling in SAP BI Web Intelligence

Unlike in Crystal Reports, In SAP Web Intelligence, it is not possible to schedule based on conditions.

However, often times you can accomplish this with the Publications as follows.

Introduction

In our sample, we will use the eFashion sample Universe / Database.

The sample business case is:

If Sales Revenue for a given City drops below certain threshold (2 Million USD), I want the board of directors to be informed via email and a personalized report to be sent to this group.
However, if the Sales for a City are more than 2 Million but lower than 3 Million I want the store manager to be informed.

We assume in this sample that you are familiar with both SAP BI Web Intelligence, and with SAP BI Publications.

Let us now see the steps in detail:

1. Create a Webi document that will be used to pre-process the Dynamic Recipients list.

Here you put only the basic stuff that is needed to build the list for the recipients.

In this sample, I entered in the report body the fields City and Sales Revenue.

Then I have created a Variable, type dimension, with the formula:
=If [Sales revenue] <3000000 Then “areamanager@mydomain.com”

ElseIf [Sales revenue] <5000000 Then “boardofdirectors@mydomain.com”

Else “”

Then I added this variable to the table.  This is what I got:

Then I filtered to remove the rows than do not need an alert (Right click, Filter, Add Filter, etc. as per below image)

This is the filtered output.

One last suggested set of steps is to:

– set the page margins to 0  and

– remove the report title

– align the table to the top left immediately under the report header.

We want to do this because otherwise when creating the Webi doc used for the Dynamic Recipients list you may have some issues when it tries to identify the column names.

Then save it to the Enterprise, and test it from BI Launchpad, you want to be sure that it works

2. Schedule to Excel the Document created at step 1.

This will create the data provider for the final Dynamic Recipient List source document.

This step is necessary, because the condition is based on a variable, and the Publications engine is not able to process variables within a Webi Document. This is the reason why we need to create this intermediate Excel Data Provider, so that we will have raw data and not variables.

To do so:

Logon to BI Launchpad, go to the folder where you saved the Webi Document that will be used to create the data provider for the  final Dynamic Recipient List source document.

• In the Recurrence, select Run Now. (Later you will re-schedule it and here you will enter the required settings.  Bear in mind that this must be refreshed before the publication will be sent.)
• In the Formats select the output format: Microsoft Excel
• In the Destinations section, enter: File System

If you have only one node, better to save on the server itself, otherwise it is preferable to save the output xls in a shared location. In either case, you need to be sure that the specified user name and password are correct and that account has r/w access to the folder you are scheduling the xls to.

Now save it to enterprise with a name like “Dynamic Recipients Final”, and once again, go to the BI Launchpad and test that the document can be refreshed without any issues.

3. Create the WebI Document to be used as Dynamic Recipients list for the Publication

In Web Intelligence, create a new WebI document, based on Excel Personal Data Provider.

The source file is the XLSX file created by the schedule at step 3.

This document will be practically identical to the one created at Step 1, the only difference is that the field with the email address is no longer a variable, hence this can be used as a Dynamic Recipients List.

Once created the document, save to enterprise with a recognizable name, i.e. “Dynamic Recipients Final”

4. Create the Publication

From the BI Launchpad, navigate to the folder where you will store the publication, right click and Select New > Publication.

In the General Properties, enter the Title,

in the Source Documents enter the Report you created at point #3

Now, from the left menu, select the Dynamic Recipients option, and specify the Source for Dynamic Recipients, then click on OK, after which you must select the Query and Map the fields.

You must also flag the checkbox “Use entire list”.

Next step is to configure the Personalization, which will be used to deliver the personalized reports to the users.

Last step is to complete the Destinations, see example in the image below.

You can also refine the publication advanced settings according to your requirements.

PS: It is not in the scope of this document to explain how Publications work, for more information please review the Business Intelligence Launch Pad User Guide.

Now you can test the publication, and adjust where necessary.

5. Fine tune the recurrence for the various schedules

Once you have successfully tested the various steps, it is time to adjust the recurrence of the various schedules, so that you have consistent results.

It is not in the scope of this document to go too much in depth into the details; however, it is suggested to put in place measures that prevent data inconsistency.

For example, the Publication should run after the Dynamic Recipients list has been refreshed, and before this can happen, the XLSX with the pre-processed recipients list must have been produced.

You can accomplish this with scheduling based on events, which is covered in the BI Launchpad User guide (7.1.8).

Continue reading

Account Category Reference (ACR) - Grandfather of Automatic Account Determination Process

Every movement of goods is followed by movement type only and without movement type use / without help of movement type – no goods movement is possible in SAP. During goods movement of transaction posting, movement type trigger transaction event key and G/L account assignment triggers based transaction event key (OBYC) with valuation class where valuation class determines the valuation class available in material master which is used for transaction posting. For automatic account determination, the vital direct parameters involves are  movement type, valuation class, chart of account, valuation area, business key (transaction key), valuation grouping code{ valuation modification or valuation modifier}, account grouping code{general modification or general modifier },nature of G/L account ,posting keys and value string.

Moderately understandable, only large vital factor – valuation class in material master determine G/L account on goods movement for a movement type and then, all are happy on validation in/for business process by cross checking accounting entries in each case/stage. Essential regard to account category reference (which is very much responsible of having valuation class in material master), play grandparent role by being silent friend for success to automatic account determination process.

The account category reference (ACR) is an artificial code of four characters which allows flexibility in linking material type with valuation class. In reality, the valuation class is linked to an account category reference and account category reference linked to material type. In other term account category reference is used to simplify the assignment of permitted valuation class/valuation classes to the material type/ material types.

Business Case-1: How to use Account Category Reference

Based on requirement, business can have one material type, one account category reference and one valuation class by assigning material type to account category reference and then assigning account category reference to valuation class. For example business can have one custom material type ZROM (Raw Material) with custom account category reference (Z001) and new valuation class (3005) for Raw Material(Raw material – inventory managed with quantity and value)

During material creation with transaction code: MM01 with certain material type manually or by any uploading tool, only one permitted valuation class is defaulted for that material type by account category reference. So in material creation process no chance of making any mistakes by users or by any uploading tool.

Business Case-2: How to use Account Category Reference

Based on requirement, business can have one material type, one account category reference and multiple valuation classes by assigning material type to account category reference and then assigning account category to valuation classes. For example business can have one custom material type ZROM (Raw Material) with custom account category reference (Z001) and new valuation classes i.e. (3005) for Raw Material, (3006) for Chemicals and (3007) for Filter material (all materials are inventory manage with quantity and value)

During material creation with transaction code: MM01 with certain material type manually or by any uploading tool, only permitted valuation classes are defaulted for that material type by account category reference . Here, there is a chance of entering wrong valuation class by user manually or through upload file using a tool which needs to be validated.

Business can go for designing a custom transaction code where material can be created through uploading file which can be verified by central material creation officer.

Business Case-3: How to use Account Category Reference

Based on requirement, business can have multiple material types, one account category reference and multiple valuation classes by assigning material types to account category reference and then assigning account category reference to valuation classes. For example business can have three custom material types such as  ZROM (Raw Material), ZCHE(Chemicals ) and ZFIL(Filter material ) with one custom account category reference (Z001) and three new valuation classes ie.. (3005) for Raw Material, (3006) for Chemicals and (3007) for Filter material (all materials are inventory manage with quantity and value)

During manual material creation with transaction code: MM01 or material creation by any uploading tool, only permitted valuation classes are defaulted for that material type by account category reference. Here, entering correct combination of material type for material and valuation class are expected through manually or through upload file which needs to be validated.

Business can go for designing a custom transaction code where material can be created by referring uploading file which can be verified by central material creation officer.

Also business can think of having “material master creation form” for any new material master creation, if necessary material code/ material number is not available in system – User/Users can fill the “template of uploading file’ with duly filled “material master creation form” and send for approval.On appropriate check and verification with approval from approving authority, if central material creation officer is happy, then he /she can upload file with custom transaction code for new material code.

Continue reading

Identify changed data on screen in Web dynpro ABAP

AT times we require to check whether the editable fields are actually changed in value by the user or not.AS we all know that the values in the web dynpro component are stored in the context via nodes and attributes, there is a way to acheive this without much of coding. This documents gives the step by step procedure for the same.

The component here has a node which in turn has an attribute associated with it.

The purpose of this attribute is to bind it with an input field, now we will create the layout after creating this node in the context.

The layout of view is as below

On the click of this button we will be checking whether user has entered something in the input field or not, this can be modified as a “SAVE” button on screen wherein we can now check whether user has actually entered something or not or user has actually entered a new value here or not.

For this We will Enable the context change log in the WDDOINIT of component controller, please note that since the node was created in the component controller we write the code in WDDOINIT of the component controller, in case this was declared in view the below code has to be written in WDDOINIT of the view.

create a method in component controller , here its named as “GET_CHANGE_LOG” and code as below. this method will be called from the view.

The table IT_LIST will have values when the field is changed from the previous value else that would be “INITIAL”.

Below are the test results:

Execute the application and press the button without entering any value

The internal table IT_LIST would be having no enteries.

Now enter some value in the input field and press the button

This time the internal table would have an entry as the context value was changed from previous held blank value

Continue reading

Pricing procedure Steps and Details in SAP MM

What is Pricing procedure?

The main concept of pricing procedure is combination of different type charges, like Gross price, freight, discount, surcharges etc etc.

We use pricing procedure to determine these all conditions into one procedure, where we can find the sub-total for net amount.

To understand pricing procedure we have to comfortable with these below things:

1. Condition Table

2. Access Sequence

3. Condition Type

4. Condition Record.

5. Schema Group

6. Calculation Schema

7. Schema Determination

Let’s discuss about all these points in details.

1. Condition Table

It’s a table where we can save the all fields with the combination for individual condition record. Suppose if I use Plant as condition table, then the condition record will be created for plant only.

We can use many fields in one condition tables.

2. Access Sequence

The main concept of Access sequence is, it searches condition record for condition type from condition table.

One access sequence contains many condition tables.

Suppose we maintain 4 condition tables in one access sequence. Then when a condition type will be searching for condition record via this access sequence, the access sequence will allow to search only this 4 condition tables.

3. Condition Type

In simple term, condition type is used for different type of charges. Like gross price, discount, freight, rebate etc etc.

Suppose we purchase a material for price 10, we get a discount of price 2. Then the price 10 will be going to a condition type and the price 2 will be going to another condition type.

4. Condition Record

Condition record contains the record which is maintained against condition table with regards to condition type.

It can be fetched via access sequence and condition type.

Suppose we maintain a condition record against condition table (vendor) with regards to condition type. Then whenever the vendor used this condition type, the condition record will be fetched.

5. Schema Group

It’s assigned to our vendor and Purchase Organization, It helps the vendor and purchase organization to choose pricing procedure.

One schema group will be assigned to vendor and one schema group will be assigned to Purchase organization. With this combination, system will fetch the pricing procedure.

6. Calculation Schema

Here we maintain sequence for the pricing calculation, like gross price, discount, rebate, surcharges etc. Here we maintain the calculation for all condition types and group together all required condition types for our pricing procedure.

7. Schema Determination

Here we maintain the pricing procedure for purchasing document. We maintain calculation schema combination of per each vendor – schema group and each purchase organization – schema group.

In general, below image will give the concept how a condition type will search for the condition records :

Configurations:

Step 1 : Maintain Condition Table

T-code M/03 or Path SPRO-IMG-MM-Purchasing-Conditions-Define Price Determination Process-Maintain Condition Table-Create condition table.

The initial screen will be appear for create condition table.

Give the new condition table no. You can use old condition table number as reference. To give reference just give the old condition table number in below “copy from condition table”.

Note: As per standard SAP, they give the entire condition table for general business requirement. If any condition table doesn’t fulfill your requirement, then you can create new condition table. Please use between 501 to 999 as condition table.

Now press enter

You can see the left side will be blank in initial screen, Right side will be always filled. Just double click on the right side field which you can add for this condition table.

When you double click the field the field will be blue colour and the field is appear in left side.

As we can see the 1 field I have selected in this condition table.

Save your data.

You can change the option as per your business requirement. For more details for these options, just press F1 on these option, you will find sap help doc.

Step 2: Maintain Access Sequence

T-code M/07 or path SPRO-IMG-MM-Purchasing-Conditions-Define Price Determination Process-Define Access Sequences.

The initial screen will appear.

You can create a new access sequence or maintain the condition table in existing access sequence (depend on your business process)

If you want to create then click New Entries. (Or you can use copy reference, Just select the access sequence and press Copy as…)

Enter your Access Sequence and give the description and also you can choose Access category.

Then select the AS and double click on Accesses

Click on New Entries

Enter the access number, condition table and if required the give routing number and Exclusive.

If you tick exclusive indicator, then if valid condition record found then system will stop searching after the first.

Choose as per your requirement.

Then select the line item and click on the fields (left side) to activate the condition table in access sequence. You do not need to do anything here, just double on the fields and go back. If you will not do that, then your condition table will be not accessible. You can add more condition table (s) on this access sequence.

Save your data.

Step 3: Maintain Condition Type

T-code M/06 or path SPRO-IMG-MM-Purchasing-Conditions-Define Price Determination Process-Define Condition Types-Define Condition Type

The initial screen will be appear 

As for gross price SAP default maintain as PBXX for time independent condition and PB00 for time dependent condition.

Time Independent condition is use with validity period, which can be differ as validity period (we use it in info record, RFQ, Contract, SA(as per configuration for document type)).

So we don’t need to create new condition type for gross price, although you can create your own starting with Z.

Assign you newly created access sequence to the gross price condition type (I have maintain in for PBXX)

Here you can find all types of condition type like as freight, discount, rebate, cash discount etc. If it can fulfill your requirement, then no need to create new condition type. If doesn’t the go for New Entries.

Here I have maintain ZCAH as discount, I give condition class A, Calculation type A, Plus/Minus X-Negative

(Note: Not required to maintain like that, you can maintain as per your requirement.)

As per this way please create other condition types as per your requirement (which will be used in Pricing Procedure)

Save you data.

Step 4: Maintain Calculation Schema

T-code M/08 or path SPRO-IMG-MM-Purchasing-Conditions-Define Price Determination Process-Define Calculation Schema

This is very very important part in pricing procedure.

Here we give the calculation for all condition types.

Here also you can find the SAP default calculation schema, you can also use one of them as your pricing procedure. Although you can create new calculation schema as per your requirement.

Just click on New Entry. (or you can copy old schema and can modify yourself. then select copy as…)

Give the name and description for new procedure.

Then Select this procedure and press Control (in left side)

You can see a lots of option there, You can read all option help which is provide by SAP (Just select the portion and press F1)

Maintain PBXX as gross price in step 1, counter 1, leave the from and to blank, Subtotal will be value 9-Copy values to KOMP-BRTWR (gross value).

Maintain other condition types as per your requirement.

I have maintained ZCAH and ZCAS, I have used from 1, it means it will calculate the value against Gross Price (PBXX)

I have used Total Discount amount, from 7 to 9, It shows the total discount value (Total of ZCAH and ZCAS)

At last I have used TOTAL AMOUNT, It shows net value for this pricing procedure.

Step 5: Maintain Schema Group for Vendor

T-code OMFN or path SPRO-IMG-MM-Purchasing-Conditions-Define Price Determination Process-Define Schema Group-Schema Groups: Vendor

Just click on New Entries and enter the Schema Grp Vndr and give the description.

Here I have maintained Z1.

Step 6: Maintain Schema Groups for Purchasing Organizations

T-code OMFM or path SPRO-IMG-MM-Purchasing-Conditions-Define Price Determination Process-Define Schema Group-Schema Groups for Purchasing Organizations

Just click on the new entries and enter the Schema GrpPOrg and description.

Here I have maintained ZMM1.

Step 6: Assign Schema Group to Purchasing Organization

T-code OMFP or path SPRO-IMG-MM-Purchasing-Conditions-Define Price Determination Process-Define Schema Group-Assignment of Schema Group to Purchasing Organization

Here find your Purchase Organization, and assign Schema GrpPOrg to Purchase organization.

Step 7: Maintain Schema Determination

T-code OMFO or path SPRO-IMG-MM-Purchasing-Conditions-Define Price Determination Process-Define Schema Determination-Determine Calculation Schema for Standard Purchase Orders

Step 8: Assign Schema group to Vendor

When you are going to create a vendor from XK01 in purchasing data you will find “Schema Group, Vendor”

Here assign the schema group which you have created on step 5.

You can also maintain it on existing vendor via XK02.

Step 9: Maintain Condition Record

T-code MEK2

Maintain the condition record against the key combination.

Save your data.

Finally all configurations has been done.

Now see the result.

Create PO with this purchase organization and with this vendor.

We can see the my new pricing procedure is working perfect.

We can use this in SA.

Just we have to configure this for document of schedule agreement.

Go to path SPRO-IMG-MM-Purchasing-Scheduling Agreement-Define Document Types

Just un-tick Time Dep. Condition for SA document type.

Then Create SA for this vendor and purchasing organization.

This is called time independent condition. You can also use this pricing procedure for RFQ. But Contract and Info record will be always time dependent condition.

Time Independent conditions are not dependent on time. It hasn’t any validity period, that means it will be always same for all time. The above settings are for time independent condition. Whenever you will use time independent condition, then you need to do these above settings.

Time dependent conditions are always time dependent. It has the validity period. You can use more than one price for the same condition record with different validity period, so that system will change it automatically as per the validity period.

I think I do not need to explain anything more about the differences Time dependent condition and Time Independent condition because there are many discussions already there for the differences.

You can use either time dependent or time independent for Schedule Agreement and Request For Quotation but you can only use time dependent condition for Contract and Info record and for Purchase Order, you need to always use time independent conditions.

For time dependent settings, you just need to set the up the condition type, Access sequence, Condition table and Calculation schema. Schema group is not needed for the time dependent condition.

We can also maintain the fixed discount for particular vendor.

Suppose one of my vendors gives me material as 5 % discount for all material.

We can maintain it in condition record.

Go to MEK2

Click on Supplement Condition. Maintain there your condition type for ZCAH as 5.

You can see the default 5% discount has been automatically arrived in PO or SA.

You can only able to see these condition types which is associated with the condition type which you have entered at the first screen and it will be your gross condition type.

To add some more condition type, you need to add these condition types in the associated calculation schema. To find the calculation schema which is associated with the gross condition type, you need to go to M/06 and you will find the calculation schema as below:

You can add your condition type in this calculation schema in t-code M/08. Then your condition type will be visible for time dependent condition (MEK1) or Info record or Contract.

Continue reading

Workflow in SRM User Interface Add-On 1.0

This blog provides insights about workflow in SRM Shopping Cart UI Add-On, draws parallel with Webdynpro and talks about how different workflow scenarios are incorporated.

To begin with SRM SC UI Add-On supports both AC and PC workflows. There is no additional configuration required. The existing configuration data is read and approver or approval chain is determined.You can also add adhoc approvers and reviewers. Let us take a look at what’s in store for workflow scenarios in SRM UI Add-On.

Approval preview:

The approval preview has a different look and feel as shown below:

Clicking on ‘Add approver’ will open up the following row where you can search for approver via first name, last name or user ID:

Here if you have to add an adhoc approver above current level then you have to choose sequence number as ‘001’ from the drop down; if you want to add approver after current level then you choose sequence number as ‘002’ from the drop down and then click on add to add adhoc approver.

In AC workflow, you can also replace existing approvers.

Workflow scenarios:

• Recall scenario:

Once a shopping cart is ordered, you can edit and recall an awaiting approval cart as shown below:

We do not have ‘show my task’ button in UI addon, but we open an awaiting approval cart directly in edit mode from ‘my carts’ tab when user has recalled that cart and has a valid revision workitem associated with it. This holds good for AC and PC workflow.

PC workflow:

Changed data in carts with PC workflow is saved by using enter key and user can add new items to the cart.

AC workflow:

User has to click on save in order to save changed data and thereby cart will switch to display mode You cannot add new items after recalling an AC workflow cart.

• Inquire scenario:

User can open accept/adjust workitem from Suite Inbox and UWL. You can accept the decision or edit the cart. This holds good only if cart is created from SRM UI Add-On.

UWL configuration:

Please refer note 1892681 to set up UWL for UI Add-On. This configuration is only for employee user. Employee can access Accept/Adjust and Revision workitems from UWL via UI Addon if shopping cart is created in UI Addon. Alternately you can also use Suite Inbox in order to access these workitems.

Continue reading

Steps for opening and closing period – MM FI CO

As many of us struggle with changing periods in our DEV and QA environments, here is quick reference for opening and closing period. In doubt, please consult with your FI/CO expert.

There can be upto four transaction involved depending on your situation.

◉ MMRV – Allow posting to previous period
◉ MMPV – Close Periods
◉ OB52 – Change view “Posting Periods: Specify Time Intervals”: Overview
◉ OKP1 – Maintain Period Lock

1. MMRV: View current period / Allow posting to previous period

This transaction allows you to view current period and change setting for posting to previous period.

2. MMPV: Close Periods

In MMPV you can execute period closing up to the end of the current fiscal year. The period closing program updates the administration record, thus ensuring that the stock data of the material master are updated.

If, for example, you want to close your periods up to 03/2013, you are not allowed to post values in 01/2013. Therefore, if you still want to make postings in period t, you should execute period closing only for a maximum of t+1 periods.

3. OB52: Change view “Posting Periods: Specify Time Intervals”: Overview

In this activity, you close the posting periods for FI-AA and open the new periods for FI-AA.

No more FI-AA postings can be made to the previous period. Postings for the future periods are allowed.

4. OKP1: Maintain Period Lock

If needed, unlock period for CO transaction.

If I have missed anything here or misinterpreted, let me know and I will correct it or add additional clarification/tips.

Continue reading