SAP Public sector implementation

2008-09-05T13:45:00.000-07:00

Step 1: Deactivate the &* functions and operation

1. Transaction PE04

And select the &* entries

Other than &DECI, please follow the steps as follows. In this document I’ll show the steps for &CURR.

Select &CURR and Enter:

Press Change and acknowledge the information:

In the Country assignment, Scroll down and you will see the entry Non profit Organization Checked.

Uncheck the entries. It should look like

Save and Exit.

After repeating this step for all &* Entries, go to transaction SE38, and check the program HUNCALC0. This program should not have any syntax error. If it has any then the deactivation of one &* feature is not done correctly. Please repeat the steps.

Note: Do not deactivate &DECI

Step II: Regenerate all $TMP objects to make them Unicode compliant.

Transaction SE38 and execute report RPUMKG00 (Based on the note 573044)

That’s all.

2008-09-04T06:58:00.000-07:00

If the data transfer Workbench (SXDA) does not have the necessary structure.

To correct this we need to maintain entries in the following two tables: SXDA2 (SAPDXfer: Structure Info for Data Transfer Object) and SXDA3 (SAPDXfer: Field Info for Data Transfer Object). Once you have the entries here these tables, the data transfer programs will start recognizing and parsing the input structures accordingly.

Let’s see the step by step procedure for maintaining the infotype 1080 in the SAP HR module. The corresponding structure is E1P1080. For this purpose, the Key for data transfer object is 0777. How did we find that out? By debugging the upload program and I will check if there is any better way to do this.

Since these structures are not available, all we have to do this is to add this structure in the SXDA2 table and the key fields in the SXDA3 table.

For SXDA2 table, let’s see the available components in the 0777 key. The way to see is transaction SM30 and maintain the list with key 0777.

The last position was 83 and the structure was E1P1063.

To add, press the ‘New Entries’

And Add the new info type like the following:

And press the Active button.

And confirm the following message.

In the same way do the changes to the SXDA3 table, which is going to have the key elements. Use transaction SM30 and maintain SXDA3.

Confirm the following message:

Position on the key 0777 and the item 83 (Which was the one we identified as the last item existed in SXDA2 before our addition. We added item 84)

Create ‘New Entries’ as below:

Remember to check the Active box. Save the entries confirming the following:

Save the changes in a transport.

Repeat the same for the following key fields:

That’s all. The whole process can be repeated for any new structure that needs to be used in the data transfer workbench.

Implicit enhancement points - Changing standard SAP code using the implict enhamcement code points

2008-08-15T13:23:00.000-07:00

Implicit enhancement points are basically points within ABAP code where an enhancement point is implied, and in which case can be created. Examples of implicit enhancement points are at the beginning and end of FORM’s, at the end of a program, include or function module etc. Below is a step by step demonstration of how to create and implicit enhancement point.

Step 1 - Activate the enhancement functionality
Within SE80 open up the program/include you want to enhance and click on the enhancement button (show below)

Step 2 - Enhancement functionality activated
The SE80 screen will now look something like below!

Step 3 - Show implict enhancement points
Goto menu 'edit->Enhamcement Operations->Show Implicit Enhancement Options' to display implicit enhancement points within the ABAP code

Step 4 - Enhancement points with the code
Once you have done this you will be able to see all the implicit enhancement points available within you code, these are denoted by the line of quotation marks and the black arrow at the start. In this example there are enhancement points at the start and end of each form and one at the very end of the include.

Step 5 - Create an implicit enhamcement point
Inorder to implement an implicit enhancement point simply right click on the required enhamcement point and select 'Enhancement Implementation->create'.

Step 6 - Enhamcement point type
Next click on the code button to create a code implementation

Step 7 - Name and description
Next give the enhancement point a name and description. Click the green tick

Step 8 - Change request
Assign change to a change request in the usual way

Step 9 - Enhancement point created
The enhamcement point will now have been created in the appropriate place. Denoted by the ENHANCEMENT...ENDENHANCEMENT tags

Step 10 - Enter code into enhancement
You can now enter your own code into the enhancement point!

Step 11 - Activate the enhancement point
Click the 'Activate Enhancements' button to activate it.

Step 12 - Turn enhancement mode off
Now click the 'Active <-> inactive' button to turn enhancement mode off and return to standard SE80

vacation

2008-08-06T18:14:00.000-07:00

Day 1
* Julius Sturgis Pretzel Bakery

Julius Sturgis Pretzel Bakery Description

What's better than being handed a big, squishy wad of dough and being taught how to twist it into a pretzel? That's what happens at the start of the Julius Sturgis Pretzel Bakery tour. The tour explores the large space where Sturgis started the first pretzel bakery in the U.S. back in the late 1700s. The guides are animated and enthusiastic, and at only 20 minutes or so the tour's short enough to hold the interest of most kids. Children will get some giggles out of the see-saw-like device used to knead pretzel dough.

Toddlers & Pre-K: The pretzel dough is just like that other kind of dough that gets in your carpet. Ward off tantrums by warning kids that they don't get to keep it.
Just the Facts

Hours: Bakery Tours Mon.-Sat. 9:30a.m.-4:30 p.m. Closed Sunday Bakery Store Mon.-Sat. 9 a.m.-5 p.m. Closed Sunday

Fees: Under $10

Planned Time: Less than 1 hour

* Abe's Buggy Rides
Abe's Buggy Rides Description

Abe's is a combination buggy ride provider, petting zoo, and miniature snack bar. Catering primarily to families, you can choose to ride in authentic Amish buggies of varying sizes for 20 to 75 minutes. Any ride longer than 20 minutes will take you under a covered bridge and past Amish farms and houses. Have your driver sign your feedback card upon your return and you'll get a homemade cookie or whoopee pie.

Toddlers & Pre-K: Animals, a buggy ride, and a big pond with koi fish. Need we say more?

Just the Facts
Hours: Mon.-Sat., 9 a.m.-6 p.m.
Fees: $10 - $20
Planned Time: 1 to 2 hours

* Hands-On House Children Museum

Hands-On House Children's Museum Description

"Don't touch that" are words you will not hear at the Hands-On House Children's Museum. While it's obviously big on hands-on, interactive elements, the museum also has a distinct Lancaster County flavor, with fun exhibits about machinery and farming. While the museum is on the small side, its interactive focus keeps kids happy and engaged.

Toddlers & Pre-K: Perfect place to let little ones run around safely.

Just the Facts
Hours: Vary by season.
Fees: Under $10
Planned Time: 1 to 2 hours

Day 2
* Dutch Wonderland Family Amusement Park

Dutch Wonderland Family Amusement Park Description

The excitement starts when you walk through the big castle faÃ§ade into Dutch Wonderland. With about 30 rides, this meandering, shady park isn't overwhelmingly large, but there's plenty of fun for kids up to age 12. Mini-theaters throughout the park provide short, entertaining shows and skits that will excite kids and give parents a chance to sit for a bit. Kids will love the royal treatment -- you might even see the Dutch Wonderland Princess or Duke, who regularly appear at events and sometimes even wander the park doing meet-and-greets with children

Toddlers & Pre-K: A selection of gentle attractions ensure that little ones can get equal time on the rides.

Just the Facts
Hours: Park is closed January through April. Hours vary by month. For specifics, visit http://www.dutchwonderland.com/hours/index.html.
Fees: $20 - $30
Planned Time: Full day

* Plain and Fancy Restaurant and Farm
Plain and Fancy Restaurant and Farm Description

When you're given the choice between ordering the Amish Farm Feast or off the menu, go for the feast. You'll be seated at a table with people you don't know, but that makes it more fun to pass around the heaping platters of fried chicken, ham, turkey, buttered noodles, green beans, and so much more that will come your way. Save room for dessert -- your kids will love the apple and shoo-fly pies topped with ice cream and whipped cream.

Day 3
* Strasburg Rail Road
Strasburg Rail Road Description

It's almost impossible not to get excited when you hear the steam train's booming horn as it closes in on the station. Larger than life, the coal-fueled steam engine is lovingly restored. Children will delight in riding the rails to Paradise (Pennsylvania, that is) while listening to the conductor note points of interest, such as the Amish farms and the Red Caboose Motel (which features real train cars as sleeping rooms). At the end of the route, your kids will love shouting and cheering for the engineers who will hook up an engine to the "back" of the train and take it on its 20-minute ride to the station.

Toddlers & Pre-K: Windows can be opened, and are just the right height to climb up to (and through!). Remind little ones to keep their hands in the car.

Just the Facts
Hours: Changes frequently. Best to check the online calendar at www.strasburgrailroad.com.
Fees: $10 - $20
Recommended Time: 1 to 2 hours

* Cherry-Crest Adventure Farm

Cherry-Crest Adventure Farm Description

Get a good night's sleep before you visit Cherry-Crest Adventure Farm and its five-acre corn maze, the Amazing Maize Maze. With more than 2.5 miles of trails, the best-case scenario is that it's going to take you an hour to get through, although some have taken five hours. That's OK -- there's a snack shack and bathrooms inside the maze, plus a few places to sit and rest.

In addition to the maze, there are dozens more attractions on the farm, including a petting zoo, the Barnyard Jump bouncy "pillow," obstacle courses, hayrides, pumpkin tosses, the Lil' Farmers Playground, and a singing chicken show. The fudge shop and Home Cookin' Cafe keep everyone fueled for maximum play time. Or, bring a picnic and enjoy it under the tents in the Barnyard area.

Toddlers & Pre-K: There is a tiny version of the maze set up with hay bales. Forego the big maze and enjoy the other activities on the farm, including a stuffed animal workshop.

School-Age Kids: Run, run, run! When they get tired, you can always take the emergency exit out of the maze. Still, you may be surprised at the motivation of making it all the way through.
Just the Facts

Hours: Vary by month and day. Check the website at https://www.cherrycrestfarm.com/schedule.asp
Fees: $10 - $20
Recommended Time: 2 to 4 hours

* Amish Farm and House
Amish Farm and House Description

Yes, it's right off the highway behind Target, but don't pass by this delightful and authentic stop in Pennsylvania Dutch Country. Complete with a covered bridge and deeded by William Penn, the farm is almost exactly like it was in 1805, the year it was built. A one-room school house on the property gives a glimpse of how many Amish children are schooled to this day. Kids will love the super-cool 1805 Conestoga wagon, animals -- including horses, pigs, cows and goats -- and lots of space to run around.
Toddlers & Pre-K: There are goats to pet and a playground to be conquered. Life is good on the Amish Farm.

Just the Facts
Hours: Vary by season.
Fees: Under $10
Recommended Time: 2 to 4 hours

Working with Workflow container macros

2008-05-13T07:37:00.000-07:00

Working with Workflow container macros:

Macros for accessing objects

Accessing objects in the business object repository is currently supported by a set of macros. These macros are described in more detail in the following.

All macros are comprised in the Include . This Include is contained in the Include , therefore making these macros automatically available in all object type implementations. Client programs which work with objects should use .

If the macros are used in ABAP Objects classes, use the includes and . contains the actual macro definitions; include it in the macro section of the class. Some attributes addressed from are defined in . must be included in the type section of the class.

Container

Containers are used for dynamic transfer of parameters and result values. The following macros are available for processing them:

Macro

Description

swc_container Declare a container

swc_create_container Create a new container

swc_release_container Release a container

swc_clear_container Clear a container

swc_create_element Create element in container

swc_set_element Insert element in container

swc_set_table Insert multiline element in container

swc_get_element Read element from container

swc_get_table Read multiline element from container

swc_delete_element Delete element from container

A detailed documentation of the container macros is provided in the SAP Library under: (Basis -> Business Management -> SAP Business Workflow Navigation -> Business Object Builder -> Programming in Implementation Program).

Object references

Declaration

DATA: TYPE SWC_OBJECT

Variables which contain object references are defined with the type SWC_OBJECT. A special case within the object implementation is the system variable SELF, which contains a reference to itself.

Create

SWC_CREATE_OBJECT

Object references are created using the macro SWC_CREATE_OBJECT. The first parameter received by the macro is the variable in which the reference is returned, the second parameter the type of object which is to be created, and the third parameter the key of the object.

Delete

SWC_FREE_OBJECT

The macro SWC_FREE_OBJECT can be used to release existing object references. The macro receives the reference to be released as input.

Read type and key

SWC_GET_OBJECT_TYPE

The macro SWC_GET_OBJECT_TYPE can be used to read the object type belonging to the object reference. The first parameter received by the macro is the object reference, the second parameter the return parameter containing the respective object type after the call. The field SWOTOBJID-OBJTYPE can be used as the data type reference for the object type.

SWC_GET_OBJECT_KEY

The macro SWC_GET_OBJECT_KEY can be used to read the key of an object. The macro is passed the reference of the object whose key is to be read as the first parameter and returns the key in the second parameter as the result. The field SWOTOBJID-OBJKEY can be used as the data type reference for the object type.

Method access

SWC_CALL_METHOD

The macro SWC_CALL_METHOD can be used to call methods of objects. The first parameter contains the object reference, the second the name of the method. The container holding all input values is passed in the third parameter. If the call is successful, the result (container element _RESULT) and the export parameters of the method call are stored in the container. If the invoked method raises an exception, the number of the exception is contained in the system variable SY-SUBRC and other values in the variables SY-MSGV1, ..., SY-MSGV4.

Attribute access

Read

SWC_GET_[TABLE_]PROPERTY

The macros SWC_GET_PROPERTY or SWC_GET_TABLE_PROPERTY can be used to access the attributes of an object. Both macros receive the object reference in the first parameter and the name of the attribute which is to be accessed in the second parameter. Both macros return the value of the attribute in the third parameter as the result. SWC_GET_PROPERTY returns single attribute values, SWC_GET_TABLE_PROPERTY returns multiline attribute values as internal tables.

Refresh

SWC_REFRESH_OBJECT

Attributes which are references to database fields are only read from the database for the first access. To refresh attribute values, the macro SWC_REFRESH_OBJECT can be called, causing the database to be read again the next time the attribute is accessed. The macro contains the object reference as an input parameter.

Trigger events

SWC_RAISE_EVENT

The macro SWC_RAISE_EVENT can be used to trigger events of object types. The reference to the object is passed to the macro as input in the first parameter, the name of the event in the second, and the container with the parameters for the event in the third parameter.

Special features within object type implementations

In addition to the macros listed above, contains macros which can be used within object type implementations.

Object reference to self

An own instance within the object type reference can be referenced with the variable SELF. This reference can be used to request attribute values of the current instance with SWC_GET_[TABLE_]PROPERTY.

Set object key

SWC_SET_OBJECTKEY

The macro SWC_SET_OBJECTKEY can be used to set the key of the object within method implementations. This is practical for methods such as create or find which link an object reference to a persistent object - which may be newly created.

Raise exceptions

EXIT_RETURN Publish Post

Within object type implementations, methods can raise exceptions which are defined in the method interface. To do this, the macro EXIT_RETURN is called which is passed the number of the exception and four result values as input. The result values can also be SPACE if they are empty.

Example

The following example is an extract from the example program RSWOCLNT. It uses the object types SCHEDULE, DOMINANT und APPOINTMENT from the SAP appointment calendar (transaction SSC1).

The program first lists the dominants (attribute DominantOfToday) and the appointments of the day (attribute AppointmentsOfToday), and then the appointments of the last and the next 5 days (method AppointmentsGet). Before the program is executed, appointments should be created in the calendar (SSC1).

REPORT RSWOCLNT.

***** use of container macros
INCLUDE .

***** object reference declaration
DATA: SCHEDULE TYPE SWC_OBJECT.

***** object reference creation
SWC_CREATE_OBJECT SCHEDULE 'SCHEDULE' SY-UNAME.
IF SY-SUBRC NE 0.
.....
ENDIF.

***** access to attribute
DATA: DOMINANT TYPE SWC_OBJECT.
SWC_GET_PROPERTY SCHEDULE 'DominantOfToday' DOMINANT.
IF SY-SUBRC NE 0.
.....
ENDIF.

***** access to mulitline attribute
DATA: APPOINTMENTS TYPE SWC_OBJECT OCCURS 0.
DATA: APP TYPE SWC_OBJECT.
SWC_GET_TABLE_PROPERTY SCHEDULE 'AppointmentsOfToday' APPOINTMENTS.
IF SY-SUBRC = 0.
LOOP AT APPOINTMENTS INTO APP.
.....
ENDLOOP.
ENDIF.

***** method invocation
DATEFROM = SY-DATUM - 5.
DATETO = SY-DATUM + 5.
* create container
SWC_CONTAINER CONTAINER.
* fill container
SWC_SET_ELEMENT CONTAINER 'DateFrom' DATEFROM.
SWC_SET_ELEMENT CONTAINER 'DateTo' DATETO.
* call method
SWC_CALL_METHOD SCHEDULE 'AppointmentsGet' CONTAINER.
IF SY-SUBRC = 0.
REFRESH APPOINTMENTS.
* read method result
SWC_GET_TABLE CONTAINER '_RESULT' APPOINTMENTS.
LOOP AT APPOINTMENTS INTO APP.
.....
ENDLOOP.
ENDIF.

Common workflow issue

2008-03-25T10:40:00.001-07:00

No Administrator Found for the task

This is a common error faced by many people during execution of the work items. In such cases, do the following:

Execute SWU_OBUF to reset the buffers. If the problem still persists, go to step 2.
SO01--> settings --> workflow settings-->refresh organization environment

2008-02-10T12:50:00.000-08:00

ABAP Review Check List

This is a work in process. Please feel free to ask questions, make suggestions & correct misinformation!
Siva Kumar at sthiagarajan@unicef.org

Mandatory Checks

I. Documentation

II. Naming Conventions

Variable Names

Selection options = s_
Internal tables (global) = t_
Internal tables (local) = lt_
Constants = c_
Ranges = r_
Form parameter = p_ (Used in the actual form not the Perform statement.)
Screen Parameters = a_ or p_
Program & Function Group Names
UNICEF SAP development guidelines Appendix B (You need to log in to Unicef's intranet to get this document)
ABAP programs (reports), function groups and module pools all use a 2 character application name abbreviation. The list of current UNICEF applications will be maintained in Appendix B.

III. Attributes

Authorization Group in attributes - Programs that can be executed by all UNICEF users must be configured using the Authorization Group 'ZOPN2ALL' for Application '*'.
Development Class needs to be application specific. This standard is a work in process.

IV. Return Codes

Test return codes (sy-subrc) for success and failure after any I/O and calls to function modules (database selects, internal table reads, call transactions, I/O to UNIX or workstation files, etc)

V. Transaction Code assigned to executable programs

Every type "executable program" must have an assigned transaction code which is used to execute the program.

VI. Authorization Checks for HR custom programs

Methods to accomplish authorization checks for HR are illustrated below:

1. Use function module "HR_READ_INFOTYPE" instead of direct SELECT
statements when reading a specific infotype.

2. Use logical database PNP to leverage SAP authorizations (caveat:
performance can be slow)

3. SELECT statements should only be used when the SAP documented data
interfaces which incorporate the SAP authorization checks (Logical
DataBases, function modules, and BAPI's) cannot provide the functionality
required. If it is necessary to use SELECT's, then you must perform your
own AUTHORITY-CHECK on the data selected.

4. Place a strict authorization group at the program (transaction)
level. If a wide variety of data for a large group of individuals is
needed in a single program, then this program must have a very strict
authorization on who can run it (definitely not on any menu path).

VII. Parameter, P_BOUNCED_EMAIL, should be passed to Z_SENDMAIL

In order of preference, please provide one of the following for P_BOUNCED_EMAIL :

A mailing list of people from the business process side who can recognize and have the ability to resolve the issue of a bounced mail (e.g. CAO maintains a master email list of cost object approvers).
A mailing list of people from an Admin Computing support or project team who can resolve the bounced mail.
"sap-bounces.unicef@gmail.com". This mail will go to Siva Kumar, Amina Alavi and Victor Lee for resolution.

VIII. Separate Dialog Program Includes

PBO
PAI
Global data
Forms

IX. Standards

Development
Quality Assurance
Change Request

Strongly Recommended Practices

I. Non Database Performance

Dead Code (Program -> Check -> Extended Prog. Check) - unused subroutines appear as warnings under PERFORM/FORM interfaces. - unused variables appear as warnings under Field attributes. Transaction code is SLIN. This will also catch literals (section III below).
When possible use MOVE instead of MOVE-CORRESPONDING (move bseg to *bseg or move t_prps[] to t_prps2[] if you want to copy entire table or t_prps to t_prps2 if you only want to copy header line.)
Code executed more than once should be placed in a form routine.
http://docs.google.com/View?docID=dhs6z73_45f5r2q9fd&revision=_latest when possible especially against non-buffered table (Data Dictionary -> Technical Info)
SORT tables BY fields
Avoid unnecessary moves to table header areas.
Subroutine parameters should be typed for efficiency and to help prevent coding and runtime errors.

II. Database Performance

Avoid ORDER BY unless there is index on the columns - sort internal table instead
SELECT SINGLE when possible
SELECT fields FROM database table INTO TABLE t_tab (an internal table) - Lengthy discussion.
Views (inner join) are a fast way to access information from multiple tables. Be aware that the result set only includes rows that appear in both tables.
Use subqueries when possible.
"Sample Code" (outer join) are very fast but keep in the mind the special features and 3 pitfalls of using it.
(a) Duplicates are removed from the answer set as if you had specified "SELECT DISTINCT"... So unless you intend for duplicates to be deleted include the unique key of the detail line items in your select statement. In the data dictionary (SE11) the fields belonging to the unique key are marked with an "X" in the key column.
(b) If the "one" table (the table that appears in the clause FOR ALL ENTRIES IN) is empty, all rows in the "many" table (the table that appears in the SELECT INTO clause ) are selected. Therefore make sure you check that the "one" table has rows before issuing a select with the "FOR ALL ENTRIES IN..." clause.
(c) If the 'one' table (the table that appears in the clause FOR ALL ENTRIES IN) is very large there is performance degradation Steven Buttiglieri created sample code to illustrate this.
Where clause should be in order of index See example.
This is important when there are multiple indexes for a table and you want to make sure a specific index is used. This will change when we convert from a "rules based" Oracle optimizer to a "cost based" Oracle optimizer. You should be aware of a bug in Oracle, lovingly referred to as the "3rd Column Blues". Click here for more information on indexes.
Where clause should contain key fields in an appropriate db index or buffered tables. As long as we are using the Oracle Cost Based Optimizer, be aware fo the "Third Column Blues", an Oracle bug.
Avoid nested SELECTs (SELECT...ENDSELECT within another SELECT...ENDSELECT). Load data in internal tables instead. See item 3 above.
Use SQL statistical functions when possible (max, sum, ...)
Delete all rows from a table. A where clause is mandatory. Specifying the client is the most efficient way.
Put Check statements into where clause - caveat: Make sure that the index is still being used after you add the additional selection criteria. If the select statement goes from using an index to doing a db scan (reading each row in the database without going through an index) get it out of the where clause and go back to using "Check"!

III. Literals

Codes ('MD') should use contants (c_medical)
Longer text should use text elements. Sample code is a good example because it uses the text element in conjunction with the hard coded text. This documents the text element and provides for the possibility of multi-language support.

IV. Miscellaneous

Use CASE statement instead of IF...ELSEIF when possible (It is only possible in equality tests)
Nested If - encounter most likely to fail first (specific to general)
And - encounter most likely to fail first (specific to general)
OR's - encounter most likely to succeed first (general to specific)
Variables should use Like when possible
Subroutine usage - don't place decision to execute in the subroutine
If not ( t_prps[] is initial ) (instead of describe table t_prps lines sy-tfill, if sy-tfill > 0...)
New document types confirmed with the configuration team via UNICEF-ABAP mail list prior to coding a report to access the data.
Dates need to be properly formatted using the user's default settings. For the explanation of the BDC example check out the developer's standards.

Function Module documentation

ZFUNCDOC

REPORT ZFUNCDOC.
************************************************************************
*  INSTRUCTIONS FOR COPYING DOCUMENTATION TEMPLATE                     *
************************************************************************
*1) SELECT THE ENTIRE TEMPLATE BY PLACING THE CURSOR IN THE FIRST
*   COLUMN double clicking three times on the Select button.
*
*2) SELECT COPY.
*
*3) GO TO THE FUNCTION YOU ARE DOCUMENTING. SELECT DOCUMENTATION AND
*   CHANGE. PRESS BUTTON 'FUNCTION MOD. DOC F9'.The documentation window
*   appears, showing the SAP default documentation
*
*4) DELETE THE DEFAULT TEXT. PASTE THE TEMPLATE INTO THE WINDOW USING
*   PASTE. The template and text formatting tags appear.
*
***************** TIPS FOR ENTERING INFORMATION ************************
*
* IF YOU WANT TO AVOID ACCIDENTALLY DELETING FORMATTING TAGS, START EACH
* LINE of your documentation on a new line.
*
* At the end of each line you type, press return; otherwise, your text
* will spill into the first column, which is used only for paragraph
* formatting.
*
************************************************************************
*                         END OF INSTRUCTIONS                          *
************************************************************************

 Include  documentation

ZDOCUINM

************************************************************************
** INSTRUCTIONS FOR COPYING DOCUMENTATION TEMPLATE **
************************************************************************
* Updated on 05/27/2007. *
************************************************************************
*1- Place cursor beneath the INCLUDE comment.
*2- Click on the Pattern soft button.
*3- Select the "Other pattern" radio button.
*4- Enter ZDOCUINM in the search box beneath this button.
*5- Follow instructions in the pattern copied to your program (below).
************************************************************************
************************************************************************
* Instructions: 1. When inserting this template in your source code,
* please replace only the angle brackets and the text
* between them.
* 2. If it is not applicable simply enter N/A.
* 3. If you need more space, use additional lines starting
* with an asterisk ONLY and kindly indent. Thanks!
* 4. Lastly, remove these instructions from your include
* documentation block. Thanks!
************************************************************************
*^ Written By : <Author>
*^ Date Written : <Date>
*^ Include Name : <Name of the include>
*^ Used in Programs: <Programs referencing this include>
*^ System Name : <System name/application area>
*^ Purpose : <Form routines, PAI/PBO modules, data declarations>
* <Kindly indent subsequent lines>
*^ Other Considerations: <anything else a developer might find helpful>
**--------------------------------------------------------------------**
*^ Maintenance History (latest on top)
*
*^ Date: <MM/DD/YY> Author: <USERID> Transport: <Transport #>
*^ Description of Change:
*
************************************************************************

Access to the change request database from VPN

2007-11-23T07:20:00.000-08:00

Please follow this link:
CRDB access via VPN

Change SAP logo in top right hand corner of SAP client

2007-10-29T07:30:00.000-07:00

I was a little bored to do heavy duty technical stuff, and ended up doing this small thing. But it is interesting and worth the time spent.

The following steps demonstrates how to replace the SAP logo in top right hand corner with a dancing penguin. If you look at the penguin image in paint you will see that it is basically a collection of slightly different still images next to each other. Therefore if you have got the time and patience you can insert any moving picture you want.

1. Open field directory C:\Program Files\SAP\FrontEnd\SAPgui\themes\HighCont
2. Rename file sapalogo to sapalogo_tmp
3. Right click on the following file and select ‘Save Target As’, save to above directory
4. Repeat for directory C:\Program Files\SAP\FrontEnd\SAPgui\themes\enjoy

Importance in Business Intelligence: Types of BI

2007-09-04T06:28:00.001-07:00

The first step in Business Intelligence is the process of transforming data into information. There are many ways of extracting the data and formulation into information, but in reality, the type of information needed is dependent on the type of the people who are expecting it. There could be people who might be working in the operational activities such as customer service representatives, and then there could be people who might be working in the tactical leave such as the lower and middle level management and those who are responsible for the strategy of an organization, such as senior and the executive management. Base on this classification, the BI component can be classified as:

1. Operational BI

2. Tactical BI and

3. Strategic BI

Based on the nature of the needs of their own field of working, the nature of the information also varies. See the following picture, which is referred as the BI pyramid depicts the nature of the information required by each user group. The pyramid is used to explain this as the number of users is less as we move from operational to strategic BI needs. This is the classical way of explain the types of BI and is religiously shown in all BI presentations:

The senior management who needs the strategic gives the information as a global overview of the entire business. In olden days it was referred as the Executive information system (EIS) and now evolved as dashboards as they are indicators of the actual performance of the critical indices.

The middle management who is very much working on the tactical issues, needs more flexible and detailed reports to improve their decision making. The information can be quickly assembled into useable form using ad-hoc queries. They are not the pre defined dash boards, but flexible and modular set of queries, which can slice and dice the data cubes for the discovery.

In the operational level, the requirement is with standardized, detailed, preformatted reports provided by an automatic report engine. Typically these reports are of the type of spreadsheets, and can be taken offline to format and regroup using standard software like Microsoft Excel.

Given the types of the BI that are needed for any organization, now-a-days most of the BI software packages do come with a variety of tools that addresses each section of the BI pyramid, though there are some inconsistencies on the definition of each layer. The only important thing that is missing in this pyramid is the data mining, which is for a special set of people who are specializing in that activity. Data mining is itself a huge subject and we can discuss this later as a separate topic. I recently read one very detailed paper (draft) by one of my colleague on the data mining explaining its relevance and importance to UNICEF.

Let’s now get into the practical side of the BI and the way in which is it used:

It is very hard to see a senior manager that is content with an overview of the business activities - unless he or she is incompetent. Any I’m sure the every competent senior manager will always need detailed data for some or many specific operations - and often on a regular basis. My honest opinion is that the dashboards are great for management meetings, but whoever runs an organization based on this alone, may at times will feel short of information that are required to make effective decisions. This is due to the very nature of the dashboard and the lack of details in it.

I have yet to see the middle managers that indulge in On-Line Analytical Processing (OLAP) and ad hoc querying more than others in the organization. Middle managers especially non-IT organizations are not more computer literate than anyone else. And OLAP and ad hoc querying do demand more computer skills from these managers. The very notion of using tools like this will drive them away from using them or try to move that work under them to operational group. Practically they get the information from the operations team, whose mind set is still in the preformatted reports.

Finally, who on an operational level feels happy about only having standardized and detailed reports? First problem is that they do not always agree with the standard form of reports, secondly the time taken to create & download the reports, thirdly the repetitive nature of the report generation creates boredom and finally they had to convert all the reports to spreadsheets for them to use it. We should not forget the fact that the use of spreadsheets is grown more then the legacy systems, ever after the implementation of all the new dimensions products such as ERP and BI.

Going back to my previous statement about the popular BI pyramid, which looks nice - especially when it comes in fancy colors - but it is rather imperfect and too far from what is practiced. As a result, more and more BI solution providers are beginning to realize that the reality is a bit more multidimensional than the BI pyramid: Strategic users also want detailed data and operational staff wants to have the overall picture. The middle managers want and need both detail and overview, and they are not more likely than anyone else to decide to spend and afternoon doing their own ad hoc queries in their office.

After a decade of BI evolution, some, but not all, have finally realized that BI is as complicated as anything else. The users are as irrational in their needs as they are with anything else. Many of them do like the colorful BI pyramid though and, given its inclusion in BI presentations, it will probably stay on for some years.

If allowed, I’d refine the BI pyramid by adding a group called systems analyst, which will be the central focus of the BI function, who will closely work with the three different user groups. They are the core set of people who knows how to use the BI tools effectively and efficiently and they are not the IT people. There is always the involvement of IT in this whole picture which is ideally the provider of BI infrastructure and not the provider of BI itself.

birthday cake

2007-09-03T06:18:00.001-07:00

After long search, I found this as the character acceptable by my son for his 4th birthdat party cake!

One ERP versus One Ecosystem

2007-07-05T12:19:00.001-07:00

One ERP versus One Ecosystem

The one thing that has been reverberating in the Information Technology circles at UNICEF is about One Enterprise Resource Planning (ERP). This is based on a very strong recommendation that came out from the Business Process reengineering (BPR) by Dalburg and accenture was to have a true ERP environment in UNICEF .This has been a very controversial at the same time political decision that involves a whole a lot of resources in terms of money and people. Please go to the following link to see the entire recommendation.

There are two different aspects to effectively achieve the true ERP system. They are having One ERP system implemented and followed worldwide so the Head Quarters (HQ) and the Country Offices (CO) see the same information in the same way. The other way is to build an Eco system, as I call it, which will comprise of one ERP, combined with one or more systems distributed worldwide with proper interfaces.

Before getting in to the discussion of going right in to the True ERP discussion, we need to look at the evolution of the software during the past fifteen years. When people started using computers for business, it was towards simple applications such as financials, simple automation of the documents using word processors and spreadsheets. Then was the use at the manufacturing such as Material requirement Planning (MRP), Inventory maintenance, accounting involving Accounts payable and Receivables, etc. Even though this was of great help, there was no value addition in the decision making process. Then came the wave of adding more value to the computerization, and integrating the common functions such as Material requirement, Inventory, Purchasing, Financials, Costing, Sales, etc. This evolution is termed as MRP-II and a lot of software development focused on these integrated issue. Even though there was a lot of resistance to these MRP II software packages, they gained steady ground over a period of two to three years, when the managers felt the automation process lead to the formation of Islands of automaton and needed more integration to be able to make effective decisions. This gave birth to the Enterprise Resource Planning (ERP) software. SAP is one among the leader and very popular ERP software with others like PeopleSoft (Oracle) and SAS.

These ERP solutions blended the business and technology so well, that it was very difficult to differentiate them from one another. But in almost all cases, the ERP initiative was driven by the business and would have been supported by the IT section of the organization. However, there were clear overlaps as the technical personal were also equally responsible for the improvement of the business as they know the customizing of the software better than the business user.

This ERP philosophy brought all applications together and tightly integrated. The entire business community was very happy to embrace it for its integrated functions. Added to that because of the Y2K fear, many corporations jumped in to the ERP bandwagon and started their implementation. The ERP as designed brought in the tight integration between different components of the business, at cost of flexibility. As a result, the implementation resulted in huge changes in the way the business was run before. Change management team was a critical element in each implementation and eventually the organizations that were implementing the ERP solutions, started customizing the system to suit their businesses. This was more like cutting their own foot to fit the shoe size. This process of custom development led the ERP software makers to think of their benefit and they themselves started delivering different products for different sectors such as Public sector, Apparel and foot ware, Beverages, Banking, Insurance, etc.

In spite of the different product lines, the organizations did not leave their quest to customize the software to their need, as against critically evaluating their current business process. Reengineering was taken out of the list and Refitting was added. The software systems which were based on the best practice processes were bent to fit to the processes existing in the organization. This has greatly influenced the gains that were projected to happen with the ERP implementations. This in addition to the technological development in the internet era, the software companies, started adding more functionality, options and catchy front ends as bolt-on features shifting from their own integrated architecture.

The convergence of the processes now took the divergence once again. This process led the organizations to use various set of software tools to cater to each specific functions such as Customer Relations Management (CRM), Business Intelligence (BI), Supplier Relationship Management (SRM), etc in addition to the core ERP application.

This will lead to the debate of using one ERP software solution and the respective bolt-on function versus the use of ERP system and to use the working legacy system or third party cheaper software and interfacing them effectively. The second method can be referred as building one Ecosystem in which the processes and the business views in all individual systems are maintained consistently. The Ecosystem approach is very common in private sector based mainly on the implementation cost and to leverage the cost invested in the legacy systems.

The main advantage of the one ERP is that the implementation is fairly simple and the future upgrades could be smoother. The business logic and the process integrity are well established and you can have a seamless support from the software vendor. The major disadvantage could be the cost. Traditionally the solutions provided by the ERP systems are very expensive and also demand a reliable and established infrastructure to operate.

On the other hand, building one eco system will be a very cost effective method, but the ownership to design, develop and maintain the software needs to be addressed in house. Keeping up with the technology will be a big challenge in this case.

Either of the two solutions can be adopted strategically to any organization. In this moment UNICEF is in cross road to make a decision on going one way or another. This strategic decision will be a key to the success of the organization’s mission in the coming years.

RFC Calls for Manipulating Internal Tables

2007-05-22T08:17:00.000-07:00

One of my friend had asked to explain the process of manipulating the internal tables with the RFC calls from SAP. The RFC is enabled by the function interface that is part of the RFC library provided by SAP.

These functions allow processing of ABAP internal tables in C.

ABAP internal tables follow the model of a relational database table.

ABAP internal tables consist of identical rows. When it is created, a table is empty. In ABAP you can fill rows into a table by the statements ‘Insert’ or ‘Append’. You can access a row by ‘Read Table’, and you can delete a row by ‘Delete’. You can free a table by ‘Free Table’, and you can receive information about tables by ‘Describe’.

These language constructs correspond to the following C routines:

ItCreate

creates a new internal table

ITAB_H

handle of an internal table

ItDelete

deletes the content of a complete internal table and frees storage

ItGetLine

reads a line from an internal table

ItInsLine

inserts a line into the given position of an internal table

ItAppLine

appends a line at the end of an internal table

ItDelLine

deletes a line from an internal table

ItGupLine

reads a line for update

ItFree

resets an internal table to initial state

ItFill

returns the number of lines in a table

ItLeng

returns the width of a table, i.e. the size of a row of the table

The syntax and semantics of the above RFC calls are identical for all platforms supported.

The syntax of the RFC calls is described in saprfc.h. The syntax of the RFC calls for manipulating internal tables is described in sapitab.h.

Creating and filling a new internal table with the following example

const int myTableSize = 200;
ITAB_H handle;
void * ptr;

handle = IitCreate("MyTable", myTableSize, 0,0);
if(handle == ITAB_NULL)
{
... error
}

do
{
ptr = ItAppLine(handle);;

if(ptr != NULL)
{
memcpy(ptr,..., myTableSize);
}
while(ptr != NULL);

More help is available in the SAP help site:

http://help.sap.com/saphelp_46c/helpdata/de/22/043074488911d189490000e829fbbd/frameset.htm

2007-01-25T10:41:00.000-08:00

Programming with Substitution

Substitution is a very powerful tool that SAP delivers with most of the application module. Let's first see what is substitution. A substitution is a configuration step, that allows a process (or a step) of replacing values as they are being entered into the SAP R/3 system using a transaction. For example in this case, we take up the substitution use in the Work Breakdown Structure (WBS). When the users are creating or modifying a particular WBS element (using transactions CJ01 or CJ02), we can change certain values behind the scenes based on certain required logic. This values can be either for standard fields or for customer fields (CI Structures). To know more about the CI structures, please see my blog on the CI structures.

And also remember, the entered values are checked against a user-defined Boolean statement (prerequisite). If the statement is true, the system replaces the specified values. Substitution occurs before data is written to the original database.

Even though in most of the cases substitution may be simple, in some cases it could be really tricky. This document is intended to address those cases. In this example, I'm going to demonstrate a custom field to show the entire process of substitution in a WBS structure.

Displaying substitution
For the project system, we open the IMG (transaction SPRO) and navigate to the following path:

Maintain substitutions and on the left frame go to the WBS element node

Go to the menu Extras -> Substitution Fields

This will show the list of the fields that are substitutable. In the standard system, most (or all) of the table related to the WBS (PRPS) will be available. As we discussed earlier even the customer fields in the CI_PRPS structure can also be used. In my case I needed to have a bunch of Z fields and they were added to the CI_PRPS structure and in turn to the PRPS table

By adding it to the CI_PRPS structure, these fields are available for me to enhance the screen for the WBS create/change transaction. To do this you need to create a project using CMOD and include the component CNEX0007. Use the screen exit to create a screen and the Function exit to add logic. Fine, now let's go back to the substitution.
SAP has a very basic common structure for all substitution related processes. The underlying table is GB01. This table contains all the tbles and fields that can be substituted based on the class type ('S' for substitution). Here is the screen shot of table GB01.

Once we decide the substitution field, we need to insert it in to this table. SAP does not provide you any means to do that. So use the following routine to add the entries
Program: ZNFI_UPDATE_TABLE_GB01
Copy the source code, and execute the program and add the fields as required into the table GB01.

After running this report for a set of Z values, the table GB01 looks like this:

Once this is done, then the substitution structures should be regenerated. Without this step that added fields in GB01 will not ba available for substitution. To do this we need to run the SAP program RGUGBR00.

Once you complete the regeneration, let's go to the actual substitution area to create and implement one.
In the example, I've created a substitution under WBS and under the node WBS_ELM

This document assumes that you know the substitution basics and the prerequisite. In this case my prerequisite is to check the project profile before carrying out the substitution. Then an user exit code is added U0500. Double clicking on this will take you to the code. Add the code to move the values to the PRPS structure based on the WBS level.

As usual, any comments welcome.

Multimedia message

2006-12-18T06:39:00.001-08:00

Cutie pie

2006-12-18T06:30:00.001-08:00

HTML control used as a web browser

2006-12-14T11:58:00.000-08:00

This is an interesting piece of development. This uses the HTML control to create a web browser. I've used the HTML related function modules in this example shown below. In order for this example to work, you need to create a WWW document Id and then call it in your main program. In this example, I've created a document id ZSIVA_BLOG.

1. Go to transaction SMW0
2. click on the HTML template for WebRFC applications and execute
3. Create new entries and enter the attributes
4. The entry will be created as below:
5. Then click on the detail function and assign the basic HTML page that needs to be loaded when your HTML control loads:
6. Instead you can use the import/export parameters as well from the menu.

7. Then click on the glasses (to display), you can see the base page in a browser.

To enable the web browser, copy the following code into a new executable program:
*&---------------------------------------------------------------------*
*& Report ZNUT_WEB_BROWSER_NEW *
*&---------------------------------------------------------------------*
* Sample program to demonstrate the HTML Control be used as a WEB BROWSER
* Siva Thiagarajan

REPORT ZNUT_WEB_BROWSER_NEW.

INCLUDE .
INCLUDE CNHTINCL.

DATA: H_HTML_CONTROL TYPE CNTL_HANDLE.
DATA: B_INIT TYPE C.
DATA: PROG_REPID LIKE SY-REPID.
DATA: FCODE LIKE SY-UCOMM.
DATA: URL(1024).

SET SCREEN 100.

*&---------------------------------------------------------------------*
*& Module STATUS_0100 OUTPUT
*&---------------------------------------------------------------------*
MODULE STATUS_0100 OUTPUT.
SET PF-STATUS 'TESTHTM1'.
SET TITLEBAR '001'.

IF B_INIT IS INITIAL.
CALL FUNCTION 'CONTROL_INIT'.
PROG_REPID = SY-REPID.
CALL FUNCTION 'HTMLCNTL_CREATE'
EXPORTING
OWNER_REPID = PROG_REPID
LINK_REPID = PROG_REPID
DYNNR = '0100'
CONTAINER = 'HTML_CONTAINER'
CHANGING
HANDLE = H_HTML_CONTROL.

B_INIT = 'x'.
CALL FUNCTION 'HTMLCNTL_INIT'
EXPORTING
H_CONTROL = H_HTML_CONTROL
REGISTER_EVENT_ON_NAVIGATE = 'x'
CB_FORM_NAVIGATE_COMPLETE = 'ON_CONTROL_EVENT'.

PERFORM LOAD_HOME_PAGE.

CALL FUNCTION 'CONTROL_FLUSH'.
ENDIF.
ENDMODULE. " STATUS_0100 OUTPUT

*&---------------------------------------------------------------------*
*& Module USER_COMMAND_0100 INPUT
*&---------------------------------------------------------------------*
MODULE USER_COMMAND_0100 INPUT.
CASE FCODE.
WHEN 'BACK'.
IF NOT B_INIT IS INITIAL.
CALL FUNCTION 'HTMLCNTL_DESTROY'
CHANGING
H_CONTROL = H_HTML_CONTROL
EXCEPTIONS
OTHERS = 1.
CALL FUNCTION 'CONTROL_FLUSH'.
ENDIF.
LEAVE PROGRAM.

WHEN 'HHOM'. " show the home page
CALL FUNCTION 'HTMLCNTL_GO_HOME'
EXPORTING
H_CONTROL = H_HTML_CONTROL.
CALL FUNCTION 'HTMLCNTL_GET_CURRENT_URL'
EXPORTING
H_CONTROL = H_HTML_CONTROL
IMPORTING
URL = URL.

WHEN 'HBAK'.
CALL FUNCTION 'HTMLCNTL_GO_BACK'
EXPORTING
H_CONTROL = H_HTML_CONTROL.
CALL FUNCTION 'HTMLCNTL_GET_CURRENT_URL'
EXPORTING
H_CONTROL = H_HTML_CONTROL
IMPORTING
URL = URL.

WHEN 'HFWD'.
CALL FUNCTION 'HTMLCNTL_GO_FORWARD'
EXPORTING
H_CONTROL = H_HTML_CONTROL.
CALL FUNCTION 'HTMLCNTL_GET_CURRENT_URL'
EXPORTING
H_CONTROL = H_HTML_CONTROL
IMPORTING
URL = URL.

WHEN 'HRFR'.
CALL FUNCTION 'HTMLCNTL_DO_REFRESH'
EXPORTING
H_CONTROL = H_HTML_CONTROL.
CALL FUNCTION 'HTMLCNTL_GET_CURRENT_URL'
EXPORTING
H_CONTROL = H_HTML_CONTROL
IMPORTING
URL = URL.

WHEN 'HNAV'.
CALL FUNCTION 'HTMLCNTL_SHOW_URL'
EXPORTING
H_CONTROL = H_HTML_CONTROL
URL = URL.

WHEN OTHERS.
CALL FUNCTION 'CONTROL_DISPATCH'
EXPORTING
FCODE = FCODE.
ENDCASE.
CLEAR FCODE.
ENDMODULE. " USER_COMMAND_0100 INPUT

* Callback form for the event 'NavigateComplete'
callback on_control_event.
CALL FUNCTION 'CONTROL_GET_EVENT_PARAM'
EXPORTING
H_CONTROL = H_HTML_CONTROL
PARAM_ID = 0
CHANGING
RETURN = URL.

endcallback.

* Homepage form
FORM LOAD_HOME_PAGE.
DATA: DOC_URL(80).

CALL FUNCTION 'HTMLCNTL_LOAD_HTML_DOCUMENT'
EXPORTING
H_CONTROL = H_HTML_CONTROL
DOCUMENT_ID = 'ZSIVA_BLOG'
IMPORTING
ASSIGNED_URL = DOC_URL
EXCEPTIONS
OTHERS = 1.

IF SY-SUBRC EQ 0.
CALL FUNCTION 'HTMLCNTL_SHOW_DATA'
EXPORTING
H_CONTROL = H_HTML_CONTROL
URL = DOC_URL.
ENDIF.
ENDFORM. " LOAD_HOME_PAGE

Fine print:

1. Please create a pf-status TESTHTM1

2. Create a screen 100 like this:
3. The PBO and PAI modules are already handled in the main program.

BDT Development - II

2006-12-14T10:41:00.000-08:00

The following is the step by step instruction on how to use the BDT to create enhancments to the Grants master screen. Using BDT development to creating a new Tab on the grants management master data transaction (GMGRANT). Please make a note that unlike the common logistics transactions which will have the four part transaction set such as create, Chage, Display and Delete, the grants transaction is one maintanence transaction which includes all the above mentioned functions. All the customizing we do using BDT has to keep this concept in mind during the development

- Execute grants management BDT development transaction (GRANT_CUSTOMIZE)
- Grant Master BDT Customizing-> Screen layout and select ‘Field groups’(GMS2)
- Click on ‘New Entries’. Try to maintain the field grouping number more than 500, to make sure it is in the customer name space and will not accidentaly interfear with SAP's standard values.
- Go back to main field group screen, select your new entry and double click on the
‘Field Group-> Fields’ folder option from the left column. Now enter your fields, for this example I have created some new entries which will be added as part of a new tab.
In order to create the custom fields, we nned to go to the table GMGR, and double click on the extension structure CI_GMGR. This is the structure that will hold all custom created fields and will automatically get appended to the BAPI extension structure. When you want to use the BAPI for accessing the Grants master data, we can use the extension_in and extension_out methods.

- Return to main BDT customizing screen and select ‘Views’(GMS3). Then click the ’New Entries’ button. In this example I've created a view called ZMG007 (Internal information ). The View is the important part of this development as majority of the development happens here in this place. The view is a logical collection of field group and is a screen by itself. You will have a screen developed which will have a PBO and PAI routines. In addition to that we will have three place holders in which we can have our own routined to perform the requiredtasks. They are:
(a) Before screen call-up
(b) Before Output
(c) After Entry
For this example I've used three custom function modules that will be used in the above mentioned place gholders. Then double click on the field group (from the left frame), and enter the field group we created in the earlier step
One more interesting note is that the option of having 'Further check'. Click on the further check from the left frame and here you can have one more routine, to do any sort of validations that can be performed after the view. This is in addition to the PAI routine for the screen and the function module at 'After Entry'. This further check is very useful in the case if you are required to some validations in the SAP provided views. I'll give an example we had done to add some validations to the grants currency for certain types of grants.
- Return to main BDT customizing screen and select ‘Sections’(GMS4).
Then click the ’New Entries’ button and enter the views that are required in the section. A section is a collection of one or more views. And go back to main Sections screen, select your new entry and double click on the Section-> Views folder option from the left column. Now enter the new view you created previously.
The last step in this process is to create the screen. A screen is a collection of one or more sections.
Select 'New Entries' and enter the attributes for the screen. We have a lot of options in this place, but will discuss it later in detail.
Click on the Sections from the left side frame and start additng the sections that are required for this screen.
Once the screens are developed, it is time to work on the sequence in which they will be displayed. The next transaction qill tell you how to order the screens both SAP delivered and the custom developed screens.

Return to main BDT customizing screen and select ‘Screen Sequence’(GMS6). Then select the screen sequence entry and double click on the Screen Sequence -> Screens folder option from the left column.
Then create a screen sequence (or) modify he existing one.
The final step is to generate the screen sequence to reflect the final changes.

Execute transaction BUSP (click on option from main grant customizing menu), new screen will now appear as tab on grant master transaction ‘GMGRANT’

That's All!!!! As usual if in doubt, please post your comments.

Generic Object Services

2006-11-06T06:57:00.000-08:00

Generic Object Services – Linking IDoc to the Business object.

Overview:

The business object and its related services can be linked using Generic object services. This is a very clean way of seeing thing right from the application which can be either master data or transactions. This document explains the ways to link the objects that are created in the customer name space. Most of the SAP’s standard services are pre built to perform this action.

When you publish the custom Business object using the function module ‘SWU_OBJECT_PUBLISH’ , a object service toolbox appears for the related business object in its business transaction.

The following services can be started in the toolbox,

Toolbox Entry	Submenu	Link to Description
Create...	Create Attachment	Appending a PC Document to an Object
	Create Note	Creating a Note for an Object
	Create External Document (URL)	Appending a Link to a Web Page
	Store Business Document	Appending and Archiving a PC Document to an Object
	Enter Bar Code	Assigning an Object the Bar Code of a Document
Attachment List		Displaying Attachments
Personal Note		Creating a Personal Note for an Object
Send Object with Note	Send Object with Note	Sending an Object with a Note
Send Object with Note	Object Outbox	Displaying the Object Outbox
Display Relationships		Displaying Relationships
Workflow	Workflow Overview	Displaying Workflows for an Object
	Archived Workflows	Displaying Workflows for an Object
	Start Workflow	Starting a Workflow for an Object
My Objects	Add to My Objects	Adding Object to your Favorites
My Objects	Subscribe/Cancel Object	Subscribing to Messages About Changes to an Object
Telephony		Telephony
Actions		Activating PPF Actions

In this example document, We will try to demonstrate the incoming and outgoing Idocs can be linked to the Business object and they can be viewed using the relationship service in the toolbox from within the application. The scenario here will be like theis:

The Idocs are created in a separate ALE distribution program and not in the same business transaction. The objective is to link the Idocs created in the separate program to its corresponding business object and should be made available in the relationship service.

The following steps are involved for linking the Idoc to its corresponding Business object.

For illustration let us link the outbound and inbound Idocs to the customized business object ‘Bank account’ (ZUNBANK).

Before linking the Idoc with the business object, the relationship service in the tool box appears disabled as below, meaning that the system cannot show or display the related service objects.

For Outbound Idoc:

Step 1: BDA4: Link the Idoc message type to the Business object type. In this example the message type, the idoc and the business objects are all in the customer name space.

The Idoc message type is linked to the object type.

Step 2:BD95: Define the ALE object type. This is just an object definition and link this to the master table and the key field.

Step 3: BD57: Define the link object type for the message type.

Step 4: BD59: Assignment of object type to message

Step 5: Execute the corresponding ALE distribution program and create the Idoc.

Now the relationship service in the toolbox is enabled.

The corresponding Idoc is displayed

For Inbound Idoc:

The inbound idoc linking is a little bit trickier than the outbound. In the case of the outbound, the file creation is in our hands and we can establish the linkage as we create and distribute the file, whereas in the inbound the same needs to be accomplished in the inbound function module. Though it is only a single step action, I’ll try to put in my next posting.

Thanks to my colleague Praveen Antony for his contributions for this document preparation.

BDT development

2006-11-02T06:03:00.000-08:00

Business Data Toolkit (BDT) is the new way of programming in SAP. This is available in IS-PS (public sector) solution and I guess this is available in some other IS solutions such as insurance etc., This is a concept in which SAP provides you all the development components with which you can build your own screens and fields and weave it nicely within the existing SAP application. This is available mostly for the master data maintenance.

Given this input, I'll try to explain the concept in which I understood. Every SAP transaction can be thought in abstract to have the following components:
1. Data element & Domains
2. Screen fields
3. Field grouping (functional set of fields)
4. Views (Combination of one or more field group)
5. Sections (Combination of one or more views)
6. Screen (Combination of one or more sections)
7. Transaction (With one or more screen in a pre determined sequence)

If this above concept is clear, then it is very easy to understand and can even start development using BDT. For those who do not have enough exposure to the Grants or other modules that have BDT, I’ll try to give an analogy using the customer master record.

In the customer master the fields that are in the KNA1 table are the data elements and domains. The screen fields are the same as the data element, but the screen needs to be built and the definition of the screen specific parameters was defined in SAP’s delivered screen itself. For example the customer name is the data element AD_NAME1 and the related screen field is ADDR1_DATA-NAME1 (Program SAPMF02D/Screen 7000)

The field grouping is the group of functionally related screen fields, which can be turned as Required, Optional or Hidden using the configuration. In this case it could be the set of fields that cover the Street address

The views can be Street address and the PO Box address together

And the Section may be the combination of Name, Search term, Street address and the PO Box address.

The screen could be the Address, Control Data, etc.,

The screen sequence is defined and the transaction XK01/02/03 is created.

With the same idea in mind SAP had given the same concept as a development tool. This eliminates the need of extending the SAP’s standard table by appending structure. And also it gives you the flexibility to append two dimensional objects such as tables as well.

interesting problem

2006-11-01T12:21:00.000-08:00

Eventhough you work for a long time in programming, say in ABAP, it is very difficult to keep in touch with all the evolving technoloagy and the concepts. and practical requirements are pretty simple and that do not need much of the complex programming techniques.

Most of the trivial programming requiremets are such as GUI operations, MS office interface, etc., can be easily built using the standard functions and can be kept as a tool kit. This will obviously be a effective methadology, as you don't have to dig over and over for the most common jobs.

Let me start posting the ABAP routines, I've developed, which can be used in any implementation.

The first posting will be a reading Excel file from the presentation server. This upload will take care of the excel files which contain macros as well.

Try and let's know if you are having fun

*&---------------------------------------------------------------------*
*& Report ZZ_TEST_EXCEL_LOAD *
*& *
*&---------------------------------------------------------------------*
*& *
*& *
*&---------------------------------------------------------------------*

REPORT ZZ_TEST_EXCEL_LOAD .

TYPE-POOLS: truxs.

PARAMETERS: p_file TYPE rlgrap-filename.

TYPES: BEGIN OF t_datatab,
col1(30) TYPE c,
col2(30) TYPE c,
col3(30) TYPE c,
END OF t_datatab.
DATA: it_datatab type standard table of t_datatab,
wa_datatab type t_datatab.

DATA: it_raw TYPE truxs_t_text_data.

* At selection screen
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
CALL FUNCTION 'F4_FILENAME'
EXPORTING
field_name = 'P_FILE'
IMPORTING
file_name = p_file.

***********************************************************************
*START-OF-SELECTION.
START-OF-SELECTION.

CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
EXPORTING
* I_FIELD_SEPERATOR =
i_line_header = 'X'
i_tab_raw_data = it_raw " WORK TABLE
i_filename = p_file
TABLES
i_tab_converted_data = it_datatab[] "ACTUAL DATA
EXCEPTIONS
conversion_failed = 1
OTHERS = 2.

IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.

***********************************************************************
* END-OF-SELECTION.
END-OF-SELECTION.
LOOP AT it_datatab INTO wa_datatab.
WRITE:/ wa_datatab-col1,
wa_datatab-col2,
wa_datatab-col3.
ENDLOOP.

Let's go to the business

2006-10-05T20:02:00.000-07:00

SAP Public sector is not so different from others in majority of the aspects. The functional structure of the module makes it differ with the mainstream SAP solutions.

In IS-PS the existance of Funds Management (FM), rants Management (GM) and Budget control system (BCS) are the three major new areas that available in addition to the common logistics, FI, CO modules. Even HR can be very similar only if your organization is so unique as United Nations and whichhas its own est of rules and procedures. And SAP is also in the process of delivering UN specific HR module soon.

In the next coming days we can discuss more in detail on Funds andGrants module and also follow up on the Budget Control System. I'll try to give as much as functional background and technical information to make the reading easier.

My current assignment

2006-10-04T06:33:00.000-07:00

I'm currently working with a large public sector in New York. Here we have SAP R/3 implemented for the last eight years. We are the ramp-up customers for the SAP IS-PS solution. we started implementing Grants and Budget control system as a part of the public sector solution.

We have a team of three functional members and a team of five ABAP programmers supporting this project. I'm very happy to work with this team as the members are so knowledgeable and bring in to the team a lot of value addition.

In the programming most of the concepts are new and we learned a lot along the implementation. I'll soon request my team members to share their valuable ideas.

About Me

2006-10-03T06:26:00.000-07:00

I started my SAP career back in 1995 in India. And I assume, I'd have been the one of the first set of people who had an opportunity to learn and work on SAP. After my initial training in SAP for about one year, I came to US eying for a project and in all practical sense a real life experience.

My first project was with a fortune 500 apparel and leather goods manufacturer in New Jersey. I've been told to develop some sapscript, which was considered to be very difficult by the analysts from ICS consulting (later they were bought by Deloitte consulting). I completed it in a jiff and got a good reputation right away. I was given master data load (material master and customer master) then was slowly involved in EDI and other related technologies.

My next project was at Phillips automotive electronics at Auburn, Indiana. This is a very small town close to Fort Wayne. This was an ASAP implantation. I was involved in the master data upload and the EDI implementation. The transactions I did was the Inbound/Outbound Orders and the outbound ASN. this was a terrific experience as the customer implemented the SAP formats as such without altering a lot. This project was only 3 months and I learned a lot in this three months.

My next stop was at Nash Finch Company at Edina, Minnesota. I was working for Ernest&Young Consulting. I was in the EDI group and focussed solely on the EDI transactions including ASN, PO, delivery and also in the preparation of the implementation guide for the EDI transactions. This was a eight month project ans the great thing about it is that I had an opportunity to lean ice scatting. My winter experience with Minnesota was not that bad, as 1997 winter was really mild, and we were playing Tennis during the month of September.

Next assignment was at Maxtor Corporation at Longmont, Denver. I was working for Pricewater house (not PWC at that time!). I was taken as the team lead for the EDI team till the time, they get a PWC staff to lead the team. The project was done at two places like Longmont in Denver as well as in San Jose in California. I did almost all EDI transactions such as Orders, ASN, delivery and was worked on the workflow on the purchasing documents. I completed this project by middle of 1998, and wanted to go back to India so badly (Home sick!). the skills I leaned were a little golfing, Hiking on the beautiful Rockie Mountains. By June 1998, I booked my tickets to India and flew back.

I got in to my next project with Wicto Corporation as I got the interview done in India and flew in and joined the project after my one month vacation in India. I was in charge of all EDI development including the workflow development and administration. I also did a lot of shell programming and did a lot of innovative things in this project. I also developed a self standing product in SAP for the purposes od divestiture. I built it based on ABAP and ALE technology. This company was later bought by another and got it name changed to CK Witco. Then got renamed as Crompton Corporation. I worked here for almost six years. the company has changed its name after another merger into Chemtura.

My next stop was to get in to a permanent position.