Hi Mahesh,
I agree with Vengal B. The problem is not related to RSKC settings, it is a general check that the string should not start with an exclamation mark.
However, instead of editing the record in the PSA, I suggest to implement an add-on for cleansing character strings. Please read my blog Introducing an Add-on for Cleansing Character Strings where you can find all details for such an approach and a link to the document with implementation instructions.
Best regards,
Sander
Dinya,
You could use a cross tab to get the desired output.
-Sri Harsha
Amardip,
You will not be able to create a custom heirarchy in universe with the above client data unless you change it to meaningful hierarchical data as you displayed below.
-Sri Harsha
Ritesh, thanks
I think your shared what i was look... great help ,
will comeback to you after creating a case.
thx again
CR
I think JCo doesn't support table type import parameters which that RFC has. At least not in older versions that 12 would be using. I don't know if thats been addressed in later versions.
Regards,
Christian
There is no need to be sorry, 
About contacting SAP , I first recommend please check with your technical expert (ABAP) in team , he/she must be having fair idea on how to deal with it , they will have possible list of workaround and based upon there reply you can take decision weather or not its require to contact SAP.
Check below thread its similar to your issue.
how to increase field length of standard database tables..........?
You can close this thread and create a new thread in ABAP Development forum and give link to this thread, there you will get more favaorable replys on it.
Hope it may help you.
Thanks
Ritesh
Dear Krishna
answer is: No. I am not aware of any kind of document which your are looking for (may be something might be explained in the "Best Pratice" guides; I did not check them) As discussed in context of e.g. document Important compositions in EH&S and how they are used and corresponding threads (and other discussion in several threads created by you): SAP delivers something (e.g. authorization group "ALL") and you (as member of company using SAP EHS) checks the "default" customizing. If it is fine for you, you just use it; if not you add further entries etc. How you would like to use the default customizing (maintenance rules etc.) is decision of a company; some companies do have may be strict rules in use, some will have no rule etc.
To be precise: this statement is true for ALL default customizing (like REAL_SUB etc.); you use either what is delivered or you adapt the structure. I would assume that (based on many discussions in many threads in this FORUM) that 60% (may be) of companies just use the default customizing, and 40% add additiionl entries; but you will find discussions here by consultants which seems to have installed a "ZCAS" number rather than using "CAS" number as delivered (and this was done for e.g. whole property tree); this is clearly a quite "extreme" exampleto generate a "company data model".
C.B.
Zia
I have same problem. Did you fix your problem?
Thank Amol and Satish,
These are SDP DB alerts (=DP mainly).
This is a bit weird but it appears like Alerts are not deleted despite the deletion programs of all kinds that exist are run. I wish I could delete them at a table level using sledge hammer.
Anyway this issue got magically fixed when I imported a new alert profile with new selection ID's (same masala inside) from source. For double safety I erased all goddamn alert profiles in the target. Erased without a trace.
Let SAP own the burden of explaining this magic to tortured souls. I don't care. It is working now. So I will claim to have solved the problem worth no more attention than 1 hour or 100 dollars whichever is les
Do not tell this secret solution to anyone :-).
Thanks
Amit.
Hay tambien en SAP una configuración que bloquea los documentos con fecha anterior a la contabilizacion.
Revisa en Gestion -> Parametrizacion de Documentos -> General
la opcion se llama
Bloquear documentos con fecha de contabilización anterior, si tiene check es lo que esta impidiendo la contabilizacion
Saludos
Prueba Instalando el Add-In de integracion de Crystal Reports 2013, ese lo encuentras en la carpeta:
C:\Program Files (x86)\SAP\SAP Business One Server\B1_SHR\Crystal
o la correspondiente donde se encuentre la B1_SHR y de ahi en la subcarpeta Crystal
Saludos
Is it on your desktop? Which OS is in your Desktop?
Dear Tejender,
Have you got any resolution on this issue? I am getting the same exception.
Thanks,
Regards,
Tirupati
Hi Veedant,
Your are saying two different part but its not matching.
you are saying that leaves are deducting and again saying not proceed.
Which is not processing and what you would like to do in the system exactly, in the system what is currently configured.
Regards,Sankarsan
Hello,
Since I suppose this error is becaouse the ST_POINT is not supported I backed up the table and modified it.
With this change I was able to activate my odata service.
Kind Regards.
Hi Saar,
One last question.
Can you please guide me how we can achieve the same scenario from WDA application clicking a link navigate to TLN other tab of the same role in WDA
Thank you
Ambica
Hi,
I have a requirement where the quota should be generated until the remaining hrs in the quota has reached a X value. for. e.g 100 hrs. If the emp reaches 100 hrs, the entitlement should stop. If he utilises the entitlement and the remaining hrs are less than 100 hrs, the quota should be generated again till 100 hrs.
Also, the Seniority, Prorate rules are applicable while generating the quota.
We dont want to use the BADI for this. This should be achieved by a PCR.
Pls Help.
Praveen
Dear All,
My technical requirement are same as using blog feature : "PI REST Adapter - Consuming synchronous RESTful service".
Data format in Request/response is XML , no conversion.
The specific demand is , after PUT call i need to read the response message header data for further manipulation in my I flows.
the header information i need is HTTstatuscode, content type and private id etc. This information comes in Response header only , not in body .
Based on info i had from documents is that Rest adapter add some specific header info in XI header for response message flow.( Rest --> PI )
but what if need some header data which not given in XI header..? any receiver Rest channel config will help..? ( response determination)
will Java mapping + dynamic config will help to extract that header info..?
or atleast HTTP status code available in rest channel logs can be extracted for both success and failure..?
Warm regards,
Ashu
please give me the document for STC01/STC02
Thanks in advance
