search

google-code-export / zaplink

Automatically exported from code.google.com/p/zaplink
1 stars 0 forks source link

System Requirements for ZAPLink #137

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Hi,

Could you please document somewhere on the project page the SAP system releases 
on which your framework was succesfully tested.
I'm on release 702 and your framework almost works ;)
The information would save some time people who don't meet the minimum 
requirements.

Thanks!
--
Br,
Jacek

Original issue reported on code.google.com by jacek.ko...@gmail.com on 5 Oct 2012 at 10:55

GoogleCodeExporter commented 9 years ago 
Hi,

This information is on the file (.info.xml) in the release repository.
Where ABAP Version is  diplayed : 
SAP_ABA => SAPKA70104
SAP_BASIS => SAPKB70104
See file : 
http://code.google.com/p/zaplink/source/browse/ZAPLink%20FrameWork%20Basic/V0.0.
009-2011-12-12/ZAPLink.V0.0.009.info.xml?repo=releases

This is a good ideaµ. I'll try to do this, but at this point I do not have 
many return from users of ZapLink Framework. Let me know what is the trouble 
i've got.

For your information, Release 0.009 has trouble for installing. This will be 
fixed in the next release that is in install test on release 7.02 where adding 
module function failed.

Original comment by tar...@bensiali.net on 5 Oct 2012 at 11:02

GoogleCodeExporter commented 9 years ago 
First of all, it's good to hear that the project is still alive and thanks for 
providing this framework.

After 3-4 hours I finally manged to install ZAPLink Basic Framework V0.0.009 in 
SAPKA70207
SAPKB70207

I must admit that the installation process is not very user-friendly.
I'm afraid that many users won't use the framework as it's really but really 
hard to install. They will simply give up at some point.

Here are the problems that I faced:

Installer program:
1. Missing type ZAPLINK_SUBCOMPONENT_LEVEL on line 84 (known issue)
2. Missing type ZAPLINK_CX_IMPORT_NOT_ALLOWED on line 20110 (known issue)
3. Dump when calling line 21325: mac_add_mf_and_raise 
'RS_FUNCTIONMODULE_INSERT' 12.
In my system RS_FUNCTIONMODULE_INSERT has only 10 exceptions (not 12).

Activation:

1. CLAS objects should not be put into the worklist.

When I create a new class manually in SE24 the worklist doesn't contain CLAS 
entry e.g.:

CINC    ZCL_BASE======================CCDEF
CINC    ZCL_BASE======================CCIMP
CINC    ZCL_BASE======================CCMAC
CPRI    ZCL_BASE
CPRO    ZCL_BASE
CPUB    ZCL_BASE
METH    ZCL_BASE                      TEST

As you can see there's no entry for CLAS.
After running ZAPLink installer my worklist contained the following entries for 
class ZAPLINK_CHECKPOINTS_DATA:

CLAS    ZAPLINK_CHECKPOINTS_DATA <============ this entry shouldn't be here
CINC    ZAPLINK_CHECKPOINTS_DATA======CCDEF
CINC    ZAPLINK_CHECKPOINTS_DATA======CCIMP
CINC    ZAPLINK_CHECKPOINTS_DATA======CCMAC
CPRI    ZAPLINK_CHECKPOINTS_DATA
CPRO    ZAPLINK_CHECKPOINTS_DATA
CPUB    ZAPLINK_CHECKPOINTS_DATA
METH    ZAPLINK_CHECKPOINTS_DATA      CONV_ACTIVATION2MODE
METH    ZAPLINK_CHECKPOINTS_DATA      CONV_MODE2ACTIVATION

This leads to a locking problem during activation: Object 
ZAPLINK_CHECKPOINTS_DATA is being processed by user....". I had to manually 
deselect all CLAS entries.

2. Incorrect entries in the worklist (they don't require activation):
LIMU ACID ZAPLINK - error message TK103 when activating (below)
LIMU MSAG ZAPLINK - error message TK103 when activating (below)

Here TK103 message:
-------
The syntax of the transferred objects is incorrect. LIMU ACID ZAPLINK made this 
check.

This could be caused by the following:

The object type LIMU ACID is unknown
The syntax of the object name ZAPLINK is incorrect
The object is a component of a system object
-------

Let me know when you create a new installer for the framework. I'll test it in 
my system.

Br,
Jacek

Original comment by jacek.ko...@gmail.com on 5 Oct 2012 at 1:31

GoogleCodeExporter commented 9 years ago 
Point 1,2 & 3 are identified. Point 1 and 2 are solved and, as said, will be 
fixed in rel 0.0.010.
Point 3 is still investigating, because working fine on previous SAP releases 
we do not detect it.

For worklist problem this point wasn't a trouble in previous SAP version that 
why it haven't been detected. Now it's fixed in the next rel 0.0.010

Thanks for all this detailled informations. I'll provide beta installer and 
beta framework of rel 0.0.010 within 1 week.

Original comment by tar...@bensiali.net on 5 Oct 2012 at 4:18

GoogleCodeExporter commented 9 years ago 
Hi,

Please find Release 0.0.009a that include fixes for the activation process.
Could you please test it :
- Create Zaplink_Installer program
- Use Installer with Framework (you might need to import twice and re-import 
component that can't be actived)

Sorry for the delay but the change in ABAP compiler from 7.01 to 7.02 has 
create this issue and I'd like to fix it properly.

Let me know as quick as possible (I still has the issue in mind)

Thanks for this issue report and thanks in advance for your test

Original comment by Taryck.B...@gmail.com on 29 Nov 2012 at 5:06

Attachments:

GoogleCodeExporter commented 9 years ago 
Hi,

Thanks a lot for your work !

I am trying to install this version version V0.9a, when I lunch the program 
zaplink_framework, and modify the ok-code in the debuging mode, I get this dump 
: 

----------------------------------------------------
Short text
    An exception occurred that was not caught.

What happened?
    The exception 'ZAPLINK_CX_IMPORT_NOT_ALLOWED' was raised, but it was not caught
     anywhere along
    the call hierarchy.

    Since exceptions represent error situations and this error was not
    adequately responded to, the running ABAP program 'ZAPLINK_INSTALLER' has to be
    terminated.

----------------------------------------------------

Any idea ?

Regards,
Rachid

Original comment by afkkir on 20 Feb 2013 at 3:34

GoogleCodeExporter commented 9 years ago 
Hi, 
please open an new issue for the execpetion ZAPLINK_CX_IMPORT_NOT_ALLOWED
The reason is that the mandant is either productive or no change are allowed 
see transaction SCC4.

Original comment by tar...@bensiali.net on 21 Feb 2013 at 1:51

GoogleCodeExporter commented 9 years ago 
Issue 139 has been merged into this issue.

Original comment by tar...@bensiali.net on 26 Feb 2013 at 11:29