on 03-16-2015 5:55 AM
Hello, Colleagues
This is Eunhwa Park. I am handling a ITSM function in Solution Manager. Especially, I am operating a Application Management Service.
So When requestor in customer side create a message in Solution Manager ITSM, I dispatch and process a message.
In this point, I have a question regarding SAP component. In standard SAP component, there are many componets.
However, customer don't know well to select SAP component. Maybe they know simple components. For example, FI(Finance). HR(Human resource) and so on. but if custmer have to select complex components, for example FI-AP-AP, they are confused to select a complex component. For this reason, I ran the report that component can be selectable. for example, FI, HR, FM and so on.
However, the background job which can get updated SAP component information from SAP backbone is running, the report which I ran is not applied to SAP component.
For these reasons, I want to make separate component which is not synchronized with standard SAP component. I mean, I want tto add a new separated component field in ITSM requestor's role.
In Processor's role, Processor can see two types of components field. One is SAP standard component and other is separate customized component.
Is it possible?
If it is possible, Please reply me.
Thanks in advance.
Best Regards,
Eunhwa Park
Hi Eunhwa,
in one ITSM solman I once had the same requirement. However, I decided to enhance the standard component list with custom values. I created a maintenance view similar to DSWP_CSNCOMP/TXT and wrote a short Z-report which downloads the SAP standard components and adds the Z-values afterwards. Users in requestor role bascially use the flat z-component structure (Z-FI. Z-HR, ...) to categorize the tickets. The processors can change the sap component if necessary (e.g. when forwarding to SAP). So, I also replaced the standard report of the SM:GET CSN COMPONENT job by the z-report in order to avoid the overwriting of the z-components by standard. There's also a standard customizing under ITSM in spro available.
The solution you're describing requires an enhancement of the CRM UI and furthermore knowledge in BSP processing/programming as you'll need an additional field which you have to link with ABAP logic.
Regards, RP
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
here's the table z_comp, the view is generated via utilities -> table maintenance generator
here's the code snippet:
DATA: langu | TYPE sy-langu, | |
ls_comp | TYPE z_comp, | |
lt_comp | TYPE STANDARD TABLE OF z_comp, | |
ls_dswp_csncomp | TYPE dswp_csncomp, | |
lt_dswp_csncomp | TYPE STANDARD TABLE OF dswp_csncomp, | |
ls_dswpcsncomptxt TYPE dswpcsncomptxt, | ||
timestamp | TYPE dswp_csncomp-timestamp, | |
sequence | TYPE dswp_csncomp-sequence. |
DELETE FROM DSWP_PARAM WHERE name = 'COMP_UPDTIME'.
COMMIT WORK AND WAIT.
DELETE FROM dswp_csncomp.
COMMIT WORK AND WAIT.
DELETE FROM dswpcsncomptxt.
COMMIT WORK AND WAIT.
langu = sy-langu.
CALL FUNCTION 'DSWP_GET_CSN_COMPONENTS'
EXPORTING
langu = langu. |
CLEAR: ls_dswp_csncomp, lt_dswp_csncomp.
SELECT * FROM dswp_csncomp INTO CORRESPONDING FIELDS OF TABLE lt_dswp_csncomp.
SORT lt_dswp_csncomp BY sequence DESCENDING.
READ TABLE lt_dswp_csncomp INTO ls_dswp_csncomp INDEX 1.
sequence = ls_dswp_csncomp-sequence.
timestamp = ls_dswp_csncomp-timestamp.
CLEAR: lt_comp, ls_comp.
SELECT * FROM z_comp INTO CORRESPONDING FIELDS OF TABLE lt_comp.
SORT lt_comp BY comp_level comp_id ASCENDING.
LOOP AT lt_comp INTO ls_comp.
sequence = sequence + 1.
CLEAR ls_dswp_csncomp.
ls_dswp_csncomp-comp_id = ls_comp-comp_id.
ls_dswp_csncomp-sequence = sequence.
ls_dswp_csncomp-comp_level = ls_comp-comp_level.
ls_dswp_csncomp-node_type = ls_comp-node_type.
ls_dswp_csncomp-selectable = ls_comp-selectable.
ls_dswp_csncomp-timestamp = timestamp.
INSERT INTO dswp_csncomp VALUES ls_dswp_csncomp.
COMMIT WORK AND WAIT.
CLEAR ls_dswp_csncomp.
ls_dswpcsncomptxt-spras = 'D'.
ls_dswpcsncomptxt-comp_id = ls_comp-comp_id.
ls_dswpcsncomptxt-comp_text = ls_comp-comp_text.
INSERT INTO dswpcsncomptxt VALUES ls_dswpcsncomptxt.
COMMIT WORK AND WAIT.
CLEAR ls_dswpcsncomptxt.
ENDLOOP.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.