Quantcast
Channel: SCN: Message List
Viewing all 8713 articles
Browse latest View live

Re: Context/Paths/Binding?

$
0
0

Hi Dennis,

 

Model looks like this:

 

{      "id":7,"company":"HECO","emp_last_name":"SAFETY DIVISION","emp_first_name":"","category":"EMERGENCY","department":"SERIOUS INJURIES","call_tree":"N/A","division":"N/A","group":"N/A","position":"N/A","last_updated":"2015-07-30T17:01:18.413-10:00","icl_phone_number":[        {          "id":7,"phone":"(808) 123-4567","type":1,"person":7,"icl_phone_type":{            "id":1,"type":"business"          }        }      ],"icl_attachments":[              ]    },{      "id":8,"company":"HECO","emp_last_name":"SAFETY DIVISION","emp_first_name":"","category":"EMERGENCY","department":"SERIOUS INJURIES","call_tree":"N/A","division":"N/A","group":"N/A","position":"N/A","last_updated":"2015-07-30T17:01:18.413-10:00","icl_phone_number":[        {          "id":8,"phone":"(808) 321-1231","type":1,"person":8,"icl_phone_type":{            "id":1,"type":"business"          }        }      ],"icl_attachments":[              ]    },{      "id":9,"company":"HECO","emp_last_name":"DOE","emp_first_name":"JOHN","category":"PERSON","department":"ITS","call_tree":"CC-ABC-3","division":"CC","group":"ABC","position":"N/A","last_updated":"2015-07-30T17:01:18.413-10:00","icl_phone_number":[        {          "id":9,"phone":"(808) 134-5792","type":1,"person":9,"icl_phone_type":{            "id":1,"type":"business"          }        },{          "id":234,"phone":"(808) 213-4657","type":2,"person":9,"icl_phone_type":{            "id":2,"type":"cell"          }        },{          "id":909,"phone":"(808) 234-","type":5,"person":9,"icl_phone_type":{            "id":5,"type":"residence"          }        }      ],"icl_attachments":[              ]    }

I have a master.controller that allows a person to be selected from list and navigates to detail view based on following:

 

     onListSelect: function(oEvent){         var oBindingContext = oEvent.getParameter("listItem").getBindingContext();          var viewId = oBindingContext.sPath;          viewId = viewId.replace(/\//g,"_");                    sap.ui.getCore().getEventBus().publish("nav", "to", {               viewName: "view.contactsDetail",               viewId: "Detail" + viewId,               data: {                   bindingContext: oBindingContext               }          });               },     

Detail view sets context like so:

 

    onBeforeFirstShow: function (oEvent) {        if (oEvent.data.bindingContext) {            this.getView().setBindingContext(oEvent.data.bindingContext);        }    },

The detail view is set to how it was defined above in the original post. Let me know if that clears things up.

 

Thanks!

DJ


Re: Not able to add roles SAP_BPT_ADMIN & SAP_BPT_USER

$
0
0

Hi Pankaj,

 

The role names are as follows:

SAP_BPT_GBT_ADMINISTRATION

SAP_BPT_GBT_EVERYONE

 

Regards/Gouda

Re: OT

$
0
0
  • These dates (Scheduled Dates) would appear once you Release the Order.

Re: Empty request is returning {"EntitySets":["infostore]}

$
0
0

HI Anthony,

 

I can see this query is not answered, hence I posted above.

 

 

Here are the details,

 

We also encountered the same problem. We are unable to publish Lumira components on BI platform using SAP Lumira. It's throwing an error as HDB05408.

 

We have tried sending an empty request to verify the url, http://localhost:6405/biprws/  it is returing the json {"EntitySets":["infostore]}.

 

We are unable to understand this message.

 

Regards

Nagabhushanam

Unable to import custom js in Component.js

$
0
0

Hi Folks,

 

I imported a WebIDE Fiori project in my eclipse workspace.

I need to import a custom .js file - stored in location WebContent > model > Config.js into the Component.js

 

I have declared the Config.js as -->  jQuery.sap.declare("namespace.Config");

 

In the Component.js - when I import the Config.js using jQuery.sap.require("namespace.Config");

     I keep getting the ReferenceError ... failed to load .. 'model' is undefined.

 

Is there any more declaration that needs to be done.

 

Regards,

Brian

Re: TAXBRA - Condição BXZF - Com alterar percentual da Condition Record

$
0
0

Obrigado pela ajuda, problema resolvido.

 

Verificamos que a condição ICZF estava sem registro de condição criado (100%) e que o cadastro de cliente estava com tax jurisdiction code incorreto.

Re: Infotype 0006-01 "start date" not getting defaulted

Re: Cannot Run Time Evaluation Error 20.

$
0
0

In IT 2011, is the clock out P20 locked?  Otherwise it should have been processed by P2011 function to pass on to TD20 or ZD20.


Re: Wrong values in EPM report

$
0
0

Hi Gerd,

 

Please check if you are you using a Dimension Member Formula to calculate value for account 31811401?

 

- Raj

Re: Not able to add roles SAP_BPT_ADMIN & SAP_BPT_USER

$
0
0

Hi Pankaj,

 

Authorizations for ArchiveLink are also contained in the following Basis roles:

●  SAP_BPT_ADMIN

●  SAP_BPT_USER

 

as per Roles for SAP ArchiveLink - ArchiveLink - SAP Library

 

Please try to add the above roles to your user and let us know if they have the same  authorizations for ArchiveLink as SAP_BC_SRV_ARL_USER and SAP_BC_SRV_ARL_ADMIN .

 

Regards

Arun

Re: Analityc - Key Figure for calculate number of days.

$
0
0

Updated: Sept 26, 2015

 

There a few techniques to achieve Aging reports (calculating duration between two time points) for Service scenarios.

 

Starting in 1508 there are some key enhancements to the main "Ticket" data source that will allow you to configure Aging reports.

 

In the Ticket data source you will find the following key figures:

 

Screen Shot 2015-09-26 at 8.35.46 AM.png

 

Notice that we include "Today" as a key figure. We included this key figure so you can create a custom calculated key figures where you can use "Today" - "Timepoint" to calculate a duration in Days. The Ticket has standard timepoints that represent specific time stamps that a ticket always goes through in this lifecycle sequence which mirrors the ticket status lifecycle:

 

1. Posted On (Reported On- when the issue is reported)

2. Created On (sometimes the ticket was created in an external system and via API/migration the ticket has a Created On date after the Reported On date)

3. Initial Review On (when the ticket is set to In Process status)

6. Completed On (when the ticket is set to Completed status)

7. Closed on (when the ticket is set to Closed status -> you can set a completed ticket to closed via the time based workflow engine to prevent any change to the ticket)

 

Anytime during the above lifecycle after a ticket is in process and prior to a completed ticket can go into:

 

a. Escalated "state" which the Escalated On timepoint is captured

b. Arrived On (when the technician has arrived on site and has captured an on site arrival time)

c. Resolved On (when the technician/agent has resolved the issue)

d. Changed On (when the ticket was last saved)

 

Today based age duration is usually relevant only for tickets that are not completed in closed status (you usually measure age for SLA compliance for tickets that are either in open or in process). Thus you will take an extra step to create a restricted key figure on the calculated key figure to only capture an Age duration for tickets in status in process or open to filter out tickets that are completed or closed.

 

All the above examples only work with duration calculations in days. C4C analytics can only calculate duration between Dates and Integers/Decimals. If you need to calculate age in minutes/seconds, you will need to do the following options:

 

Option 1: export the data into excel and use the timepoints to calculate the diff of Date/Time in excel

Option 2: use standard age key figures in seconds for a few standard duration scenarios such as

 

Total Time at Requestor (aggregate duration in seconds that a ticket is in customer action)

Total Time at Processor (aggregate duration in seconds that a ticket is in processor action)

 

For the standard durations that are in seconds, you can configure a custom key figure to calculate the duration in hours, days, etc... using simple math of Total Time at Processor (seconds) / 3600 = Total Time at Processor (hours)

 

Option 3: add Integer or Decimal fields to the Ticket, and using workflow engine field update rules to capture each timepoint as a UNIX EPOCH timestamp (these are counter based timestamps that increment from 1970 and beyond).

 

At a high level do the following

 

1. Add a decimal extension field to the BO (the decimal field is used to store a UNIX EPOCH time stamp)

2. Create a field update workflow rule that will populate this extension field the EPOCH Time in the extension field (This has been available since 1505 as a key user activity).

3. Add a calculated extension field if you want to calculate a duration between two decimal extension fields

4. Add key figures into analytics to do reporting

 

Then you can decide how to do durations. Duration can be calculated either in analytics (run an analytical report which will calculate duration when the report is run) or stored as a calculated field on the BO. The former is good for compliance/KPI reporting, such as give me distribution of tickets with a duration, counters on specific durations, etc... The later is good if you need to drive a workflow process from the duration (when the duration exceeds a threshold, then trigger a workflow to do something else)

 

To calculate duration in the BO as a calculated field, create a calculation rule where you subtract one decimal field from another field (similar to how you would do this in analytics).

Re: Analityc - Key Figure for calculate number of days.

$
0
0

sergio aguero

 

Look at my updated post. I think you can configure your requirement using the "Today" key figure and the standard date key figures in the "Tickets" data source. There are few more key figures and characteristics for all time points in the "Tickets with Timepoints" data source. Join the two data sources and you should have what you need to calculate age via C4C analytics and/or excel.

 

CC: Gowri Shankar V, Jeffry AntonioSuman Bandopadhyay

Re: Restrict Work order for a specific equipment category

$
0
0

Hello JK S,

 

Through AuthObject

While using the I_BEGRP AuthObject for your purpose (to represent Equipment Category) perhaps we will have to use the AuthorizGroup (BEGRU) field of Equipment master to represent the Equipment Category (EQTYP). Means whatever we are maintaining in Equipment Category we have to replicate in AuthorizGroup field. If you do not have any issues to sacrifice this field (BEGRU) for this purpose then you have the solution in standard. In my case under a single Equipment category, different AuthorizGroups were used for other purposes.  One such example just for knowledge sharing is hereIH01 Structure Customizing beyond I_INGRP AuthObject

 

Through enhancement

In case you have decided to go the enhancement way (which I always find convenient in the areas where direct Authorization Objects are unavailable. Please check about the referred exit IWO10033. I do not have it in my system (ECC6.0) and I remember after release ECC4.7, this has been replaced by BAdi IWO1_ORDER_BADI. So if you also do not find the exit, you can try this BAdi.

 

My recommendation if enhancement route is selected

Though the control comes at Order SAVE event, I prefer user-exit IWO10009. This code first checks the Equipment category of the Equipment on which the Order is being created and if it is not the one you allow for Order then it throws an error at Order SAVE.

 

Suppose your Equipment category is 'M' which is OK for Order, then the code to be put in the include ZXWOCU07 of the exit IWO10009 will be:

DATA: v_eqtyp TYPE equi-equnr.
CLEAR v_eqtyp.
SELECT SINGLE eqtyp FROM equi INTO v_eqtyp WHERE equnr = caufvd_imp-equnr.

IF v_eqtyp IS INITIAL.
   MESSAGE: 'Please fill Equipment field' TYPE 'E' DISPLAY LIKE 'I'.
ELSEIF v_eqtyp <> 'M'.
   MESSAGE: 'You can not create Order for EquipCtgy other than ''M''.' TYPE 'E' DISPLAY LIKE 'I'.
ENDIF.

 

This throws the following error when the Equipment category is not 'M'.

Capture.JPG

 

 

Lastly


@Sebastian:

Kindly correct me, in case I went wrong somewhere in the first part of my reply (Through AuthObject) and also what I told in the context of exit IWO10033.

@JK S :

  • Please do not get influenced by the length of a response received. Understand the content and then go by your own suitability.
  • In case you are going the user-exit way, the task for your ABAPer is very simple. He just puts the above code as suggested. Also it is very simple for him to extend the validity of Order creation for more Equipment Categories by making tiny changes in the code.

 

 

Regards & Good luck

KJogeswaraRao

Re: Data load issue

$
0
0

Hi Vijay,

 

In the last screen shot I observed that the background job has status "scheduled". Only background jobs with status "released" are going to run. Could this be the issue, the background job with status "scheduled" will not run? It could be an authorization issue.

 

Best regards,

Sander

Re: Custom fields in Task-List operations

$
0
0

I shall be closing the thread. We opted to handle the requirement using Z development where Task-list master will play a less significant role. Thanks Pete Atkin for adding a different dimension to address the requirement.


Re: Integration Webdynpro Interface with SAP BW DSO

$
0
0

Hi Pat,

 

You will need a DSO for Direct Update. It comes along with a set of APIs which can be found in SAP Help. You have to be careful if you are going into this direction, e.g. how to deal with locking?

 

I suggest as an alternative to consider Integrated Planning. It has out-of-the-box functionality for data input. You can make an input-ready BEx Query available for business user to input the data.

 

Best regards,

Sander

Re: dbcc checkstorage

$
0
0

It is the number of faults of that type reported for that table.

 

Among other things, this shows that a number of tables are affected.

Re: Activation of DSO data

$
0
0

Hi,

 

Although it is not completely clear to me what you mean by 6, 3, 5, I assume that you are talking about the number of background processes. It is indeed possible to define a higher number than 3 (default value). However, it will be dependent on the availability of free background processes at run-time.

Do you have any indication of bottlenecks in number of available background processes?

 

Best regards,

Sander

Re: How to eliminate # and not assigned from report level

$
0
0

Hi,

 

That's what happens when not all InfoCubes's dimensions are loaded in the same transformation. Two  entries are created in the cube, one coming from each flow, the non-loaded characteristics from DSO1 produce some Not Assigned characteristics and the non-loaded ones from DSO2 produce the other ones.

 

The solution is to load all the cube's characteristics on a single transformation.  You could choose DSO1 --> cube1 or DSO2 --> cube2 indistinctly.  The important thing is that some ABAP coding inside this transformation will be necessary to join DSO1's characteristics with DSO2's ones.  This way the cube will end up with a single entries with all their dimensions filled.  No more Not Assigned values will be there provided they aren't present from the DSO's.

 

Best regards,

Fernando

Re: Internatinalisation of SAP PM

$
0
0

Hello Renjith,

 

From functional point point of view, you need to understand at which level is the planning performed. It will help you in understanding if the new location (plant) needs to be configured as planning plant.

 

From configuration point of view, you will have to do the below basic settings in SPRO

 

1) Enterprise Structure -> Definition -> Plant Maintenance -> Maintain maintenance planning plant

2) Enterprise Structure -> Assignment -> Plant Maintenance -> Assign maintenance planning plant to maintenance plant

 

Apart from above mentioned setting, their are many other paramters which you will require to set in SPRO. Another important thing would be Order Type; if you intend to use the existing order type, then, you will have to extend the order for new maintenance plant else you can configure a new order type.

 

Cheers!!

Viewing all 8713 articles
Browse latest View live




Latest Images