Distribution and commision management in insurance industry

dear all
Could anybody help to provide some solution model with distribution and commission management in insurance industry?
Thanks a lot

Zhuoija,
Are you looking at industry standard process models or solution architectures for the same ?
Arun
P.S There are a few of them in the IBM website.... with regard to Process models
http://www-03.ibm.com/industries/financialservices/doc/content/bin/fss_iaa_poster_jun2006.pdf

Similar Messages

Incentive and commision management

Hi,
We are working for client Pearl Dubai, here we are working on a solution for Incentive and Commission Management(ICM)
We are looking for configuration document or any other relevant document for the ICM CRM.
Any help in this regard would be highly appreciated.
Thanks,
Suman

hi Suman,
The following link will help in configuring CRM to ICM interface -
[http://help.sap.com/saphelp_crm70/helpdata/EN/c6/161c6534e946a4a14bb547f972b7f1/frameset.htm]
Thanks and Regards
Ravi G

How to export "Managed by" field of Distribution and Security groups and import with new values? (Exchange 2010, AD 2003)

My Active Directory environment is 2003 functional level and we have Exchange 2010.
I am trying to find out the best way to do a mass edit for the "Managed by" values of our security and distribution groups.
I know we can export the "managed by" field by csvde but I am not sure this is the correct way to do it. Also in the case that there are multiple users assigned to be managing a distribution group it only shows one value. Also powershell from Exchange
2010 can be used with "get-distribution" but as our AD environment is 2003 is this correct also?
Finally once the data is exported to csv can it be edited to then reimport and udpate the existing group managed by fields with new values?
Not really sure that the best way to go about this is.
Summary - We have 2003 AD with Exchange 2010 and I am trying to export a list of all our Distribution/Security groups showing the group name and managedby values so we can edit and update the
existing managedby values with new ones. In some cases we have multiple users as the owners.
Appreciate any advice on how this can be best achieved. Thank you.

Hi,
We can use the following command in Exchange 2010 to export "Managed by" field of Distribution and Security groups:
Get-DistributionGroup | Select-object Name,@{label="ManagedBy";expression={[string]::join(“;”,$_.managedby)}},Primarysmtpaddress | Export-Csv
C:\export.csv
After you changed the Managed by field in export.csv and saved it as a new file named import.csv, we can run the following command to set with new value:
Import-Csv C:\import.csv | Foreach-Object{ Set-DistributionGroup –Identity $_.Name –ManagedBy $_.ManagedBy}
Hope it works.
Thanks,
Winnie Liang
TechNet Community Support

Q&A db for warehouse management and inventory management

Hello Everybody,
i read on the help.sap website that standard as well as industry specific versions of Q&A db are available. but the website doesnt say where. i searched a lot but the links dont lead to the actual Q&A db.
i would like to request you to kindly share the Q&A db for inventory management and warehouse management with me as i need it for preparing the AS IS documentation.(preferably automotive industry but if not then even standard Q&A db is fine).
thanks a lot.
sapman.

Now QADB will not help to map the clinets requirement. Instead of QADB get AS IS information form Coreusers... thats best practice now....
Go through www.sap-img.com for further details...
Edited by: Ganti on Jul 26, 2008 7:26 AM

Training and Event Management under ESS

Hi!!
I've been looking at the sap´s help and the only way I can find for implementing Training and Event Management as an ESS application is using ITS. But as I uderstand, the use of ITS is in the past. I want to implement that in ECC 6.0, what should I do?
This is th elink where all they say is using ITS
http://help.sap.com/saphelp_erp60/helpdata/en/77/bff8ab4a2911d182b80000e829fbfe/frameset.htm
Thanks a lot

this is for the erp
 
SAP_ABA - 700 
SAP_BASIS - 700 
ST-PI - 2005_1_700 
PI_BASIS - 2005_1_700 
SAP_BW - 700 
SAP_AP - 700 
LCAPPS - 2005_700 
SAP_APPL - 600 
SAP_HR - 600 
EA-IPPE - 400 
EA-APPL - 600 
EA-DFPS - 600 
EA-FINSERV - 600 
EA-GLTRADE - 600 
EA-HR - 600 
EA-PS - 600 
EA-RETAIL - 600
FINBASIS - 600 
FI-CAX - 600 
INSURANCE - 600 
IS-CWM - 600 
IS-H - 600 
IS-M - 600 
IS-OIL - 600 
IS-PS-CA - 600 
IS-UT - 600 
FI-CA - 600 
ERECRUIT - 600 
ECC-DIMP - 600 
CPRXRPM - 400 
WFMCORE - 200 
SLL-LEG - 7.00 
SEM-BW - 600 
LSOFE - 600 
AIN - 400 
 
and the portal part is
 
Software Components
Vendor Name Version Provider Location Applied
 sap.com ADSSAP 7.00 SP19 (1000.7.00.19.0.20090425161554) SAP AG SAP AG 20090817182515
 sap.com BASETABLES 7.00 SP19 (1000.7.00.19.0.20090425162149) SAP AG SAP AG 20090817174302
 sap.com BI_MMR 7.00 SP19 (1000.7.00.19.0.20090425162208) SAP AG SAP AG 20090817182624
 sap.com BI_UDI 7.00 SP19 (1000.7.00.19.0.20090425162218) SAP AG SAP AG 20090817182701
 sap.com BP_DMSCONN 6.75 SP1 (1000.6.75.1.9.20081125093814) SAP AG SAP AG 20090706161758
 sap.com BP_ERP5ESS 1.0 SP1 (1000.1.0.1.0.20051008075035) SAP AG MAIN_ERP05PAT_C 20090810173157
 sap.com CAF 7.00 SP19 (1000.7.00.19.0.20090427142735) SAP AG MAIN_APL70P19_C 20090817184849
 sap.com CAF-KM 7.00 SP19 (1000.7.00.19.0.20090427135649) SAP AG MAIN_APL70P19_C 20090817194420
 sap.com CAF-UM 7.00 SP19 (1000.7.00.19.0.20090427142740) SAP AG MAIN_APL70P19_C 20090817182712
 sap.com CORE-TOOLS 7.00 SP19 (1000.7.00.19.0.20090425162400) SAP AG SAP AG 20090817174353
 sap.com DI_CBS 7.00 SP19 (1000.7.00.19.0.20090427141356) SAP AG MAIN_APL70P19_C 20090817192659
 sap.com DI_CMS 7.00 SP19 (1000.7.00.19.0.20090427141416) SAP AG MAIN_APL70P19_C 20090817192939
 sap.com DI_DTR 7.00 SP19 (1000.7.00.19.0.20090427141423) SAP AG MAIN_APL70P19_C 20090817192954
 sap.com EP-PSERV 7.00 SP19 (1000.7.00.19.1.20090619074403) SAP AG SAP AG 20090817193057
 sap.com EP-WDC 7.00 SP19 (1000.7.00.19.1.20090619074425) SAP AG SAP AG 20090817193208
 sap.com EPBC 7.00 SP19 (1000.7.00.19.1.20090619074204) SAP AG SAP AG 20090817182927
 sap.com EPBC2 7.00 SP19 (1000.7.00.19.1.20090619074221) SAP AG SAP AG 20090817193212
 sap.com JLOGVIEW 7.00 SP19 (1000.7.00.19.0.20090425155500) SAP AG SAP AG 20090817174420
 sap.com JSPM 7.00 SP19 (1000.7.00.19.0.20090425155600) SAP AG SAP AG 20090817151518
 sap.com KM-KW_JIKS 7.00 SP19 (1000.7.00.19.0.20090522114445) SAP AG SAP AG 20090817182939
 sap.com KMC-BC 7.00 SP19 (1000.7.00.19.1.20090619074454) SAP AG SAP AG 20090817193310
 sap.com KMC-CM 7.00 SP19 (1000.7.00.19.1.20090619074602) SAP AG SAP AG 20090817193348
 sap.com KMC-COLL 7.00 SP19 (1000.7.00.19.1.20090619074633) SAP AG SAP AG 20090817193434
 sap.com LM-PORTAL 7.00 SP19 (1000.7.00.19.0.20090427140244) SAP AG MAIN_APL70P19_C 20090817193436
 sap.com LM-TOOLS 7.00 SP19 (1000.7.00.19.0.20090427143229) SAP AG MAIN_APL70P19_C 20090817185623
 sap.com NET-PDK 7.00 SP19 (1000.7.00.19.1.20090618100600) SAP AG SAP AG 20090817191644
 sap.com RTC 7.00 SP19 (1000.7.00.19.1.20090618135900) SAP AG SAP AG 20090817191648
 sap.com RTC-STREAM 7.00 SP19 (1000.7.00.19.1.20090618135900) SAP AG SAP AG 20090817193442
 sap.com SAP-EU 7.00 SP19 (1000.7.00.19.0.20090427140415) SAP AG MAIN_APL70P19_C 20090817194226
 sap.com SAP-JEE 7.00 SP19 (1000.7.00.19.0.20090425162953) SAP AG SAP AG 20090817174456
 sap.com SAP-JEECOR 7.00 SP19 (1000.7.00.19.0.20090425163113) SAP AG SAP AG 20090817174642
 sap.com SAP_JTECHF 7.00 SP19 (1000.7.00.19.0.20090522115053) SAP AG SAP AG 20090817174829
 sap.com SAP_JTECHS 7.00 SP19 (1000.7.00.19.0.20090522115208) SAP AG SAP AG 20090817184107
 sap.com UMEADMIN 7.00 SP19 (1000.7.00.19.0.20090427143818) SAP AG MAIN_APL70P19_C 20090817185703
 sap.com UWLJWF 7.00 SP19 (1000.7.00.19.1.20090619074757) SAP AG SAP AG 20090817193546
 sap.com VCBASE 7.00 SP19 (1000.7.00.19.1.20090619074802) SAP AG SAP AG 20090817194605
 sap.com VCFLEX 7.00 SP19 (1000.7.00.19.1.20090619074835) SAP AG SAP AG 20090817194422
 sap.com VCFRAMEWORK 7.00 SP19 (1000.7.00.19.1.20090619074842) SAP AG SAP AG 20090817194428
 sap.com VCKITGP 7.00 SP19 (1000.7.00.19.1.20090619074842) SAP AG SAP AG 20090817194610
 sap.com VCKITXX 7.00 SP19 (1000.7.00.19.1.20090619074842) SAP AG SAP AG 20090817194616
 sap.com WDEXTENSIONS 7.00 SP19 (1000.7.00.19.0.20090427140606) SAP AG MAIN_APL70P19_C 20090817194724

Can anyone explain difference b/w Schedule Manager and Solution Manager

Hi,
Is there any difference b/w schedule manager and solution manager or both are same. Plz do reply at the earliest.
thanks,
suresh

Dear Suresh,
Schedule Manager (SCMA):
Schedule Manager automates your routinue task. It facilitate the definition, scheduling, execution, and review of tasks that are executed on a regular basis, such as period-end closing.
Solution Manager - The SAP Solution Manager supports you throughout the entire lifecycle of your solutions, from the Business Blueprint thru configuration to production operation. It provides central access to tools methods and preconfigured content, that you can use during the evaluation, implementation, and productive operation of your systems.
Implementation of the mySAP Business Suite
·        All phases of the implementation project (Business Blueprint, Configuration) are performed centrally in the Solution-Manager system.
·        Central project documentation repository in the Solution Manager
·        Integrated Project Administration allows you to manage planning schedules, human resources and other project data.
Customizing Synchronization
·        The Customizing Scout, with which you can compare customizing in various SAP components, e.g. an ERP system with SAP MDM
·        The Customizing Distribution, with which you can synchronize customizing in various SAP components.
Test
·        You can use the Test Workbench to organize and perform tests at the end of a project phase.
·        Reuse of the project structure for process-oriented tests
Global rollout
Integrated authoring environment, with which customers and partners can create their own templates, which they can reuse in subsidiaries, e.g. in a global rollout
E-Learning management
Creation of training material and learning maps (computer-supported self-tuition courses) to train end users after the implementation of new functions
Solution Monitoring
·        Central system administration
·        Analyze your system landscape with Service Level Reporting
·        System monitoring in real time
·        Business Process Monitoring
Services
Access to programs and Services, which help you to monitor and optimize the performance and availability of your system landscapes, and minimize your operational system risks
Service Desk
Solution support with workflow to create and handle problem messages
Change Management
Management of change requests, with workflow for the monitoring and audit of changes and transports in your system landscape, with the Change Request Management.
Regards,
Naveen.

Grant access to help desk users to add members to distribution and security groups

Hello,
I am trying to create a set of help desk users that has full access to add or remove members from distribution and security groups as well as update users. We want it to bypass owner approval and essentially allow this group to add or remove members
in the FIM Portal and flow it down to ADS.
This obviously works fine if one is a member of the Administrators set, but we want a second tier of power users with limitied rights compared to FIM Admins. We have added the help desk team to the Security Group Users and Group Users set as
well as MPR "Security group management: Users can read selected attributes of group resources".
The help desk users can update users in the Portal with no issue. The can search groups with no issue but when they try to add members to a group they get the error "Access Denied".
Any help is greatly appreciated.
Thanks!

I'm having very similar problem - I have users with delegated right to modify group membership only. User can add someone to group and it works fine, but when the same user is trying to remove and user from a group (even if this is the same user
which was added a minute ago) he gets Access Denied:
The
request included members which the requestor is not authorized
to add and/or remove from this group."
It is caused by default MPR:
Group management workflow: Validate requestor on remove member
Question is how this activity validates this request - any insight?

Governance and Data Management

Hello,
We need to know about governance and data management, from this week I am working as master data coordinator in Empresas Polar (Mass Consumer Products Industry), where the role of this function is to assure the creation and maintenance of the master data, as initial activities we are raising statistics to know the most important information of the master data in all SAP modules, and the idea is across own developments in R/3, Portal, Workflow and Tools that exist on the market to simplify Update of the information on the part of the user, we know that in SAP the information is created in different views or transactions, which makes very difficult the opportune update of the data.
I am interested to know about MDM or any tool/application which eolud help us,
I appreciate your help,
Thanks

Hi torres,
The MDM system for master data management and single-source cross-media catalog publishing does more than just database management, asset management, or even database publishing.It uses an industry-standard SQL-based DBMS as a u201Ccontaineru201D for the repository database. But then it goes much further to implement an elegant and seamless combination of many different technologies,concepts, and minute details to create a comprehensive solution to an
age-old problem.Many of the features incorporated into the MDM system are unique.
ADVANTAGES
End-to-end solution. The MDM system provide an end-to-end
solution that automates the entire process of managing master data from start to finish, including bulk data import, centralized master data management, and published output to a variety of media.
u2022 Database-driven system. MDM layers a thick shell of functionality on top of a powerful SQL-based DBMS so that the MDM system is fully scalable and the master data is fully accessible to other SQLbased applications and tools.
u2022 Large capacity. The MDM system efficiently manages master data repositories containing up to millions of records.
u2022 Superior performance. MDM breaks through SQL performance
bottlenecks to deliver blazingly fast performance that is measured in milliseconds rather than seconds and is literally 100u20131000 times that of a SQL DBMS alone. No other system on the market today delivers comparable performance.
u2022 Powerful search and retrieval. All of the MDM modules include
powerful search and retrieval capabilities, so that an entire repository of thousands or millions of items can be easily searched and any item or group of items located in a matter of seconds.
u2022 Cross-media publishing. The MDM system is the only one on the market today that includes tightly integrated functionality for both electronic and printed output, for Web, CD-ROM, and paper output from a single MDM repository.

Table entries for Personnel administration and organisation management

Hi ,
For a functional consultant do we need to remember the table entries where the employee infotypes saved or where the table entries is useful as far as Personnel administration and organisation management is concerned.....
and one more thing how to create a custom Infotype (employee) detail documentation required ...
keep me posted
Thanks

hi,
it is really helpful if you rember the table name which holds the information about the infotypes
table starting with PA contains all the personnel information data
like PA0001 holds the information of infoty0001
similary you can check for other info types
and hr haster table like HRP1000 or HRP1001 hold all the other hr objects including your personnel objects as well as organizational related objects
infotype numbers
Four digit number nnnn
Unique identification
9000 to 9999 reserved for customer infotypes
naming convention
0000 to 0999 HR Master data / Applicant data
1000 to 1999 Organizational Management
2000 to 2999 Time data
4000 to 4999 Applicant data
9000 to 9999 Customer defined
defination of infotypes
Each infotype nnnn requires at least two structures and one table:
Structure PSnnnn
 Structure PSnnnn contains all of the infotype data fields.
Structure Pnnnn
 Structure Pnnnn contains infotype key fields and all of the data fields
from structure PSnnnn .
Transparent table PAnnnn and/or transparent table PBnnnn
infotype module pool
A module pool should be used with each infotype. This module pool is the main program for the maintenance interface for the info type.
The name of the program is MPnnnn00. Where P stands for Human Resources (personnel) and nnnn is the four-digit info type number.
Transparent table PAnnnn is required if you want to use an infotype within Personnel Administration.
 If you want to use an infotype within Recruitment, transparent table PBnnnn is required.
In accordance with the distribution of infotype name ranges, objects P9nnn , PS9nnn , PA9nnn and PB9nnn are assigned to the customer name range.
infotype screen
An initial screen
A single screen
A list screen
Initial screen is used as technical interface
Screen 1000 is used for all info types
Processed in background and not displayed
Performs general initialization procedures
A single screen
Its an interface between the system and the user.
It enables to create, display or maintain data records.
Screen 2000 is used for single screen.
list screen
Unable to list all records in info type
Screen 3000 is used for list screen
infotype time constrains
A time constraint indicates whether more than one infotype record may be available at one time. The following time constraint indicators are permissible:
A Only one record may exist, valid from 01/01/1800 to 12/31/9999. Splitting and deletion is not permissible.
B Only one record may exist, valid from 01/01/1800 to 12/31/9999. Splitting is not permissible, but may be deleted.
T The time constraint varies depending on the subtype.
Z Refers to time management infotypes.

to create infotype
Transaction code
PM01.
enhancing PA infotype
Start the Personnel Administration info type copier (PM01)
Enter the info type number.
Choose Enhance info type.
Start transaction PM01
You access the Create Info type screen:
Choose Enhance Info types.
In the Info type no. field, enter the four-digit number of the info type you want to create. When you specify the info type number, please remember to enter any leading zeros.
In the Sub-Objects group box, flag CI Include.
Choose Create. The Dictionary: Initial Screen is displayed.
Create the Cl include.
Choose Activate.
Return to the Create Info type screen.
Choose Create All.
hope this information will help you..
and don't forget to reward points

Best way to move the distribution and subscriber to another server

What is the best way to move the distribution and subscriber role to a different server for transactional replication?
Stop activity on the publisher then script out the drop and create and point to the new ones?
The publisher will remain the same server.
Thank you!
Paula

Hi Paula,
According to your description, you want to move distribution database and subscription database to a different server.
Firstly, to move distribution database without dropping and recreating the replication topology, you could follow the steps in the
article . However, the best way I recommend is to remove the replication, create the distribution on the new server, and recreate publication and subscription.
To make this process simple, you could use SQL Server Management Studio (SSMS) to generate scripts and run the scripts to recreate publications and subscriptions or drop publications and subscriptions as the screenshot below. Checking ‘To create or enable
the components’ generates the script for creating the publications and subscriptions, and Checking ‘To drop or disable the components’ generates the script for dropping the publications and subscriptions.
Firstly, please use SSMS to generate the script which is used to create publications and subscriptions.
1.Connect to Publisher, or Subscriber in SSMS, and then expand the server node.
2.Right-click the Replication folder, and then click Generate Scripts.
3.In the Generate SQL Script dialog box, check ‘To create or enable the components’.
4.Click Script to File.
5.Enter a file name in the Script File Location dialog box, and then click Save. A status message is displayed.
6.Click OK, and then click Close. For more information about the process, please refer to the article:
http://msdn.microsoft.com/en-us/library/ms152483.aspx.
Secondly, follow the steps above, check ‘To drop or disable the components’ to generate the script used to drop publications and subscriptions. Then run the script to drop publications and subscriptions.
Thirdly, please disable distribution using Transact-SQL or SSMS following the steps in the article:
http://technet.microsoft.com/en-us/library/ms152757(v=sql.105).aspx.
Fourthly, please create the distribution at the new server using Transact-SQL or SSMS following the steps in the article:
http://msdn.microsoft.com/en-us/library/ms151192.aspx#TsqlProcedure.
Last, please run the script generated in the first step to recreate publications and subscriptions.
Regards,
Michelle Li
If you have any feedback on our support, please click
here.

Oracle Service Cloud Achieves Federal Risk and Authorization Management Program Provisional Authority to Operate

News Summary
Oracle Service Cloud -- a software-as-a-service (SaaS) solution -- has received a Federal Risk and Authorization Management Program (FedRAMP) moderate provisional Authority to Operate (p-ATO) from the Joint Authorization Board (JAB), comprised of the Chief Information Officers (CIOs) of the U.S. Department of Homeland Security (DHS), U.S. Department of Defense (DOD), and U.S. General Services Administration (GSA).
News Facts
Oracle announced that Oracle Service Cloud -- a software-as-a-service (SaaS) solution -- has received a Federal Risk and Authorization Management Program (FedRAMP) moderate provisional Authority to Operate (p-ATO) from the Joint Authorization Board.
The Oracle Service Cloud is Oracle's premier Software as a Service (SaaS) solution providing the industry's best in class customer service platform for enterprise customers. Oracle customers can deploy Oracle Service Cloud onto a robust, secure infrastructure hosting Oracle's patented customer experience (CX) software applications in an environment accredited to FedRAMP-moderate specifications.
Oracle Service Cloud has been granted a p-ATO by the FedRAMP's Joint Authorization Board (JAB), the primary governance and decision-making body for the FedRAMP program. A JAB p-ATO provides a government wide view for security and stringent review by the JAB Technical Representatives from the DHS, DOD, and GSA. As a result, government customers can save time and money by leveraging Oracle's JAB approval to grant their own authority to operate without having to go through a full certification and accreditation.
The rigorous review of Oracle's environment was completed by an accredited third-party organization at the FedRAMP moderate baseline level, for a SaaS offering using a community deployment model.
Supporting Quotes
"Oracle is very excited to announce the Service Cloud p-ATO as we continue to work towards meeting our public sector customers' demands for a highly secure, robust suite of cloud solutions built for government," Aaron Erickson, Director of Government Innovation, Public Sector North America, Oracle.
EMarkets Daily
Executive Biz
FCW.com
Markets Daily
Tech Taffy
Business Week
CNN
Congoo
Yahoo Finance

Have you checked the docs? There are some specific docs for enabling security like http://docs.oracle.com/cd/E18941_01/tutorials/jdtut_11r2_29/jdtut_11r2_29.html
which guide you through the process.
Timo

Form distribution and collection by e-mail alone?

I am trying to set up an automated system for data collection via Acrobat-generated forms. But, the respondents are in rural Africa and have at best lousy internet access and can barely manage e-mail. Do the form distribution and collection functions of Acrobat work when using e-mail back and forth alone, or is a connection to Acrobat.com required?
Thanks

Yes, it can work if the forms are sent by email. The idea is they are sent to you, and you use Acrobat to add them to Tracker. Or you can not use Tracker and just manage the data yourself.

Difference between extent management and segment management

friends what is the basic difference between extent management and segment management,as we know that segment is a collection of extents then why is it necesassry to manage both??..and what is the need to do so?

saugat chatterjee wrote:
friends what is the basic difference between extent management and segment management,as we know that segment is a collection of extents then why is it necesassry to manage both??..and what is the need to do so?Oracle stores data in it's own logical structure.
Blocks --> Extent --> Segment
Oracle block(also known as page) being the granular level where the data is stored. Extent is a collection of blocks.
When you specify extent management, you mean where the allocation/de-allocation of extents(group of blocks) will be managed (either in dictionary or using bitmaps).
When you specify segment space management, you mean that how the space inside a block will be managed. Extent management doesn't control space distribution inside block.
Regards,
S.K.

Difference between SAP PSCD and tax and Revenue management

Hi All,
I am new to SAP industry solutions for public sector and am actually trying to understand the new systems. Can anyone please tell me the difference between SAP PSCD and SAP Tax and Revenue management ? Please revert.
Thanks in advance,
Shakuntala

Hi Shakuntala,
PSCD is an industry add-on on top of SAP ERP FI-CA (Contract Accounting), which is part of SAP ERP Core.
Tax & Revenue Management is a Public Sector industry solution, which utilizes PSCD to enable some of its key processes (e.g. account management and collection management). However, TRM as a business solution also make use of other modules and systems (e.g. CRM).
The initial development of PSCD was strongly driven by Tax&Revenue Management, therefore people usually have hard time to differentiate between the two terms. But now PSCD is also used by and enhanced for other SAP Public Sector solutions like Grantor Management or Social Services.
Best regards,
Xiaoi
Edited by: Xiaopeng Tan on May 22, 2009 5:27 PM

RE: List Archive and Release Management

Hi back.
>> what procedures do people use to manage the development, testing
and release of software?
It's useful to have a separate repository for Development, QA, Production,
etc. It's true that you have to 'import' between them, each time you
propagate changes. It might seem like a pain to constantly export/import,
but actually it's better that way.
Firstly, you should only export to QA when you're absolutely sure it's ready
for quality assurance, and this doesn't happen every day (or shouldn't)
Second, the advantage of this is that you get a 'clean' import and compile
each time, with no other baggage. This is especially critical when you
migrate from QA to a production environment.
There's no need to have a testing_verXX repository, just make a different
workspace for each version of test.
Just check out all the components, import, and integrate. The 'old'
workspace will have a snapshot of the old release.
* Don't Update that old workspace or you'll lose it!
* Put an administrator password on the repos, to protect against
inadvertent usage.
* It's expensive to have many repositories running on your environment
manager, so I recommend only one repos for each of development, QA and
Deployment.
* You might want to consider only bringing up the production repos as
required, they hog RAM like crazy.
It's critical to have a complete image of each version of every application
you have in production. That way, you can recreate any problem.
It's even useful to migrate your development repos every now and then. As
you know, these repos beasties can grow quite large, and it's god to start
from scratch on a regular basis.
For example, every month or so, our core architecure team releases a new
version of the core components. We all integrate, and we create a new repos
from the core architecture stuff, and import all our stuff over the top of
it. That way, we keep a loose coupling between sub-systems, and their stuff
never depends on ours. Also, with a split developmen repos, you can locate
the different teams on different intranets, or even on different sides of
the world, all with relatively little fuss.
Forté SCM hooks and SCCSWe use a unix version control called CMVC.
Whenever we integrate, it checks out the pex files, exports them, and checks
them back in.
John Pianezze
S1 Technologies (Asia Pacific)
Melbourne, Australia
-----Original Message-----
From: Duncan Kinnear [SMTP:[email protected]]
Sent: Wednesday, July 21, 1999 1:05 PM
To: [email protected]
Subject: List Archive and Release Management
Hi folks!
First of all, does anyone know what's going on with the list archive
on
SageIT? There doesn't seem to be a search facility anymore. Seems
a
bit weird when each message is appended with a little signature
'advertising' a searchable archive.
Second (and this is the biggy!), what procedures do people use to
manage the development, testing and release of software? I'm
talking
about how you keep them separate, how you do hot-fixes, how you
identify installed versions at customer sites, etc.
I've thought that we could do it with separate repositories for
"current
development", "testing_verXX", "release_verXY", etc., where we
export
from "development" and then import into "testing", and similarily
for
"release".
Also, we are looking at using the Forté SCM hooks and SCCS on our
Unix host to store historical versions of the projects/classes. But
we
somehow need to identify which version of a particular component is
installed at the customer site. I had thought of defining a
constant in
each project/class called "SCCS_VER" which contains the SCCS
keywords that get mapped to SCCS ID and date when put into SCCS.
Then the constant could be used to display these values in a
Window's
"About" window.
Any thoughts/opinions welcome.
Cheers,
Duncan Kinnear,
McCarthy and Associates, Email:
[email protected]
PO Box 764, McLean Towers, Phone: +64 6 834
3360
Shakespeare Road, Napier, New Zealand. Fax: +64 6 834
3369
Providing Integrated Software to the Meat Processing Industry for
over 10 years
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/forte>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/forte>

Under Forte 2 we used to export all projects, then import them into a make
repository, then produce an app. Due to the time involved importing &
exporting, and errors resulting from importing projects out of order, we
switched to making copies of the dev repository and producing apps from
that. For us, it used to take 2+ hours to export/import, as opposed to 5
minutes for copying repository files. Unfortunately, we have found that
unless we force-compile prior to deploying, we will get errors when
attempting to compile partitions.
Our current procedure:
Shut down dev repos
Copy to make env
make a workspace that includes all projects
force-compile
update
integrate
make a new workspace for each app to make
make each app
export code
remove unused workspaces
clean repos
-----Original Message-----
From: Peter Sham (HTHK - Assistant Manager - Software Development, IITB)
[mailto:[email protected]]
Sent: Wednesday, July 21, 1999 3:31 AM
To: John Pianezze; Duncan Kinnear
Cc: [email protected]
Subject: RE: List Archive and Release Management
Hi,
We, like what you've explained, keep different releases of our application
in different workspaces. However, when the release is getting larger, this
"check-out-every-components-then-overwrite-by-import" procedure get tougher.
Sometimes, it even creates garbage in the repository which corrupts my
workspace.
So, I have an alternative proposal on this procedure ( though I haven't
really test on this idea ) which is to create a new repository for each new
release.
What do you think?
Regards,
Peter Sham.
-----Original Message-----
From: John Pianezze [SMTP:[email protected]]
Sent: Wednesday, July 21, 1999 3:44 PM
To: Duncan Kinnear
Cc: [email protected]
Subject: RE: List Archive and Release Management
Hi back.
what procedures do people use to manage the development, testingand release of software?
It's useful to have a separate repository for Development, QA, Production,
etc. It's true that you have to 'import' between them, each time you
propagate changes. It might seem like a pain to constantly export/import,
but actually it's better that way.
Firstly, you should only export to QA when you're absolutely sure it's
ready
for quality assurance, and this doesn't happen every day (or shouldn't)
Second, the advantage of this is that you get a 'clean' import and compile
each time, with no other baggage. This is especially critical when you
migrate from QA to a production environment.
There's no need to have a testing_verXX repository, just make a different
workspace for each version of test.
Just check out all the components, import, and integrate. The 'old'
workspace will have a snapshot of the old release.
* Don't Update that old workspace or you'll lose it!
* Put an administrator password on the repos, to protect against
inadvertent usage.
* It's expensive to have many repositories running on your environment
manager, so I recommend only one repos for each of development, QA and
Deployment.
* You might want to consider only bringing up the production repos as
required, they hog RAM like crazy.
It's critical to have a complete image of each version of every
application
you have in production. That way, you can recreate any problem.
It's even useful to migrate your development repos every now and then. As
you know, these repos beasties can grow quite large, and it's god to start
from scratch on a regular basis.
For example, every month or so, our core architecure team releases a new
version of the core components. We all integrate, and we create a new
repos
from the core architecture stuff, and import all our stuff over the top of
it. That way, we keep a loose coupling between sub-systems, and their
stuff
never depends on ours. Also, with a split developmen repos, you can locate
the different teams on different intranets, or even on different sides of
the world, all with relatively little fuss.
Forti SCM hooks and SCCSWe use a unix version control called CMVC.
Whenever we integrate, it checks out the pex files, exports them, and
checks
them back in.
John Pianezze
S1 Technologies (Asia Pacific)
Melbourne, Australia
-----Original Message-----
From: Duncan Kinnear [SMTP:[email protected]]
Sent: Wednesday, July 21, 1999 1:05 PM
To: [email protected]
Subject: List Archive and Release Management
Hi folks!
First of all, does anyone know what's going on with the list archive
on
SageIT? There doesn't seem to be a search facility anymore. Seems
a
bit weird when each message is appended with a little signature
'advertising' a searchable archive.
Second (and this is the biggy!), what procedures do people use to
manage the development, testing and release of software? I'm
talking
about how you keep them separate, how you do hot-fixes, how you
identify installed versions at customer sites, etc.
I've thought that we could do it with separate repositories for
"current
development", "testing_verXX", "release_verXY", etc., where we
export
from "development" and then import into "testing", and similarily
for
"release".
Also, we are looking at using the Forti SCM hooks and SCCS on our
Unix host to store historical versions of the projects/classes. But
we
somehow need to identify which version of a particular component is
installed at the customer site. I had thought of defining a
constant in
each project/class called "SCCS_VER" which contains the SCCS
keywords that get mapped to SCCS ID and date when put into SCCS.
Then the constant could be used to display these values in a
Window's
"About" window.
Any thoughts/opinions welcome.
Cheers,
Duncan Kinnear,
McCarthy and Associates, Email:
[email protected]
PO Box 764, McLean Towers, Phone: +64 6 834
3360
Shakespeare Road, Napier, New Zealand. Fax: +64 6 834
3369
Providing Integrated Software to the Meat Processing Industry for
over 10 years
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/forte>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/forte>-
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/forte>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/forte>

Distribution and commision management in insurance industry

Similar Messages

Maybe you are looking for