Discussion successfully moved from SAP for Mobile to SAP Fiori as the more appropriate community for this topic.
Regards, Mike (Moderator)
SAP Technology RIG
Discussion successfully moved from SAP for Mobile to SAP Fiori as the more appropriate community for this topic.
Regards, Mike (Moderator)
SAP Technology RIG
Hi Pedro,
I guess SAPUI5 library version is old.
Please try SAP Fiori - UI Add-on SP12 notes list, SAPUI5 library 1.28.11.
Regards,
Masa / SAP Technology RIG
Hi All,
We need to hide the buttton Change and Approve button in UWL that button is available in backend aswell i was unable to find the ActionId of that button in Supported Action for this item.How to hide that button?
Please provide your inputs............
Regards,
Rahul.
Hi Martín,
Did you click on the back button or the black and white close button in the right corner?
Regards,
Andy
Hi Fred,
I am writing this in Root->AfterModify and also tried in a custom action event.
Also tried Opportunity.SegmentCombos;
The errors I see are
Error 41 [Activate] Root: Error in activation of runtime object \XBO_Opportunity-Root-Event-AfterModify.absl
Error 42 [Activate] Syntax error in generated ABAP method \XBO_Opportunity-Root-Event-AfterModify.absl
thanks
-M
HI,
SORRY.
I donot known "With BEx universe "result from another query" is disabled"
Two queries Prompt text is the same name is ok?
wang
Hi Ludek,
If we are going to use XI R2 on a Windows 2008 (32 bit) server. Would it solve my problem as below:-
SET objFactory = CREATEOBJECT("CrystalReports.ObjectFactory.2")
SET SESSION("objFactory") = objFactory
SET rptAppSession = objFactory.CREATEOBJECT("CrystalReports.ReportAppSession")
The problem happened on the line
SET rptAppSession = objFactory.CREATEOBJECT("CrystalReports.ReportAppSession").
Thanks a lot,
Vincent
Time wage types are generated in Time eval by the function GWT with one line for each applicable proc type in DZL table (in the time schema like TM00, TM04), using the config in V_T510S. This function GWT is inserted in the time schema after all necessary processing types have been formed in a time pair, so that you don't miss a proc type for this function.
They can be generated with ADDZL operation in a PCR.
POVT function generates OT wage types in ZML.
The time w/t's in ZML table are converted to DZL table entries before all time w/t's are output to the B2 cluster for an employee.
Examples of such time w/t's: Overtime, Shift penalty, etc.
The time w/t's contain w/t code, any pointer to costing/absence, hours, from/to, etc
P2001 function generates entries in AB table for each absence in time eval period.
In Payroll sub-schema XT00: the function DAYPR also invokes the time eval schema to perform this function; here this will evaluate if the PDC recalc date in IT 3 for an employee is prior to the current for-pay-period end date. Some small companies do the time eval this way only.
The function ZLIT imports the time w/t's from ZL table to IT table.
The function PAB generates w/t's for absences using AB table, based on config of V_T554C, etc.
Function P2010 processes IT 2010 entries to generate w/t's. IT 2010 may have a certain valuation criteria. It uses a PCR like X930 which evaluates these w/t's.
IT 416 is processed in P0416 function to generate leave compensation w/t's.
The PCRs like X015, X115 valuate the time w/t's.
All these valuations use operation VALBSx where x = 0, 1, 2 using valuation basis of a w/t in V_512W_B. Derived w/t is usually to create a subsequent w/t for reporting in payslip, etc. see link below. Do not pay attention to Philipines payroll reference here. This applies to all countries.
Technical Procedure for Wage Type Valuation using Valuation Base - Philippines - SAP Library
Statutory w/t's refer to such items used for
-tax calculated,
-superannuation or 401K, deduction,
-statutory net pay (based on minimum pay rules), etc.
Technical w/t's start with the character '/' (slash) - e.g., tax calculated, in-flow from previous retro period, etc. These are provided by SAP. While you can use such SAP provided w/t for reporting, it is recommended that users do not create such w/t's since they can not expect that SAP would not use one such w/t in future if they have not already used. Several medium to major support packs are known to introduce such new w/t's
SAP provides model w/t's starting with M, etc. They are configured with specific characteristics depending on the country code. They can be used to copy/create customer w/t's to reduce config effort. Again it would be better to copy/create from these w/t's rather than using them as they are.
Hope this helps.
Hi Mahesh,
Is that like a syntax error?
I mean there is an red or green line under elementsof?
Can you delete the ABSL and create a new one?
If the error is still happening, I think the problem would be in the extended node.
There is nothing wrong with your code.
Best Regards
Fred
Hi,
Yes. The deleted dimensions are 2 user defined dimensions and the added dimension is flow. I added back the old user defined dimensions and adjusted the template. And then removed the user defined dimension. But aftr login again to this new model, we are unable to edit any report/input form.
Use SU53 to trace the required authorizations, add them to the RFC user.
To have a WT end up in the RT, check it's Cumulation Classes 03, 20 and 41 (could be others also, depending on your Country Code and where its gets cumulated in your schema).
You can't have a WT in the Payslip until it is in the RT. Then, search discussion threads related to PaySlip or Remuneration Statement, and t-code pe51.
Hi,
All scheduled jobs can be found in SM37..
Scheduled jobs = Background jobs which can be found in SM37..
Maybe ask the BASIS for help on how to find the job which is running? Using the job in SM37 you can have an idea what type of job is it..
Regards,
Loed
By the way, regarding following SAP help link:
Sending E-Mails - Service Request Management - SAP Library
At the bottom of the help page, there is a feedback column. If you have any additional
feed back, you can input your thoughts and comments and even your email address
if you want SAP to get back to you.
Thank you for the spro node to get in to the evaluation group
Hi,
Maybe you did not do any changes so it was not saved? For example the auth user before is named AUTH_SAMPLE..Then you delete it and re-typed again with AUTH_SAMPLE..If you click the SAVE, that will be the message since no changes really has been done..
As Gajesh said, it is a mandatory field so you should be able to save it else an error will occur..
Regards,
Loed
Thank you for the detailed example which helped my assignment.
Kind regards,
Thank you
Hi, one question you resolved this problem? I am not able to download SAP Lumira Personal edition.
Regards
LEJS