SNC Implementation Timelines
Hi SNC Experts ,
We were planning to build an SNC demo in our internal systems.I want to know if 2 months is a reasonable timeline to configure SNC and integrate it with ECC .
The scenarios we are looking at is
SNC for Forecast Capture .
Inventory Tracking
Customer Collaboration
We want to build this demo for abt 2 locations.
Let me know if it is a reasonable timeline.
Thanks in advance for your replies.
Regards,
Ranjini.
Hi Ranjini,
It depends on whether the system is ready by assuming there no issue from basis or XI it reasonable time line.
You can configure SNC and integrate it with ECC .
As per SAP for SNC for Forecast Capture,Inventory Tracking,Customer Collaboration time line is 9 weeks
Limits of Pilot Scope:
1u20133 plants, <= 3 customers, <= 200 products
Thanks,
Nikhil
Similar Messages
-
Steps and Check list SNC implementation
Dear Experts.
Believe that you'll spend some time to put your precious quotes on this query.
1. How SNC implementation should be done, what are the steps to be carried out?
2. What are the Pre-requisites and check list for implementation?
3. What testing needed to be done after implementation.
Thanks in advance
VinothHi Vinoth,
Responsibilities:
BASIS / Security :
1. System Upgrade / Installation
2. Post upgrade activities like SPAU (if its upgrade), notes that are required to be implemented.
3. Email / SMS set-up (Exchange infrastructure)
4. Work-out the authorizations that need to be provided for different Business roles
XI / PI :
1. Download the content for latest SNC release
2. Set-up communication between ERP <> XI <> SNC
3. Check SLDCHECK
4. Configuration scenario e.g. Sender Agreement, Receiver Agreement, Receiver Determination, Interface Determination, etc.
Functional :
1. Master Data set-up
2. Required customizing
Hopefully, this should give an overall idea.
Regards,
Sandeep
Re: What are the ODM components available in SNC?
Posted: Aug 6, 2010 10:39 AM in response to: Sandeep Mandhana Reply
Hi Nikhil & Sandeep,
Thanks for your valuable information.
Could you please let me know the checklist and steps that should be followed while implementing SNC.
Basis/Security peoples responsiblities?
XI/PI peoples responsibilites?
Functional peoples responsibilities?
Thanks in advance
vinoth -
Hi Experts,
Could you please provide me the SNC implementation document.
Thank you
SivaWe are implementing SNC between NGA webmethods to SAP . The configuration
part is done from Webmethods side.and configuration is done from SAP side
except profile parameters settings.
We are using Single PSE file in both the systems.we have installed the
"libsapcrypto.o" successfully. and created the PSE and cred_v2 files.
we have imported and exported the PSE file. after that we have created the parameters. and i have rebooted the system. but the SAP is not up and running. Oracle is running. R3trans also working. i am attching you the dev-w0 log file.
please suggest me.
we are working in AIX environment. and web methods OS is Linux.
We did not use any third party tools.
Thnks in Advance.
more dev_w0
trc file: "dev_w0", trc level: 1, release: "640"
ACTIVE TRACE LEVEL 1
ACTIVE TRACE COMPONENTS all, M
M sysno 01
M sid DV1
M systemid 324 (IBM RS/6000 with AIX)
M relno 6400
M patchlevel 0
M patchno 196
M intno 20020600
M make: single threaded, ASCII, 64 bit
M pid 3850476
M
M
M Mon May 24 06:32:45 2010
M ***LOG Q01=> tskh_init, WPStart (Workproc 0 1 3850476) [thxxhead.c 1142]
M calling db_connect ...
C Got ORACLE_HOME=/oracle/DV1/920_64 from environment
C got NLS_LANG='AMERICAN_AMERICA.WE8DEC' from environment
C Client NLS settings: AMERICAN_AMERICA.WE8DEC
C Logon as OPS$-user to get SAPCAD's password
C Connecting as /@DV1 on connection 0 (nls_hdl 0) ... (dbsl 640 250407)
C Nls CharacterSet NationalCharSet C EnvHp ErrHp ErrHpBatch
C 0 WE8DEC 1 11324fde0 1132593a0 113258c58
C Attaching to DB Server DV1 (con_hdl=0,svchp=11325c0b8,srvhp=11325c318)
C Starting user session (con_hdl=0,svchp=11325c0b8,srvhp=11325c318,usrhp=113266688)
C Now '/@DV1' is connected (con_hdl 0, nls_hdl 0).
C Got SAPCAD's password from OPS$-user
C Disconnecting from connection 0 ...
C Close user session (con_hdl=0,svchp=11325c0b8,usrhp=113266688)
C Now I'm disconnected from ORACLE
C Connecting as SAPCAD/<pwd>@DV1 on connection 0 (nls_hdl 0) ... (dbsl 640 250407)
C Nls CharacterSet NationalCharSet C EnvHp ErrHp ErrHpBatch
C 0 WE8DEC 1 11324fde0 1132593a0 113258c58
C Starting user session (con_hdl=0,svchp=11325c0b8,srvhp=11325c318,usrhp=113266688)
C Now 'SAPCAD/<pwd>@DV1' is connected (con_hdl 0, nls_hdl 0).
C Database NLS settings: AMERICAN_AMERICA.WE8DEC
C DB instance DV1 is running on pharaoh with ORACLE version 9.2.0.8.0 since MAY 24, 2010, 06:32:34
B Connection 0 opened (DBSL handle 0)
B Wp Hdl ConName ConId ConState TX PRM RCT TIM MAX OPT Date Time DBHost
B 000 000 R/3 000000000 ACTIVE NO YES NO 000 255 255 20100524 063245 pharaoh
M db_connect o.k.
M ICT: exclude compression: .zip,.cs,.rar,.arj,.z,.gz,.tar,.lzh,.cab,.hqx,.ace,.jar,.ear,.war,.css,.pdf,.js,.gzip,.uue,.bz2,.iso,.sda,
.sar,.gif
I MtxInit: 0 0 0
M SHM_PRES_BUF (addr: 700000002d37000, size: 24000000)
M SHM_ROLL_AREA (addr: 700000890000000, size: 30720000)
M SHM_PAGING_AREA (addr: 7000008a0000000, size: 134217728)
M SHM_ROLL_ADM (addr: 70000000441c000, size: 2672386)
M SHM_PAGING_ADM (addr: 7000008b0000000, size: 656416)
M ThCreateNoBuffer allocated 324144 bytes for 1000 entries at 7000008c0002000
M ThCreateNoBuffer index size: 3000 elems
M ThCreateVBAdm allocated 7040 bytes (50 server) at 7000008d0000000
X EmInit: MmSetImplementation( 2 ).
X EM/TOTAL_SIZE_MB = 4096
B
B Mon May 24 06:32:46 2010
B db_con_shm_ini: WP_ID = 0, WP_CNT = 21, CON_ID = -1
B
B Mon May 24 06:32:47 2010
B dbtbxbuf: Buffer TABL (addr: 700000900000100, size: 30000000, end: 700000901c9c480)
B dbtbxbuf: Profile: max_objects = 5000, displace = 1, reorg = 1
B dbtbxbuf: request_unit = 2000, sync_reload = 5, inval_reload = 5
B dbtbxbuf: protect_shm = 0, force_checks = 0
B dbtbxbuf: tsize_retry = 14420224
B ***LOG BB0=> buffer TABL started with length 30000000 bytes [dbtbxbuf#8 @ 16037] [dbtbxbuf1603 7]
B dbtbxbuf: Buffer TABLP (addr: 7000000046aa100, size: 16384000, end: 70000000564a100)
B dbtbxbuf: Profile: max_objects = 200, displace = 1, reorg = 1
B dbtbxbuf: request_unit = 2000, sync_reload = 5, inval_reload = 5
B dbtbxbuf: protect_shm = 0, force_checks = 0
B dbtbxbuf: tsize_retry = 8156096
B ***LOG BB0=> buffer TABLP started with length 16384000 bytes [dbtbxbuf#8 @ 16037] [dbtbxbuf1603 7]
B dbtbxbuf: Reading TBX statistics:
B dbtbxbuf: 66 object entries precreated
B Layout of EIBUF buffer shared memory:
B 0: 1 * 4 = 4
B 1: 1 * 360 = 360
B 2: 21 * 40 = 840
B 3: 4001 * 40 = 160040
B 4: 2000 * 160 = 320000
B 5: 4001 * 8 = 32008
B 6: 1 * 200 = 200
B 7: 65 * 8 = 520
B 8: 28752 * 128 = 3680256
B Tracing = 0, Shm Protection = 0, Force checks = 0, Recovery delay = 500000
B dbexpbuf: Buffer EIBUF (addr: 70000000564c108, size: 4194304, end: 700000005a4c108)
B ***LOG BB0=> buffer EIBUF started with length 4096k bytes [dbexpbuf#6 @ 2342] [dbexpbuf2342 ]
B Layout of ESM buffer shared memory:
B 0: 1 * 4 = 4
B 1: 1 * 360 = 360
B 2: 21 * 40 = 840
B 3: 4001 * 40 = 160040
B 4: 2000 * 160 = 320000
B 5: 4001 * 8 = 32008
B 6: 1 * 200 = 200
B 7: 65 * 8 = 520
B 8: 28752 * 128 = 3680256
B Tracing = 0, Shm Protection = 0, Force checks = 0, Recovery delay = 500000
B dbexpbuf: Buffer ESM (addr: 700000910000108, size: 4194304, end: 700000910400108)
B ***LOG BB0=> buffer ESM started with length 4096k bytes [dbexpbuf#6 @ 2342] [dbexpbuf2342 ]
B Layout of CUA buffer shared memory:
B 0: 1 * 4 = 4
B 1: 1 * 360 = 360
B 2: 21 * 40 = 840
B 3: 9001 * 40 = 360040
B 4: 4500 * 160 = 720000
B 5: 9001 * 8 = 72008
B 6: 1 * 200 = 200
B 7: 193 * 8 = 1544
B 8: 31488 * 256 = 8060928
B Tracing = 0, Shm Protection = 0, Force checks = 0, Recovery delay = 500000
B dbexpbuf: Buffer CUA (addr: 7000008c2e23108, size: 9216000, end: 7000008c36ed108)
B ***LOG BB0=> buffer CUA started with length 9000k bytes [dbexpbuf#6 @ 2342] [dbexpbuf2342 ]
B Layout of OTR buffer shared memory:
B 0: 1 * 4 = 4
B 1: 1 * 360 = 360
B 2: 21 * 40 = 840
B 3: 4001 * 40 = 160040
B 4: 2000 * 160 = 320000
B 5: 4001 * 8 = 32008
B 6: 1 * 200 = 200
B 7: 81 * 8 = 648
B 8: 28751 * 128 = 3680128
B Tracing = 0, Shm Protection = 0, Force checks = 0, Recovery delay = 500000
B dbexpbuf: Buffer OTR (addr: 700000920000108, size: 4194304, end: 700000920400108)
B ***LOG BB0=> buffer OTR started with length 4096k bytes [dbexpbuf#6 @ 2342] [dbexpbuf2342 ]
B ***LOG BB0=> buffer CALE started with length 500000 bytes [dbcalbuf#5 @ 2274] [dbcalbuf2274 ]
B dbtran INFO (init_connection '<DEFAULT>' [ORACLE:640.00]):
B max_blocking_factor = 5, max_in_blocking_factor = 50,
B min_blocking_factor = 5, min_in_blocking_factor = 5,
B prefer_union_all = 0, prefer_union_for_select_all = 0,
B prefer_fix_blocking = 0, prefer_in_itab_opt = 1,
B convert AVG = 0, alias table FUPD = 0,
B escape_as_literal = 1, opt GE LE to BETWEEN = 0,
B select * =0x0f, character encoding =SBCS / <none>:-,
B use_hints = abap->1, dbif->0x1, upto->2147483647, rule_in->0,
B rule_fae->0, concat_fae->0, concat_fae_or->0
M PfHIndInitialize: memory=<7000008e007d328>, header=<7000008e007d328>, records=<7000008e007d358>
M
M Mon May 24 06:32:48 2010
M SecAudit(RsauInit): Start init of Security Audit Log for first wp.
M SecAudit(RsauInit): Shared memory for Security Audit Log already exists.
M SecAudit(RsauInit): Re-initialize with new profile parameters
M SecAudit(RsauShmInit): SCSA size................ = 4096
M SecAudit(RsauShmInit): addr of SCSA............. = 700000020000000
M SecAudit(RsauShmInit): addr of RSAUSHM.......... = 700000020000450
M SecAudit(RsauShmInit): addr of RSAUSLOTINFO..... = 700000020000488
M SecAudit(RsauShmInit): addr of RSAUSLOTS........ = 700000020000494
M SecAudit(RsauShmInit): SHM version.............. = 5
M SecAudit(RsauShmInit): SHM Slot version......... = 2
M SecAudit(RsauShmInit): RSAU active.............. = 0
M SecAudit(RsauShmInit): number of slots possible. = 10
M SecAudit(RsauShmInit): number of slots requested = 2
M SecAudit(RsauShmInit): number of slots used..... = 2
M SecAudit(RsauShmInit): user selection........... = 0
M SecAudit(RsauShmInit): max size of one file..... = 0 KB
M SecAudit(RsauShmInit): max size of all files.... = 102400 KB
M SecAudit(RsauGetCurrentProfile): Init of shared memory completed
M SecAudit(RsauGetCurrentProfile): Security Audit Log not active
M SsfSapSecin: automatic application server initialization for SAPSECULIB
N SsfSapSecin: Looking for PSE in database
N SsfPseLoad: started...(path=/usr/sap/DV1/DVEBMGS01/sec, AS=pharaoh, instanceid=01)
N SsfPseLoad: Downloading file /usr/sap/DV1/DVEBMGS01/sec/SAPSYS.pse (client: , key: SYSPSE, len: 1215)
N SsfPseLoad: ended (1 of 1 sucessfully loaded, 1 checked...
N MskiCreateLogonTicketCache: Logon Ticket cache created in shared memory.
N MskiCreateLogonTicketCache: Logon Ticket cache pointer registered in shared memory.
M rdisp/reinitialize_code_page -> 0
M icm/accept_remote_trace_level -> 0
M rdisp/no_hooks_for_sqlbreak -> 0
N SncInit(): Initializing Secure Network Communication (SNC)
N IBM RS/6000 with AIX (st,ascii,SAP_UC/size_t/void* = 8/64/64)
N SncInit(): found snc/data_protection/max=3, using 3 (Privacy Level)
N SncInit(): found snc/data_protection/min=1, using 1 (Authentication Level)
N SncInit(): found snc/data_protection/use=9, using 3 (Privacy Level)
N SncInit(): Trying builtin default as a
N gssapi library name: "sncgss.o".
N SncInit(): snc/gssapi_lib UNDEFINED in profile!
N YOU DEFINITELY SHOULD SET snc/gssapi_lib !!
M *** ERROR => DlLoadLib: dlopen()= 0509-022 Cannot load module .
0509-026 System error: A file or directory in the path name does not exist. -> DLENOACCESS (2,No such file or directory) [dlux.c 314]
N *** ERROR => SncPDLInit(): DlLoadLib("sncgss.o")=DLENOACCESS
N [sncxxdl.0340]*** ERROR => SncPDLInit()==SNCERR_INIT, Adapter (#0) sncgss.o not loaded
N [sncxxdl.0604]<<- SncInit()==SNCERR_INIT
N sec_avail = "false"
M ***LOG R19=> ThSncInit, SncInitU ( SNC-000001) [thxxsnc.c 223]
M *** ERROR => ThSncInit: SncInitU (SNCERR_INIT) [thxxsnc.c 225]
M in_ThErrHandle: 1
M *** ERROR => SncInitU (step 1, th_errno 44, action 3, level 1) [thxxhead.c 9621]
M
M Info for wp 0
M
M stat = 4
M reqtype = 1
M act_reqtype = -1
M rq_info = 0
M tid = -1
M mode = 255
M len = -1
M rq_id = 65535
M rq_source = 255
M last_tid = 0
M last_mode = 0
M int_checked_resource(RFC) = 0
M ext_checked_resource(RFC) = 0
M int_checked_resource(HTTP) = 0
M ext_checked_resource(HTTP) = 0
M report = > <
M action = 0
M tab_name = > <
M PfStatDisconnect: disconnect statistics
M Entering TH_CALLHOOKS
M ThCallHooks: call hook >SAP-Trace buffer write< for event BEFORE_DUMP
M TrThHookFunc: called for WP dump
M ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
M *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c 730]
M *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c 254]
M Entering ThSetStatError
M Entering ThReadDetachMode
M call ThrShutDown (1)...
M ***LOG Q02=> wp_halt, WPStop (Workproc 0 3850476) [dpuxtool.c 318]
thank & regards
Shiva -
BC sets & Implementation timelines
Hi,
I would like to know about Business configuration( BC) sets and ways to reduce implementation timelines?
Regards,,
Nishant KansaraHi Nishant,
In the R/3 system from SAP, a Business Configuration Set (BC Set) is a management tool that allows the user to record, save, and share customized settings.
By creating a BC Set, the user is provided with a snapshot of the customized settings of a system that can be used later on as a template; SAP also provides pre-packaged BC sets designed for specific industries and applications.
BC Sets are useful because they provide continuity and prevent project team members from overwriting each other's settings.
They can also be used for a group rollout, where the customizing settings are bundled by the group headquarters and passed on in a structured way to its subsidiaries.
When a BC Set is created, values and combinations of values are copied from the original Customizing tables into the BC Set and can be copied into in the tables, views and view clusters in the customer system. The BC Sets are always transported into the customer system in which Customizing is performed.
The loading of BC Sets is logged by the system, i.e. which BC Set was copied when into the system, and any errors which occurred. This information is significant for Continuous Change and Upgrade.
There are two kinds of BC Sets:
· BC Sets (previously sometimes referred to as "simple BC Sets")
· Hierarchical BC Sets
A BC Set is identified by the following attributes:
· Name
· Type (simple or hierarchical)
· Release
· Software component
· Last changed by (person), on (date) and at (time)
BC Sets
A BC Set can contain data from one or more IMG activities. Each IMG activity is listed separately with its Customizing objects (tables or views). The data is selected by table columns and rows, each column is a field, each row a record.
Advantages of using BC Sets:
· Efficient group rollout.
· Industry sector systems are easier to create and maintain.
· Customizing can be performed at a business level.
· Change Management is quicker and safer.
· Upgrade is simpler.
REWARD POINTS IF HELPFUL
Regards
Sai -
Business content implementation timeline
Hello folks,
Trying to get an idea of timeline to plan for implementing standard business content for the new G/L functionality and Asset accounting. Assume a brand new SAP BI install EHP3 and no customization. Will appreciate any guidelines to consider for this.
Thanks!No customization? Standard guidance is that business content only gets you 10-20% of the way....
Also still many variables...performance optimization...for instance do you use FI_GL_10 or FI_GL_12...same content but different method of delta extraction and big concern depending on requirements....Also do you plan to convert business content to follow current best practice? LSA/EDW approach? Or leave it in 3.x format? Queries? Implementation of MultiProviders? Time to design security roles and validate? Bex web or simply analyzer? Are you wanting to know end to end time for no customization and integration testing with users, and time to go-live? Or just straight content activation time in development only?
The straight up content activation time with no customization, testing, etc. is the smallest part of the project, but is still significant depending on which InfoProviders you choose, etc.
You can stand it up in a couple of weeks...but you'll spend months making it useful. -
How much does 12i add to a normal implementation timeline?
We are currently running 11.5.10, however are undertaking a new initiative to re-implement. Naturally we are considering 12i for the re-implementation, however are concerned that it will add significant risk and time to our implementation, which has some aggressive targets. Our implementers are mostly internal staff who are extremely knowledgeable on 11.5.10. We are concerned that a task or activity we are familiar with will take significantly longer due to the functional and technical changes. Does anyone have any experience they could share around this? Again, I'm concerned that an interface design that would take 2-3 weeks in 11.5.10 now takes 4-5. Configuring for CRP which is a 2 week effort now takes a month. Any feedback would be greatly appreciated. Thanks!
Hello Readthebox,
Thank you for your inquiry today. I understand how important it is to have access to add multiple devices to your account. Do you recall which plan your are on? If you are currently on the Share Everything Plan, you can add a tablet to your existing account for as little as $10.00 per month. If you are on a different type of plan, your options will differ. To view our current offerings, please visit http://bit.ly/xdDajD. Please let us know if you have any additional questions, thanks!
MatthewS_VZW
VZW Support
Follow us on Twitter @VZWSUPPORT -
Hi All,
I want to know what is the average number of months and no of resource required to implement SAP MII for a pharma company with multi plant architecture. Also the no. of applications to integrate are around 10 to 12.
Many thanks in advance..
Regards,
Pooja S.
Edited by: PoojaShah on Sep 30, 2009 7:07 AMPooja,
you need some more information about your requests to give an estimation on effort and resources needed.
- what is your system landscape (local / central MII servers, one or more MI server) ?
- how is the MII knowledge of your MII developers (beginner, experienced) ?
- how many people are involved in the project (small or big team, many interface responsibles) ?
- how many interfaces do you need (external DBs, one or more SAP systems) ?
- what kind of applications are requested (only routing, number of GUI pages, reporting) ?
Without knowing those factors it is hard to give a reasonable estimation.
Michael -
Hi,
I read one statement some where else. The statement is XSLT mapping (e.g. for SNC mappings). Here my question is what is this SNC mapping and how we will do this SNC mapping in SAP XI
Thanks
RaoHi,
Connections between SAP system components that communicate using RFC can be secured with SNC, which secures the data communication paths between the various SAP system components. SAP systems support external security products that implement cryptographic algorithms. With SNC, you can apply these algorithms to your data for increased protection
Configuring SNC
http://help.sap.com/saphelp_nw04/helpdata/en/c3/d2281db19ec347a2365fba6ab3b22b/content.htm
A example where SNC implementation is useful
Security in XI
Regards,
Prateek
Message was edited by:
Prateek Srivastava -
Performance Impact When Using SNC Communication
Hello,
Does anybody know if and how much performance impact there is if we use SNC for communication between the SAP Server and SAPGUI?
I think there are two areas that may be impacted; Network and server CPU.
For network load, I did find a part in "Front-End Network Requirements for SAP Business Solutions" document saying "overhead of roughly 350 bytes per user interaction step" but it does not specify the type of encryption. I wonder if there is any other info on this?
For CPU impact, how much overhead should I consider for sapgui access?
I see no field for this in the quicksizer and I can't seem to find any white papers on this subject.
Thank you in advance.>
Peter Adams wrote:
> Ken,
>
> if you plan to use SAPcryptlib for SNC between SAP servers, then you should use a SAPcryptolib-compatible solution for the SNC communication between SAPGUI and SAP server, and there is only one vendor who can provide this. Let me know, if you need help finding it. My contact information is in my SDN business card.
Just so Kan is clear - It is not legal to use the SAP cryptolib provided by SAP for SNC between SAP GUI and SAP servers, so if x.509 is the desired mechanism you need to purchase additional software from the company which Peter works for to provide SAP GUI SNC-based SSO. I think instead, Kan might be using the free SAP supplied SNC Kerberos library, which is why I asked him to confirm this in my last post. I doubt he is interested to buy any third party software.
> As to the performance discussion: first of all, yes, there will be a small performance impact if SNC is used (no matter which type or implementation), but from our experience with many actual SNC implementations, I can state that this is practically not relevant. It is not noticeable by users. There were never any performance discussions with customers. See also SAP Note 1043694.
I agree with this - the performance impact is not noticed by users, but the system managers who look after the servers where SAP is installed, and the team responsible for the network need to be aware of any differences (if any) when SNC is turned on and when SNC is turned off. I think this is why Kan is asking these questions, not because he is concerned about users noticing any difference when they logon to SAP.
> Just a first quick comment on certain statements above: Tim's arguments for proving his overall statement are not conclusive from my perspective. Nor do I think his overall statement itself is correct.
The facts I mentioned are well known facts, e.g. symmetric crypto is far better from performance point of view than asymmetric. I know the examples I have shown which I found when doing a quick google search were not conclusive, but they were shown as initial examples, not necessarily the best examples. This is why I specifically mentioned that if you search in google yourself you will see many more references where comparisons are done between Kerberos (e.g. symmatric) compared with PKI (e.g. asymmetric).
> First of all, he only selects one aspect of performance - CPU impact of encryption algorithms.
No, I didn't. Some of the examples I referred to also discuss other differences. I also mentioend other differences such as memory and what protection level is used when configuring SNC.
> But for a true comparison, you'd have to look at all relevant aspects (latency, network overhead, ...).
Yes, I agree. No doubts here.
>Network performance overhead is usuallly worse with Kerberos than with PKI.
This is not true. When SAP is using SNC, the GSS-API standard is used and so the only network communication involves SAP software sending a standard GSS token from the workstation to the SAP server, and this GSS token is often about the same size, regardless of which mechanism is used, so any network performance differences are not related to the mechanism, but more related to the complexity of the cryptography used on each end (mostly on the server side).
>Second, you need to look at the specific usage scenario. For example, the first report referenced by Tim is an analysis about different Token Profile mechanism for WS Security, for one specific implementation. This does not allow to draw any conclusion for the SNC use case in general, and for sure not for a specific implemenation. It does not take the overhead for the encryption of the message content into account. Third, Tim associates PKI exclusively with asymmetric encryption. Yes, it is well known that asymmetric algorithms are slower than symmetric ones, but it is also well known that the encryption of the message content (by far the majority of the data) happens with symmetric encryption algorithms in the PKI scenario. With PKI-based SNC, you can even select a symmetric algorithm and use a more performant one that the ones that Kerberos prescribes.
Kerberos works with many different symmetric algorithms as well, so mentioning that the alg is selectable is not relavent to any comparison.
> To summarize, I will try and collect facts that will support the opposite point of view. From our practical experience, the performance overhead is not relevant, and criteria like consistency with SAPcryptolib, strength of security, ease of administration, choice of authentication and encryption mechanism, etc. are much more important.
>
> Peter -
No Relationship found to partner error..in Maintaining the ASN Number Ranges in SNC SC
Hello SNC Gurus,
We are working on one of SNC implementation project. We have to implement three Scenarios 1. Purchase Order Processing 2. Release Processing 3. Supplier Managed Inventory. I have done the configuration part perfectly in SNC for the above 3 scenarios.
I am facing an issue when i am performing the activity Maintaining the ASN Number Ranges activity.
Exactly the Error message is " No Relationship found to Partner **************(Partner No)
Here i created different partners to different Users for example for Customer Users and Supplier Users seperate business partners.
When i am trying to maintaining the ASN Number Ranges in SNC, I am getting the above issue. Not able to move forward and struckup this particular point. Please reply me the solution to overcome this issue, if anybody faced the above kind of issue earlier in your project expieriances.
Thanks,
SN.Hi Bharath,
Here in i am confirming the below answers for your questions
1. Yes its assigned to Partner. Its assigned to Customer.
2. Customer View -- Via /n/sca/ich_c t code.
3. I am defining the number range interval for the Customer. which my user id already assigned to Customer.
Here i am facing the issue in 2 activities. Facing the No Relationship Found to PartnerNo error in 1.. Maintaining ASN Number Ranges Attribute
Facing the error with " You are not authorized to maintain the Customer or Supplier " in 2. Maintaining ASN Number Ranges Intervals.
This is the input i entered in SNC Web UI path ASN Number Ranges Attribute Activity : Master Data --> Number Ranges --> Number Range Attributes: Interval Type : ASN, Customer : 1000 , Supplier : Vendor which is CIFFed to SNC. Append/Replace : A, Prefix : A2, No Overwrite : Check box should select , Max Number Length: 10
For Maintaining ASN Number Ranges Intervals activity : Customer : 1000, Supplier: 390001, IntervalFrom : 00000001 , IntervalTo : 19999999
Please let me know for any more information required. and reply back to me based in the above inputs mentioned is there any route cause to resolve this issue.
Thanks,
SN -
SAP R/3 implementation methodologies
Hi,
Can any one send me SAP R/3 implementation methodologies Documents and links.
Thanks & Regards,
Ramhi,
1
SAP R/3 Implementation
at Geneva Pharmaceuticals1
Company Background
Geneva Pharmaceuticals, Inc., one of the worlds largest generic drug manufacturers, is the North
American hub for the Generics division of Swiss pharmaceutical and life sciences company Novartis
International AG. Originally founded by Detroit pharmacist Stanley Tutag in 1946, Geneva moved
its headquarters to Broomfield, Colorado in 1974. The company was subsequently acquired by Ciba
Corporation in 1979, which in 1996, merged with Sandoz Ltd. in the largest ever healthcare merger to
form Novartis. Alex Krauer, Chairman of Novartis and former Chairman and CEO of Ciba,
commented on the strengths of the merger:
Strategically, the new company moves into a worldwide leadership position in life
sciences. Novartis holds the number two position in pharmaceuticals,
number one in crop protection, and has tremendous development potential in
nutrition.
The name Novartis comes from the Latin term novae artes or new arts, which eloquently captures
the companys corporate vision: to develop new skills in the science of life. Novartis inherited,
from its parent companies, a 200-year heritage of serving consumers in three core business segments:
healthcare, agribusiness, and nutrition. Business units organized under these divisions are listed in
Exhibit 1. Today, the Basel (Switzerland) based life sciences company employs 82,500 employees
worldwide, runs 275 affiliate operations in 142 countries, and generates annual revenues of 32 billion
Swiss Francs. Novartis key financial data for the last five years (1994-98) are presented in Exhibit 2.
The companys American Depository Receipts trade on the New York Stock Exchange under the
ticker symbol NVTSY.
Novartis global leadership in branded pharmaceuticals is complemented by its generic drugs
division, Novartis Generics. This division is headquartered in Kundl (Austria), and its U.S.
operations are managed by Geneva Pharmaceuticals. In 1998, Geneva had revenues of $300 million,
employed nearly 1000 employees, and manufactured over 4.6 billion dosage units of generic drugs.
1 This freeware case was written by Dr. Anol Bhattacherjee to serve as a basis for class discussion rather than
to demonstrate the effective or ineffective handling of an administrative or business situation. The author is
grateful to Randy Weldon, CIO of Geneva Pharmaceuticals, and his coworkers for their unfailing help
throughout the course of this project. This case can be downloaded and distributed free of charge for non-profit
or academic use, provided the contents are unchanged and this copyright notice is clearly displayed. No part of
this case can be used by for-profit organizations without the express written consent of the author. This case
also cannot be archived on any web site that requires payment for access. Copyright © 1999 by Anol
Bhattacherjee. All rights reserved.
ERP Implementation at Geneva Pharmaceuticals 2
Geneva portfolio currently includes over 200 products in over 500 package sizes, covering a wide
range of therapeutic categories, such as nervous system disorders, cardio-vascular therapies, and
nonsteroidal anti-inflammatory drugs. Its major products include ranitidine, atenolol, diclofenac
sodium, ercaf, metoprolol tartrate, triamterene with hydrochlorothiazide, and trifluoperazine.
Genevas business and product information can be obtained from the company web site at
www.genevaRx.com.
Generic drugs are pharmaceutically and therapeutically equivalent versions of brand name drugs with
established safety and efficacy. For instance, acetaminophen is the equivalent of the registered brand
name drug Tylenolâ, aspirin is equivalent of Ecotrinâ, and ranitidine HCl is equivalent of Zantacâ.
This equivalence is tested and certified within the U.S. by the Food and Drug Administration (FDA),
following successful completion of a bioequivalence study, in which the blood plasma levels of the
active generic drug in healthy people are compared with that of the corresponding branded drug.
Genevas business strategy has emphasized growth in two ways: (1) focused growth over a select
range of product types, and (2) growth via acquisitions. Internal growth was 14 percent in 1998,
primarily due to vigorous growth in the penicillin and cephalosporin businesses. In pursuit of further
growth, Geneva spend $52 million in 1997 to upgrade its annual manufacturing capacity to its current
capacity of 6 billion units, and another $23 million in 1998 in clinical trials and new product
development.
Industry and Competitive Position
The generic drug manufacturing industry is fragmented and highly competitive. In 1998, Geneva was
the fifth largest player in this industry, up from its eighth rank in 1997 but still below its second rank
in 1996. The companys prime competitors fall into three broad categories: (1) generic drugs
divisions of major branded drug companies (e.g., Warrick a division of Schering-Plough and
Apothecon a division of Bristol Myers Squibb), (2) independent generic drug manufacturers (e.g.,
Mylan, Teva Pharmaceuticals, Barr Laboratories, and Watson Pharmaceuticals), and (3) drug
distributors vertically integrating into generics manufacturing (e.g., AndRx). The industry also has
about 200 smaller players specializing in the manufacture of niche generic products. While Geneva
benefited from the financial strength of Novartis, independent companies typically used public stock
markets for funding their growth strategies.
In 1998, about 45 percent of prescriptions for medications in the U.S. were filled with generics. The
trend toward generics can be attributed to the growth of managed care providers such as health
maintenance organizations (HMO), who generally prefer lower cost generic drugs to more expensive
brand name alternatives (generic drugs typically cost 30-50 less than equivalent brands). However,
no single generics manufacturer has benefited from this trend, because distributors and pharmacies
view generic products from different manufacturers as identical substitutes and tend to
autosubstitute or freely replace generics from one company with those from another based on
product availability and pricing at that time. Once substituted, it is very difficult to regain that
customer account because pharmacies are disinclined to change product brand, color, and packaging,
to avoid confusion among consumers. In addition, consumer trust toward generics has remained
lower, following a generic drug scandal in the early 1990s (of which Geneva was not a part).
ERP Implementation at Geneva Pharmaceuticals 3
Margins in the generics sector has therefore remained extremely low, and there is a continuous
pressure on Geneva and its competitors to reduce costs of operations.
Opportunities for international growth are limited because of two reasons. First, consumers in some
countries such as Mexico are generally skeptical about the lack of branding because of their cultural
background. Second, U.S. generics manufacturers are often undercut by competitors from India and
China, where abundance of low-cost labor and less restrictive regulatory requirements (e.g., FDA
approval) makes drug manufacturing even less expensive.
Continuous price pressures has resulted in a number of recent industry mergers and acquisitions in the
generic drugs sector in recent years, as the acquirers seek economies of scale as a means of reducing
costs. The search for higher margins has also led some generics companies to venture into the
branded drugs sector, providing clinical trials, research and development, and additional
manufacturing capacity for branded drugs on an outsourced basis.
Major Business Processes
Genevas primary business processes are manufacturing and distribution. The companys
manufacturing operations are performed at a 600,000 square foot facility in Broomfield (Colorado),
while its two large distribution centers are located in Broomfield and Knoxville (Tennessee).
Genevas manufacturing process is scientific, controlled, and highly precise. A long and rigorous
FDA approval process is required prior to commercial production of any drug, whereby the exact
formulation of the drug or its recipe is documented. Raw materials are sourced from suppliers
(sometimes from foreign countries such as China), tested for quality (per FDA requirements),
weighed (based on dosage requirements), granulated (i.e., mixed, wetted, dried, milled to specific
particle sizes, and blended to assure content uniformity), and compressed into a tablet or poured into a
gelatinous capsule. Some products require additional coatings to help in digestion, stabilizing,
regulating the release of active ingredients in the human body, or simply to improve taste. Tablets or
capsules are then imprinted with the Geneva logo and a product identification number. Following a
final inspection, the medications are packaged in childproof bottles with a distinctive Geneva label, or
inserted into unit-dose blister packs for shipment.
Manufacturing is done in batches, however, the same batch can be split into multiple product types
such as tablets and capsules, or tablets of different dosages (e.g., 50 mg and 100 mg). Likewise,
finished goods from a batch can be packaged in different types of bottles, based on customer needs.
These variations add several layers of complexity to the standard manufacturing process and requires
tracking of three types of inventory: raw materials, bulk materials, and finished goods, where bulk
materials represent the intermediate stage prior to packaging. In some cases, additional intermediates
such as coating solution is also tracked. Master production scheduling is focused on the manufacture
of bulk materials, based on forecasted demand and replenishment of safety stocks at the two
distribution centers. Finished goods production depends on the schedule-to-performance, plus
availability of packaging materials (bottles and blister packs), which are sourced from outside
vendors.
ERP Implementation at Geneva Pharmaceuticals 4
Bulk materials and finished goods are warehoused in Broomfield and Knoxville distribution centers
(DC) prior to shipping. Since all manufacturing is done was done at Broomfield, inventory
replenishment of manufactured products is done first at Broomfield and then at Knoxville. To meet
additional customer demand, Geneva also purchases finished goods from smaller manufacturers, who
manufacture and package generic drugs under Genevas level. Since most of these outsourcers are
located along the east coast, and hence, they are distributed first to the Knoxville and then to
Broomfield. Purchasing is simpler than manufacturing because it requires no bill of materials, no
bulk materials management, and no master scheduling; Geneva simply converts planned orders to
purchase requisitions, and then to purchase orders, that are invoiced upon delivery. However, the
dual role of manufacturing and purchasing is a difficult balancing task, as explained by Joe Camargo,
Director of Purchasing and Procurement:
Often times, we are dealing with more than a few decision variables. We have to
look at our forecasts, safety stocks, inventory on hand, and generate a replenishment
plan. Now we dont want to stock too much of a finished good inventory because that
will drive up our inventory holding costs. We tend to be a little more generous on the
raw materials side, since they are less costly than finished goods and have longer
shop lives. We also have to factor in packaging considerations, since we have a
pretty short lead time on packaging materials, and capacity planning, to make sure
that we are making efficient use of our available capacity. The entire process is
partly automated and partly manual, and often times we are using our own
experience and intuition as much as hard data to make a good business decision.
Geneva supplies to a total of about 250 customers, including distributors (e.g., McKesson, Cardinal,
Bergen), drugstore chains (e.g., Walgreen, Rite-Aid), grocery chains with in-store pharmacies (e.g.,
Safeway, Kroger), mail order pharmacies (e.g., Medco, Walgreen), HMOs (e.g., Pacificare, Cigna),
hospitals (e.g., Columbia, St. Lukes), independent retail pharmacies, and governmental agencies
(e.g., U.S. Army, Veterans Administration, Federal prisons). About 70 percent of Genevas sales
goes to distributors, another 20 percent goes to drugstore chains, while HMOs, government, retail
pharmacies, and others account for the remaining 10 percent. Distributors purchase generic drugs
wholesale from Geneva, and then resell them to retail and mail order pharmacies, who are sometimes
direct customers of Geneva. The volume and dollar amount of transaction vary greatly from one
customer to another, and while distributors are sometimes allow Geneva some lead time to fulfill in a
large order, retail pharmacies typically are unwilling to make that concession.
One emerging potential customer segment is Internet-based drug retailers such as Drugstore.com and
PlanetRx.com. These online drugstores do not maintain any inventory of their own, but instead
accept customer orders and pass on those orders to any wholesaler or manufacturer that can fill those
orders in short notice. These small, customized, and unpredictable orders do not fit well with
Genevas wholesale, high-volume production strategy, and hence, the company has decided against
direct retailing to consumers via mail order or the Internet, at least for the near future.
As is standard in the generics industry, Geneva uses a complex incentive system consisting of
rebates and chargebacks to entice distributors and pharmacies to buy its products. Each drug is
assigned a published industry price by industry associations, but Geneva rebates that price to
distributors on their sales contracts. For instance, if the published price is $10, and the rebates
assigned to a distributor is $3, then the contract price on that drug is $7. Rebate amounts are
ERP Implementation at Geneva Pharmaceuticals 5
determined by the sales management based on negotiations with customers. Often times, customers
get proposals to buy the product cheaper from a different manufacturer and ask Geneva for a
corresponding discount. Depending on how badly Geneva wants that particular customer or push that
product, it may offer a rebate or increase an existing rebate. Rebates can vary from one product to
another (for the same customer) and/or from one order volume to another (for the same product).
Likewise, pharmacies ordering Genevas products are paid back a fraction of the sales proceeds as
chargebacks.
The majority of Genevas orders come through EDI. These orders are passed though multiple filters
in an automated order processing system to check if the customer has an active customer number and
sufficient credit, if the item ordered is correct and available in inventory. Customers are then
assigned to either the Broomfield or Knoxville DC based on quantity ordered, delivery expiration
dates, and whether the customer would accept split lots. If the quantity ordered is not available at the
primary DC (say, Knoxville), a second allocation is made to the secondary DC (Broomfield, in this
case). If the order cannot be filled immediately, a backorder will be generated and the Broomfield
manufacturing unit informed of the same. Once filled, the distribution unit will print the order and
ship it to the customer, and send order information to accounts receivable for invoicing. The overall
effectiveness of the fulfillment process is measured by two customer service metrics: (1) the ratio
between the number of lines on the order that can be filled immediately (partial fills allowed) to the
total number of lines ordered by the customer (called firstfill), and (2) the percentage of items send
from the primary DC. Fill patterns are important because customers typically prefer to get all items
ordered in one shipment.
Matching customer demand to production schedules is often difficult because of speculative buying
on the part of customers. Prices of drugs are typically reassessed at the start of every fiscal year, and
a distributor may place a very large order at the end of the previous year to escape a potential price
increase at the start of the next year (these products would then be stockpiled for reselling at higher
prices next year). Likewise, a distributor may place a large order at the end of its financial year to
transfer cash-on-hand to cost-of-goods-sold, for tax purposes or to ward off a potential acquisition
threat. Unfortunately, most generics companies do not have the built-in capacity to deliver such
orders within short time frames, yet inability to fulfill orders may lead to the loss of an important
customer. Safety stocks help meet some of these unforeseen demands, however maintaining such
inventory consumes operating resources and reduce margins further.
SAP R/3 Implementation
Up until 1996, Genevas information systems (IS) consisted of a wide array of software programs for
running procurement, manufacturing, accounting, sales, and other mission-critical processes. The
primary hardware platform was IBM AS/400, running multiple operational databases (mostly DB/2)
and connected to desktop microcomputers via a token-ring local area network (LAN). Each business
unit had deployed applications in an ad hoc manner to meet its immediate needs, which were
incompatible across business units. For instance, the manufacturing unit (e.g., materials requirements
planning) utilized a manufacturing application called MacPac, financial accounting used
Software/2000, and planning/budgeting used FYI-Planner. These systems were not interoperable,
and data that were shared across systems (e.g., accounts receivable data was used by order
ERP Implementation at Geneva Pharmaceuticals 6
management and financial accounting packages, customer demand was used in both sales and
manufacturing systems) had to be double-booked and rekeyed manually. This led to higher incidence
of data entry errors, higher costs of error processing, and greater data inconsistency. Further, data
was locked within functional silos and were unable to support processes that cut across multiple
business units (e.g., end-to-end supply chain management). It was apparent that a common,
integrated company-wide solution would not only improve data consistency and accuracy, but also
reduce system maintenance costs (e.g., data reentry and error correction) and enable implementation
of new value-added processes across business units.
In view of these limitations, in 1996, corporate management at Geneva initiated a search for
technology solutions that could streamline its internal processes, lower costs of operations, and
strategically position the company to take advantage of new value-added processes. More
specifically, it wanted an enterprise resource planning (ERP) software that could: (1) implement best
practices in business processes, (2) provide operational efficiency by integrating data across business
units, (3) reduce errors due to incorrect keying or rekeying of data, (4) reduce system maintenance
costs by standardizing business data, (5) be flexible enough to integrate with new systems (as more
companies are acquired), (6) support growth in product and customer categories, and (7) is Y2K (year
2000) compliant. The worldwide divisions of Novartis were considering two ERP packages at that
time: BPCS from Software Systems Associates and R/3 system from SAP. Eventually, branded drug
divisions decided to standardize their data processing environment using BPCS, and generics agreed
on deploying R/3.2 A brief description of the R/3 software is provided in the appendix.
R/3 implementation at Geneva was planned in three phases (see Exhibit 3). Phase I focused on the
supply side processes (e.g., manufacturing requirements planning, procurement planning), Phase II
was concerned with demand side processes (e.g., order management, customer service), and the final
phase was aimed at integrating supply side and demand side processes (e.g., supply chain
management). Randy Weldon, Genevas Chief Information Officer, outlined the goals of each phase
as:
In Phase I, we were trying to get better performance-to-master production schedule
and maybe reduce our cost of operations. Our Phase II goals are to improve sales
and operations planning, and as a result, reduce back orders and improve customer
service. In Phase III, we hope to provide end-to-end supply chain integration, so that
we can dynamically alter our production schedules to fluctuating demands from our
customers.
For each phase, specific R/3 modules were identified for implementation. These modules along with
implementation timelines are listed in Exhibit 3. The three phases are described in detail next.
2 However, each generics subsidiary had its own SAP R/3 implementation, and therefore data sharing across
these divisions remained problematic.
ERP Implementation at Geneva Pharmaceuticals 7
Phase I: Supply Side Processes
The first phase of R/3 implementation started on November 1, 1997 with the goal of migrating all
supply-side processes, such as purchasing management, capacity planning, master scheduling,
inventory management, quality control, and accounts payable from diverse hardware/software
platforms to a unified R/3 environment. These supply processes were previously very manual and
labor intensive. A Macpac package running on an IBM AS/400 machine was used to control shop
floor operations, prepare master schedules, and perform maintenance management. However, the
system did not have simulation capability to run alternate production plans against the master
schedule, and was therefore not used for estimation. The system also did not support a formal process
for distribution resource planning (DRP), instead generated a simple replenishment schedule based on
predefined economic order quantities. Materials requirements planning (MRP) was only partially
supported in that the system generated production requirements and master schedule but did not
support planned orders (e.g., generating planned orders, checking items in planned orders against the
inventory or production plan, converting planned orders to purchase orders or manufacturing orders).
Consequently, entering planned orders, checking for errors, and performing order conversion were all
entered manually, item by item, by different sales personnel (which left room for rekeying error).
Macpac did have a capacity resource planning (CRP) functionality, but this feature was not used since
it required heavy custom programming and major enhancements to master data. The system had
already been so heavily customized over the years, that even a routine system upgrade was considered
too unwieldy and expensive. Most importantly, the existing system did not position Geneva well for
the future, since it failed to accommodate consigned inventory, vendor-managed inventory, paperless
purchasing, and other innovations in purchasing and procurement that Geneva wanted to implement.
The objectives of Phase I were therefore to migrate existing processes from Macpac to R/3, automate
supply side process not supported by MacPac, and integrate all supply-side data in a single, real-time
database so that the synergies could be exploited across manufacturing and purchasing processes.
System integration was also expected to reduce inventory and production costs, improve
performance-to-master scheduling, and help managers make more optimal manufacturing and
purchase decisions. Since R/3 would force all data to be entered only once (at source by the
appropriate shop floor personnel), the need of data reentry would be eliminated, and hence costs of
data reconciliation would be reduced. The processes to be migrated from MacPac (e.g., MRP,
procurement) were fairly standardized and efficient, and were hence not targeted for redesign or
enhancement. Three SAP modules were scheduled for deployment: materials management (MM),
production planning (PP), and accounts payable component of financial accounting (FI). Exhibit A-1
in Appendix provides brief descriptions of these and other commonly referenced R/3 modules.
Phase I of R/3 implementation employed about ten IS personnel, ten full-time users, and ten part-time
users from business units within Geneva. Whitman-Hart, a consulting company with prior experience
in R/3 implementation, was contracted to assist with the migration effort. These external consultants
consisted of one R/3 basis person (for implementing the technical core of the R/3 engine), three R/3
configurators (for mapping R/3 configuration tables in MM, PP, and FI modules to Genevas needs),
and two ABAP programmers (for custom coding unique requirements not supported by SAP). These
consultants brought in valuable implementation experience, which was absolutely vital, given that
Geneva had no in-house expertise in R/3 at that time. Verne Evans, Director of Supply Chain
Management and a super user of MacPac, was assigned the project manager for this phase. SAPs
ERP Implementation at Geneva Pharmaceuticals 8
rapid implementation methodology called Accelerated SAP (ASAP) was selected for deployment,
because it promised a short implementation cycle of only six months.3
Four months later, Geneva found that little progress had been made in the implementation process
despite substantial investments on hardware, software, and consultants. System requirements were
not defined correctly or in adequate detail, there was little communication or coordination of activities
among consultants, IS personnel, and user groups, and the project manager was unable to identify or
resolve problems because he had no prior R/3 experience. In the words of a senior manager, The
implementation was clearly spinning out of control. Consultants employed by Whitman-Hart were
technical specialists, and had little knowledge of the business domain. The ASAP methodology
seemed to be failing, because although it allowed a quick canned implementation, it was not flexible
enough to meet Genevas extensive customization needs, did not support process improvements, and
alienated functional user groups from system implementation. To get the project back into track and
give it leadership and direction, in February 1998, Geneva hired Randy Weldon as its new CIO.
Weldon brought in valuable project management experience in R/3 from his previous employer,
StorageTek.4
From his prior R/3 experience, Weldon knew that ERP was fundamentally about people and process
change, rather than about installing and configuring systems, and that successful implementation
would require the commitment and collaboration of all three stakeholder groups: functional users, IS
staff, and consultants. He instituted a new project management team, consisting of one IS manager,
one functional manager, and one senior R/3 consultant. Because Genevas internal IS department had
no R/3 implementation experience, a new team of R/3 professionals (including R/3 basis personnel
and Oracle database administrators) was recruited. Anna Bourgeois, with over three years of R/3
experience at Compaq Computers, was brought in to lead Genevas internal IS team. Weldon was not
particularly in favor of Whitman-Hart or the ASAP methodology. However, for project expediency,
he decided to continue with Whitman-Hart and ASAP for Phase 1, and explore other options for
subsequent phases.
By February 1999, the raw materials and manufacturing component of R/3s MM module was up
and running. But this module was not yet integrated with distribution (Phase II) and therefore did
not have the capability to readjust production runs based on current sales data. However, several
business metrics such as yield losses and key performance indicators showed performance
improvement following R/3 implementation. For instance, the number of planning activities
performed by a single individual was doubled. Job roles were streamlined, standardized, and
consolidated, so that the same person could perform more value-added activities. Since R/3
eliminated the need for data rekeying and validating, the portion of the inventory control unit that
dealt with data entry and error checking was disbanded and these employees were taught new skills
for reassignment to other purchasing and procurement processes. But R/3 also had its share of
disappointments, as explained by Camargo:
3 ASAP is SAPs rapid implementation methodology that provides implementers a detailed roadmap of the
implementation life cycle, grouped into five phases: project preparation, business blueprint, realization, final
preparation, and go live. ASAP provides a detailed listing of activities to be performed in each phase,
checklists, predefined templates (e.g., business processes, cutover plans), project management tools,
questionnaires (e.g., to define business process requirements), and a Question & Answer Database
4 StorageTek is a leading manufacturer of magnetic tape and disk components also based in Colorado.
ERP Implementation at Geneva Pharmaceuticals 9
Ironically, one of the problems we have with SAP, that we did not have with
Macpac, is for the job to carry the original due date and the current due date, and
measure production completion against the original due date. SAP only allows us to
capture one due date, and if we change the date to reflect our current due date, that
throws our entire planning process into disarray. To measure how we are filling
orders, we have to do that manually, offline, on a spreadsheet. And we cant record
that data either in SAP to measure performance improvements over time.
Bourgeois summed up the implementation process as:
Phase I, in my opinion, was not done in the most effective way. It was done as
quickly as possible, but we did not modify the software, did not change the process,
or did not write any custom report. Looking back, we should have done things
differently. But we had some problems with the consultants, and by the time I came
in, it was a little too late to really make a change. But we learned from these
mistakes, and we hope to do a better job with Phases II and III.
Phase II: Demand Side Processes
Beginning around October 1998, the goals of the second phase were to redesign demand-side
processes such as marketing, order fulfillment, customer sales and service, and accounts receivable,
and then implement the reengineered processes using R/3. Geneva was undergoing major business
transformations especially in the areas of customer sales and service, and previous systems (Macpac,
FYI Planner, etc.) were unable to accommodate these changes. For instance, in 1998, Geneva started
a customer-based forecasting process for key customer accounts. It was expected that a better
prediction of order patterns from major customers would help the company improve its master
scheduling, while reducing safety stock and missed orders. The prior forecasting software, FYI
Planner, did not allow forecasting on a customer-by-customer basis. Besides, demand-side processes
suffered from similar lack of data integration and real-time access as supply side processes, and R/3
implementation, by virtue of its real-time integration of all operational data would help manage crossfunctional
processes better. Mark Mecca, Director of Customer Partnering, observed:
Before SAP, much of our customer sales and service were managed in batch mode
using MacPac. EDI orders came in once a night, chargebacks came in once a day,
invoicing is done overnight, shipments got posted once a day; so you dont know
what you shipped for the day until that data was entered the following day. SAP will
allow us to have access to real-time data across the enterprise. There will be
complete integration with accounting, so we will get accurate accounts receivable
data at the time a customer initiates a sales transaction. Sometime in the future,
hopefully, we will have enough integration with our manufacturing processes so that
we can look at our manufacturing schedule and promise a customer exactly when we
can fill his order.
However, the second phase was much more challenging than the first phase, given the non-standard
and inherently complex nature of Genevas sales and service processes. For instance, customer rebate
ERP Implementation at Geneva Pharmaceuticals 10
percentages varied across customers, customer-product combinations, and customer-product-order
volume combinations. Additionally, the same customer sometimes had multiple accounts with
Geneva and had a different rebate percentage negotiated for each account.
Bourgeois was assigned overall responsibility of the project, by virtue of her extensive knowledge of
EDI, R/3 interface conversion, and sales and distribution processes, and ability to serve as a technical
liaison between application and basis personnel. Whitman-Hart was replaced with a new consulting
firm, Arthur Andersen Business Consulting, to assist Geneva with the second and third phases of R/3
implementation. Oliver White, a consulting firm specializing in operational processes for
manufacturing firms, was also hired to help redesign existing sales and distribution processes using
best practices, prior to R/3 implementation. Weldon explained the reason for hiring two consulting
groups:
Arthur Anderson was very knowledgeable in the technical and configurational
aspects of SAP implementation, but Oliver White was the process guru. Unlike
Phase I, we were clearly targeting process redesign and enhancement in Phases II
and III, and Oliver White brought in best practices by virtue of their extensive
experience with process changes in manufacturing organizations. Since Phase I was
somewhat of a disaster, we wanted to make sure that we did everything right in
Phases II and III and not skimp on resources.
Technical implementation in Phase II proceeded in three stages: conceptual design, conference room
pilot, and change management. In the conceptual design stage, key users most knowledgeable with
the existing process were identified, assembled in a room, and interviewed, with assistance from
Oliver White consultants. Process diagrams were constructed on post-it notes and stuck to the
walls of a conference room for others to view, critique, and suggest modifications. The scope and
boundaries of existing processes, inputs and deliverables of each process, system interfaces, extent of
process customization, and required level of system flexibility were analyzed. An iterative process
was employed to identify and eliminate activities that did not add value, and generate alternative
process flows. The goal was to map the baseline or existing (AS-IS) processes, identify bottlenecks
and problem areas, and thereby, to create reengineered (TO-BE) processes. This information
became the basis for subsequent configuration of the R/3 system in the conference room pilot stage.
A core team of 20 IS personnel, users, and consultants worked full-time on conceptual design for 2.5
months (this team later expanded to 35 members in the conference room pilot stage). Another 30
users were involved part-time in this effort; these individuals were brought in for focused periods of
time (between 4 and 14 hours) to discuss, clarify, and agree on complex distribution-related issues.
The core team was divided into five groups to examine different aspects of the distribution process:
(1) product and business planning, (2) preorder (pricing, chargebacks, rebates, contracts, etc.), (3)
order processing, (4) fulfillment (shipping, delivery confirmation, etc.), and (5) post-order (accounts
receivable, credit management, customer service, etc.). Thirteen different improvement areas were
identified, of which four key areas emerged repeatedly from cross-functional analysis by the five
groups and were targeted for improvement: product destruction, customer dispute resolution, pricing
strategy, and service level. Elaborate models were constructed (via fish bone approach) for each of
these four areas to identify what factors drove these areas, what was the source of problems in these
areas, and how could they be improved using policy initiatives.
ERP Implementation at Geneva Pharmaceuticals 11
The conceptual design results were used to configure and test prototype R/3 systems for each of the
four key improvement areas in the conference room pilot stage. The purpose of the prototypes was to
test and refine different aspects of the redesigned processes such as forecast planning, contract
pricing, chargeback strategy determination, receivables creation, pre-transaction credit checking,
basic reporting, and so forth in a simulated environment. The prototypes were modified several times
based on user feedback, and the final versions were targeted for rollout using the ASAP methodology.
In the change management stage, five training rooms were equipped with computers running the
client version of the R/3 software to train users on the redesigned processes and the new R/3
environment. An advisory committee was formed to oversee and coordinate the change management
process. Reporting directly to the senior vice president level, this committee was given the mandate
and resources to plan and implement any change strategies that they would consider beneficial. A
change management professional and several trainers were brought in to assist with this effort.
Multiple brown bag luncheons were organized to plan out the course of change and discuss what
change strategies would be least disruptive. Super users and functional managers, who had the
organizational position to influence the behaviors of colleagues or subordinates in their respective
units, were identified and targeted as potential change agents. The idea was to seed individual
business units with change agents they could trust and relate to, in an effort to drive a grassroots
program for change.
To stimulate employee awareness, prior to actual training, signs were put up throughout the company
that said, Do you know that your job is changing? Company newsletters were used to enhance
project visibility and to address employee questions or concerns about the impending change. A
separate telephone line was created for employees to call anytime and inquire about the project and
how their jobs would be affected. The human resources unit conducted an employee survey to
understand how employees viewed the R/3 implementation and gauge their receptivity to changes in
job roles as a result of this implementation.
Training proceeded full-time for three weeks. Each user received an average of 3-5 days of training
on process and system aspects. Training was hands-on, team-oriented, and continuously mentored,
and was oriented around employees job roles such as how to process customer orders, how to move
inventory around, and how to make general ledger entries, rather than how to use the R/3 system.
Weldon described the rationale for this unique, non-traditional mode of training:
Traditional system training does not work very well for SAP implementation
because this is not only a technology change but also a change in work process,
culture, and habits, and these are very difficult things to change. You are talking
about changing attitudes and job roles that have been ingrained in employees minds
for years and in some cases, decades. System training will overwhelm less
sophisticated users and they will think, O my God, I have no clue what this computer
thing is all about, I dont know what to do if the screen freezes, I dont know how to
handle exceptions, Im sure to fail. Training should not focus on how they should
use the system, but on how they should do their own job using the system. In our
case, it was a regular on-the-job training rather than a system training, and
employees approached it as something that would help them do their job better.
ERP Implementation at Geneva Pharmaceuticals 12
Several startling revelations were uncovered during the training process. First, there was a
considerable degree of confusion among employees on what their exact job responsibilities were,
even in the pre-R/3 era. Some training resources had to be expended in reconciling these differences,
and to eliminate ambiguity about their post-implementation roles. Second, Genevas departments
were very much functionally oriented and wanted the highest level of efficiency from their
department, sometimes to the detriment of other departments or the overall process. This has been a
sticky cultural problem, and at the time of the case, the advisory committee was working with senior
management to see if any structural changes could be initiated within the company to affect a mindset
change. Third, Geneva realized that change must also be initiated on the customer side, so that
customers are aware of the systems benefits and are able to use it appropriately. In the interest of
project completion, customer education programs were postponed until the completion of Phase III of
R/3 implementation.
The primary business metric tracked for Phase II implementation was customer service level, while
other metrics included days of inventory on hand, dollar amount in disputes, dollar amount destroyed,
and so forth. Customer service was assessed by Genevas customers as: (1) whether the item ordered
was in stock, (2) whether Geneva was able to fill the entire order in one shipment, and (3) if
backordered, whether the backorder delivered on time. With a customer service levels in the 80s,
Geneva has lagged its industry competitors (mostly in the mid 90s), but has set an aggressive goal to
exceed 99.5 percent service level by year-end 1999. Camargo observed that there was some decrease
in customer service, but this decrease was not due to R/3 implementation but because Geneva faced
an impending capacity shortfall and the planners did not foresee the shortfall quickly enough to
implement contingency plans. Camargo expected that such problems would be alleviated as
performance-to-schedule and demand forecasting improved as a result of R/3 implementation. Given
that Phase II implementation is still underway at the time of the case (go live date is February 1,
2000), it is still too early to assess whether these targets are reached.
Phase 3: Integrating Supply and Demand
Genevas quest for integrating supply and demand side processes began in 1994 with its supply chain
management (SCM) initiative. But the program was shelved for several years due to the nonintegrated
nature of systems, immaturity of the discipline, and financial limitations. The initiative
resurfaced on the planning boards in 1998 under the leadership of Verne Evans, Director of SCM, as
R/3 promised to remove the technological bottlenecks that prevented successful SCM
implementation. Though SCM theoretically extends beyond the companys boundaries to include its
suppliers and customers, Geneva targeted the mission-critical the manufacturing resource planning
(MRP-II) component within SCM, and more specifically, the Sales and Operations Planning (SOP)
process as the means of implementing just-in-time production scheduling. SOP dynamically linked
planning activities in Genevas upstream (manufacturing) and downstream (sales) operations,
allowing the company to continuously update its manufacturing capacity and scheduling in response
to continuously changing customer demands (both planned and unanticipated). Genevas MRP-II and
SOP processes are illustrated in Exhibits 5 and 6 respectively.
Until the mid-1990s, Geneva had no formal SOP process, either manual or automated.
Manufacturing planning was isolated from demand data, and was primarily based on historical
ERP Implementation at Geneva Pharmaceuticals 13
demand patterns. If a customer (distributor) placed an unexpected order or requested a change in an
existing order, the manufacturing unit was unable to adjust their production plan accordingly. This
lack of flexibility led to unfilled orders or excess inventory and dissatisfied (and sometimes lost)
customers. Prior sales and manufacturing systems were incompatible with each other, and did not
allow the integration of supply and demand data, as required by SOP. In case production plans
required modification to accommodate a request from a major customer, such decisions were made on
an ad-hoc basis, based on intuition rather than business rationale, which sometimes had adverse
repercussions on manufacturing operations.
To remedy these problems, Geneva started a manual SOP process in 1997 (see Exhibit 6). In this
approach, after the financial close of each month, sales planning and forecast data were aggregated
from order entry and forecasting systems, validated, and manually keyed into master scheduling and
production planning systems. Likewise, prior period production and inventory data were entered into
order management systems. The supply planning team and demand analysis team arrived at their
own independent analysis of what target production and target sales should be. These estimates
(likely to be different) were subsequently reviewed in a joint meeting of demand analysts and master
schedulers and reconciliated. Once an agreement was reached, senior executives (President of
Geneva and Senior Vice Presidents), convened a business planning meeting, where the final
production plan and demand schedule were analyzed based on business assumptions, key customers,
key performance indicators, financial goals and projections (market share, revenues, profits), and
other strategic initiatives (e.g., introduction of a new product). The purpose of this final meeting was
not only to fine-tune the master schedule, but also to reexamine the corporate assumptions, growth
estimates, and the like in light of the master schedule, and to develop a better understanding of the
corporate business. The entire planning process took 20 business days (one month), of which the first
10 days were spent in data reentry and validation across corporate systems, followed by five days of
demand planning, two days of supply planning, and three days of reconciliation. The final business
planning meeting was scheduled on the last Friday of the month to approve production plans for the
following month. Interestingly, when the planning process was completed one month later, the
planning team had a good idea of the production schedule one month prior. If Geneva decided to
override the targeted production plans to accommodate a customer request, such changes undermined
the utility of the SOP process.
While the redesigned SOP process was a major improvement over the pre-SOP era, the manual
process was itself limited by the time-lag and errors in data reentry and validation across sales,
production, and financial systems. Further, the process took one month, and was not sensitive to
changes in customer orders placed less than a month from their requested delivery dates. Since much
of the planning time was consumed in reentering and validating data from one system to another,
Evans estimated that if an automated system supported real-time integration of all supply and demand
data in a single unified database, the planning cycle could be reduced to ten business days.
Though SAP provided a SOP module with their R/3 package, Genevas R/3 project management team
believed that this module lacked the intelligence required to generate an optimal production plan
from continuously changing supply and demand data, even when all data were available in a common
database. The R/3 system was originally designed as a data repository, not an analysis tool to solve
ERP Implementation at Geneva Pharmaceuticals 14
complex supply chain problems or provide simulation capabilities5. Subsequently, in 1999, when
SAP added a new Advanced Purchase Optimizer (APO) module to help with data analysis, Geneva
realized that the combination of R/3s SOP and APO modules would be the answer to their unique
SOP needs.
At the time of the case, Geneva was in the initial requirements definition stage of SOP
implementation. To aid in this effort, Oliver White had created a template that could aggregate all
relevant data required for SOP from distribution, operations, purchasing, quality control, and other
functional databases, and tie these data to their source processes. It was expected that the template
would provide a common reference point for all individuals participating in the SOP process and
synchronize their decision processes.
The primary business metric targeted for improvement in Phase III implementation is available to
promise (ATP), i.e., whether Geneva is able to fulfill a customer order by the promised time. ATP is
an integration of customer service level and business performance, the erstwhile key business metrics
in the pre-SOP era. Customers often placed orders too large to be fulfilled immediately, and ATP
was expected to provide customers with reasonably accurate dates on when they should expect which
part of their order to be filled. Generating and meeting these dates would enable Geneva improve its
customer service levels that not providing any fulfillment dates at all. With declining profit margins,
as the generics industry is forced to explore new means of cost reduction, Geneva expects that thin
inventories, just-in-time manufacturing, and top quality customer service will eventually be the
drivers of success, hence the importance of this metric. Evans explains the importance of ATP as a
business metric as:
Most of our customers understand the dynamics of our business, and how difficult it
is for us to fulfill a large order instantaneously with limited production capacity. But
most of them are willing to bear with backorders if we can promise them a
reasonable delivery date for their backorder and actually deliver on that date. That
way, we take less of a customer service level hit than defaulting on the order or being
unable to accommodate it. In commodity business such as ours, customer service is
the king. Our customers may be willing to pay a little premium over the market for
assured and reliable service, so that they can meet their obligations to their
customers. Customer service may be a strategic way to build long-term relationships
with our customers, but of course, we are far from proving or disproving that
hypothesis.
Future Plans
Despite some initial setbacks in Phase I, Geneva is now back on the road to a successful R/3
implementation. The senior management, functional units, and IS personnel are all enthusiastic about
the project and looking forward to its deployment in all operational areas of business and beyond.
R/3 implementation has opened up new possibilities to Geneva and more means of competing in the
5 Typically, manufacturing companies requiring SCM analysis used additional analysis tools from I2
Technologies or Manugistics on top of ERP databases from SAP or Oracle for SCM purposes.
ERP Implementation at Geneva Pharmaceuticals 15
intensely competitive generic drugs industry. Weldon provided an overall assessment of the benefits
achieved via R/3 implementation:
In my opinion, we are doing most of the same things, but we are doing them better,
faster, and with fewer resources. We are able to better integrate our operational
data, and are able to access that data in a timely manner for making critical business
decisions. At the same time, SAP implementation has placed us in a position to
leverage future technological improvements and process innovations, and we expect
to grow with the system over time.
Currently, the primary focus of Genevas R/3 implementation is timely completion of Phase II and III
by February 2000 and December 2000 respectively. Once completed, the implementation team can
then turn to some of R/3s additional capabilities that are not being utilized at Geneva. In particular,
the quality control and human resource modules are earmarked for implementation after Phase III.
Additionally, Geneva plans to strengthen relationships with key suppliers and customers by
seamlessly integrating the entire supply chain. The first step in this direction is vendor managed
inventory (VMI), that was initiated by Geneva in April 1998 for a grocery store chain and a major
distributor. In this arrangement, Geneva obtains real-time, updated, electronic information about
customers inventories, and replenish their inventories on a just-in-time basis without a formal
ordering process, based on their demand patterns, sales forecast, and actual sales (effectively
operating as customers purchasing unit).6 Genevas current VMI system, Score, was purchased from
Supply Chain Solutions (SCS) in 1998. Though Mecca is satisfied with this system, he believes that
Geneva can benefit more from R/3s ATP module via a combination of VMI functionality and
seamless company-wide data integration. Currently, some of Genevas customers are hesitant to
adopt VMI because sharing of critical sales data may cause them to lose bargaining power vis-à-vis
their suppliers or prevent them from speculative buying. But over the long-term, the inherent
business need for cost reduction in the generics industry is expected to drive these and other
customers toward VMI. Geneva wants to ensure that the company is ready if and when such
opportunity arises.
6 Real-time customer forecast and sales data is run through a VMI software (a mini-MRP system), which
determines optimum safety stock levels and reorder points for customers, and a corresponding, more optimum
production schedule for Geneva. Initial performance statistics at the grocery store chain indicated that customer
service levels increased from 96 percent to 99.5 percent and on-hand inventory decreased from 8 weeks to six
weeks as a result of VMI implementation. For the distributor, Geneva expects that VMI will reduce on-hand
inventory from seven months to three months.
ERP Implementation at Geneva Pharmaceuticals 16
Exhibit 1. Novartis divisions
Divisions Business Units
Healthcare Pharmaceuticals
Consumer Health
Generics
CIBA Vision
Agribusiness Crop Protection
Seeds
Animal Health
Nutrition Infant and Baby Nutrition
Medical Nutrition
Health Nutrition
Exhibit 2. Novartis five-year financial summary
1998 1997 1996 1995 1994
Annual sales 31,702 31,180 36,233 35,943 37,919
Sales from healthcare 17,535 16,987 14,048 12,906 14,408
Sales from agribusiness 8,379 8,327 7,624 7,047 7,135
Sales from consumer health 5,788 5,866 5,927 5,777 4,258
Sales from industry - - 8,634 10,213 12,118
Operating income 7,356 6,783 5,781 5,714 5,093
Net income 6,064 5,211 2,304 4,216 3,647
Cash flow from operations 5,886 4,679 4,741 5,729 5,048
R&D expenditure 3,725 3,693 3,656 3,527 3,786
Total assets 55,375 53,390 58,027 50,888 51,409
Net operating assets 20,913 19,619 21,820 22,278 22,952
Number of employees at year-end 82,449 87,239 116,178 133,959 144,284
Sales per employee (Swiss Francs) 369,337 350,905 289,705 258,357 266,740
Debt/equity ratio 0.28 0.41 0.46 0.46 0.57
Current ratio 2.0 1.7 1.9 2.2 1.6
Return on sales (%) 19.1 16.7 13.9 - -
Return on equity (%) 21.0 20.7 16.7 - -
Note: All figures in millions of Swiss Francs, except otherwise indicated.
Pre-1996 data is on pro forma basis, based on pooled data from Ciba and Sandoz.
ERP Implementation at Geneva Pharmaceuticals 17
Exhibit 3. Phases in R/3 implementation at Geneva
Phases1 Business processes R/3 modules Implementation timeline
(inception to go-live)
Phase I: Supply side
management
MRP, purchasing, inventory
management
MM2, PP,
FI/CO3
Nov 1997 Feb 1999
Phase II: Demand side
management
Order management, sales,
customer service
SD, MM4,
FI/CO5
Oct 1998 Feb 2000
Phase III: Supply/demand
integration, business
intelligence
Sales & operations planning,
supply chain management,
data warehousing
APO, MES,
BIW
Early 2000 End 2000
Note: 1Vendor selection took place in mid-1997
2MM: Raw materials inventory
4MM: Finished goods inventory
3FI/CO: Accounts payable
5FI/CO: Accounts receivable
Vendor
System
Sales orders ATP
Sales & Distribution
Customer
Inquiry Quotation
Order
Generation
Goods
Issue
Billing
Delivery Document
Update
Financials
Inventory
Management
Update
Demand
Management
Run
MPS/MRP
Production Planning Materials
Management
Finance &
Controlling
Exhibit 4. Genevas order management process
ERP Implementation at Geneva Pharmaceuticals 18
Business Planning
Sales & Operations
Planning
DRP Master
Scheduling
Detailed Materials/
Capacity Planning
Plant & Supplier
Scheduling
Execution
Demand
Management
Rough-Cut
Capacity Planning
Exhibit 5. Genevas manufacturing resource planning process
Exhibit 6. Genevas sales & operations planning process
Demand
Planning
Supply
Planning
Integration/
Reconciliation
Business Planning
(S&OP)
Key Activities:
Product planning
Forecasting
Sales planning
Performance
management
(prior period)
Master production
scheduling
Capacity planning
Materials requirements
planning
Consolidation of
demand, supply,
inventory, and
financial plans
Feedback to
demand and
supply planning
Performance review
Key assumptions review
Product family review
Key customers review
Financial review
Approval/action items
Current Planning Cycle (Monthly):
Financial
close
(prior month)
0 5 10 15 17 20 (Business
days)
Demand
planning
Supply
planning
Integration
Business
planning
Goal:
To reduce the planning cycle time from one month to 10 business days.
ERP Implementation at Geneva Pharmaceuticals 19
Appendix
SAP (Systems, Applications, and Products in Data Processing) is the worlds fourth largest software
company, and the largest enterprise resource planning (ERP) vendor. As of February 1999, the
company employed 19,300 employees and had annual revenues of $5 billion, annual growth of 44
percent, over 10,000 customers in 107 countries, and 36 percent of the ERP market. SAP AG was
founded in 1972 by Dr. H.C. Hasso Plattner and Dr. Henning Kagermann in Walldorf, Germany with
the goal of producing an integrated application software, that would run all mission-critical operations
in corporations, from purchasing to manufacturing to order fulfillment and accounting. This
integration would help companies optimize their supply chains, manage customer relationships, and
make better management decisions. SAP brings in 26 years of leadership in process innovations and
ERP, and invests 20 percent of its revenues back into research and development.
SAPs first breakthrough product was the R/2 system, which ran on mainframe computers. R/2 and
its competitors were called ERP systems, to reflect the fact that they extended the functions of earlier
materials requirements planning (MRP) systems in manufacturing firms to include other functions
and business processes such as sales and accounting. In 1992, SAP released its R/3 system, the
client/server variant of the earlier R/2 system, which was installed in 20,000 locations worldwide, and
R/2 is installed in over 1,300 locations by mid-1999. Initially targeted at the worlds largest
corporations such as AT&T, BBC, Deutsche Bank, IBM, KPMG, Merck, Microsoft, Nestle, Nike,
and Siemens, R/3 has since been deployed by companies of all sizes, geographical locations, and
industries. SAP solutions are available for 18 comprehensive industry solutions (verticals) for
specific industry sectors such as banking, oil & gas, electronics, health care, and public sector. -
Does SAP support Solaris 10 ZFS filesystem when using DB2 V9.5 FP4?
Hi,
I'm installing NW7 (BI usage). SAPINST has failed in the step "ABAP LOAD due to the DB2 error message
"Unsupported file system type zfs for Direct I/O". It appears my Unix Admin must have decided to set these filesystems as ZFS on this new server.
I have several questions requiring your expertise.
1) Does SAP support ZFS filesystems on Solaris 10 (SPARC hardware)? I can not find any reference in SDN or Service Market Place? Any reference will be much appreciated.
2) How can I confirm my sapdata fielsystems are ZFS?
3) What actions do you recommend for me to resolve the SAPINST errors? Do I follow the note "Note 995050 - DB6: NO FILE SYSTEM CACHING for Tablespaces" to disable "Direct I/O" for all DB2 tablespaces? I have seen Markus Doehr's forum Link:[ thread|Re: DB2 on Solaris x64 - ZFS as filesystem possible?; but it does not state exactly how he overcame the error.
regards
BennyHi Frank,
Thanks for your input.
I have also found the command "zfs list" that would display any ZFS filesystems.
We have also gone back to UFS as the ZFS deployment schedule does not meet this particular SAP BW implementation timeline.
Has any one come across any SAP statement that states NW7 can be deployed with ZFS for DB2 database on Solaris SPARC platform. If not, I'll open an OSS message.
regards
Benny -
SNP Planned order - Doesnt get the complete BOM when CIFd to ECC
Hello,
When we create SNP Planned order in APO and sent to ECC, the Planned order doesn’t get the complete BOM, it works for the most part, except if we have Materials from multiple plants within the same BOM (sourcing from multiple plants).
Do we have to do any separate Configuration for this scenario?
We are planning only the End item in SNP, and we are generating the production version and PDS transfer to APO. We are not transferring all the materials to APO.
if we go to the Change mode of the Planned order in ECC and re-explode the BOM, I get all the components from the BOM, its just that when the planned order gets created thru the CIF we have this issue.
Any help would be appreciated.
Regards
GkHello Marius
Thank you for your quick response.
I looked at the SAP note you mentioned, the description seems to be matching with the issue we are having. Recently we had SNC implemented, and the note states that that can be the case why the components are getting deleted during planned order creation.
The only thing about this note is its very old, and we are having the SAP 6.0 and SCM 7.2 ,
Do you think this would be still applicable.
I will look into the details and let you know whether the note is applicable for us.
Regards
Gk -
hi all
I am encountering a strange problem when i implement timeline graphs [http://apex.oracle.com/pls/otn/f?p=50734:2:5792901813709709::NO |http://apex.oracle.com/pls/otn/f?p=50734:2:5792901813709709::NO ] everything is working fine but in the process is not generating the xml from table. Iam using the same code and tables.I have checked it by calling the process from url and found the xml content is not generated as expected, instead only htp.p('Phone: ' || pPhone); statement is executed and output is printed in the browser. But when i implemented the same in apex.oracle.com workspace it is working fine and i can see all the xml content when i checked from url.
Iam wondering whether there are any issues in my workspace that effect the generation of xml or are there any setting to be made in workspace.
create or replace package TLTest is
procedure AllEmps;
end TLTest;
create or replace package body TLTest is
procedure WriteHeader is
begin
owa_util.mime_header('application/xml', FALSE );
owa_util.http_header_close;
htp.p('<data>');
end;
procedure WriteFooter is
begin
htp.p('</data>');
end;
procedure WriteEvent(pName IN Varchar2,
pHireDate IN Date,
pPhone IN Varchar2) is
begin
htp.p('<event');
htp.p('start="' || to_char(pHireDate, 'Mon DD YYYY') || ' 00:00:00 GMT"');
htp.p('title="' || pName || '">');
htp.p('Phone: ' || pPhone);
htp.p('</event>');
end;
procedure AllEmps is
begin
WriteHeader;
for rec in (select Trim(first_name || ' ' || last_name) name, hire_date, Phone_Number
from employees)
loop
WriteEvent(rec.Name, rec.hire_date, rec.phone_number);
end loop;
WriteFooter;
end;
end TLTest;
I hope i have made it clear. Any tips.
thanks in advance
Pavanhi all
I am encountering a strange problem when i implement timeline graphs [http://apex.oracle.com/pls/otn/f?p=50734:2:5792901813709709::NO |http://apex.oracle.com/pls/otn/f?p=50734:2:5792901813709709::NO ] everything is working fine but in the process is not generating the xml from table. Iam using the same code and tables.I have checked it by calling the process from url and found the xml content is not generated as expected, instead only htp.p('Phone: ' || pPhone); statement is executed and output is printed in the browser. But when i implemented the same in apex.oracle.com workspace it is working fine and i can see all the xml content when i checked from url.
Iam wondering whether there are any issues in my workspace that effect the generation of xml or are there any setting to be made in workspace.
create or replace package TLTest is
procedure AllEmps;
end TLTest;
create or replace package body TLTest is
procedure WriteHeader is
begin
owa_util.mime_header('application/xml', FALSE );
owa_util.http_header_close;
htp.p('<data>');
end;
procedure WriteFooter is
begin
htp.p('</data>');
end;
procedure WriteEvent(pName IN Varchar2,
pHireDate IN Date,
pPhone IN Varchar2) is
begin
htp.p('<event');
htp.p('start="' || to_char(pHireDate, 'Mon DD YYYY') || ' 00:00:00 GMT"');
htp.p('title="' || pName || '">');
htp.p('Phone: ' || pPhone);
htp.p('</event>');
end;
procedure AllEmps is
begin
WriteHeader;
for rec in (select Trim(first_name || ' ' || last_name) name, hire_date, Phone_Number
from employees)
loop
WriteEvent(rec.Name, rec.hire_date, rec.phone_number);
end loop;
WriteFooter;
end;
end TLTest;
I hope i have made it clear. Any tips.
thanks in advance
Pavan -
SAP GUI with SNC logon and Hummingbird Exceed - SAP GUI window size issue
We have discovered an issue when SAP GUI 7.10 is used to logon via SNC and Hummingbird Exceed is used on the same workstation to logon to a UNIX system either via x-windows or telnet.
When the user logs onto a UNIX system using Hummingbird Exceed, then uses SAP GUI to logon to a SAP system with SNC authentication, the SAP GUI authentication works, but the favourites list is not fully displayed and has to be resized before any of the entries are available.
Has anybody else seen this issue, and do they know if there is a fix available ? We wondered if there might be an issue with fonts or some other sort of conflict between Exceed and SAP GUI, but it is strange that the problem only occurs if SNC authentication is being used, and when userid+password is used to logon to SAP the problem does not occur.
Cheers,
TimHello Tim and Wolfgang,
I was curious too as I found it interesting... so I tested a few combinations, but could not reproduce what Tim has described, at least not before my CPU reached 100% and the applications stopped responding (~2GHz processor, 1GB RAM, 48 kbps connection, latency ~ 2 x width of the Pacific Ocean, but Backend 7.00!).
However I did notice some indications which might be a help (based on 7.00!):
Back in 4.?? there was a problem in that large menus could not be searched(!). Sorry, I don't have access to SAP now, but from memory the note # was 444043 (or very similar) and introduced a form routine for large menus - from a printscreen I still have the message number which led me to the note - 'I476(S#)'.
The system certainly distinguishes between MENU_TYPEs and the above note corrections could be found in several locations relating to the SAP menu 'S', the role menu 'A' etc, but I could only see that for favourites 'F' this is implemented for the menu search (when searching, not when loading).
@ Tim: Ask you customer to create a favourites menu which only has 1 node or max 2 (certainly not more than 4!) and ~ 20 executable objects in it (not more than 30!)? Can they under any conditions achieve the described problem with such a menu?
If not possible to reproduce, then the closest I could guess is a maximum limit of 4 nodes and max 30 objects for a 'F'avourite menu, before it is a minimum candidate for "performance problems" and consideration to be converted to a role ('A'ctivity group) menu instead.
Sorry that I can only help by speculating, because I could not reproduce what you have described.
Hopefully this problem will not happen to me in the New Year, and hope you will solve it for the rest of the year
Cheers,
Julius
Updated memory (not RAM) by: Julius Bussche on Jan 3, 2008 9:07 AM
Maybe you are looking for
-
Dear all, We have problem with a user few days before,while updating exchange rate daily, Suddenly all datas disappeared for a moment & reappeared,we also encountered problems before while entering goods issue & also in receipt from production a mont
-
Please allow more than 13 digits in the financial report calculation
Dear SAP development team, I would like to suggest the financial report programming code or query or what else that is used to generate the financial reports (TB;P&L;BS) could allow the calculation of debit or credit more than 9223372036854. It made
-
GOTO Functionality from BW Report to Transaction on Portal
Hi All, I wanted to know if anyone has any idea about having a "go to" function capability from the BW report to a transaction on the Portal? for eg if we can jump from a CRM complaints or opportunity report to the corresponding transaction on portal
-
Data load - Financial documents
Hi I need to upload Payments to Open Receivables Items (Open Debit Items) (FB70) & Payments to Open Receivables Items (Open Credit Items)(FB75) into SAP from the legacy system. I am looking for a standard program that can upload these. Can the progra
-
Connecting to eBuddy app - Nokia 301
Hi I am in Portugal trying to connect to ebuddy on Nokia301 but it keeps telling me no Java settings, How can I change this, is driving me mad I have searched everywhere, hope you can help I'm on vodafone pay as you go Moderator's Note: The subject w