Get images? can you explain more....
Limits are typically limited by system resources but there may be either a 256 or 512 limit. But maybe not. You can always add more UFL's if you do run into a limit.
See if this sample works for you, ther is a C++ plus a COM UFL sample attached to the KBA.
https://i7p.wdf.sap.corp/sap/support/notes/1603381
Don
Yeah, I didn't notice as I am doing resend to FU EH from FO EH. Let me see if I can find a solution for this scenario.
Thanks,
Vishnu
Hi Baithi, how are you?
Please help me with the following question, and I have completed all the steps to connect a system to GRC Legacy 5.3
- Define cross-application SoD ruleset
- Legacy data mapping
- Build ruleset files
- Uploading the ruleset
- Generating the ruleset
- Data extractions
- Extraction files from legacy and other non-SAP applications for User, Role, Profile, and Authorization Sync
Now I'm doing the migration to GRC 10.1 and connectors was defined as Local File not know how to create them in GRC 10.1.
This is de connector in GRC 5.3:
I see that in your answer as you indicate, but I wonder if I can expand the information of the following:
Create a connector as file type(Maintain the Source Connector type and the Logical Port with same name.
Integration in the authorization management (File system for legacy extraction)
Create two file paths: the first one for user, and the second one for user - action
Assign physical path to a logical path (transaction FILE) and indicate the route where the files of extraction data is located.
Thanks for your help.
Regards.
Natalia
C4C supports both helpdesk (employee facing) and customer service service processes. It is a generic scenario where you can manage service tickets for employees, just like you can for end customers. The helpdesk process does not have any out-of-box integration to SolMan or Incident Management nor is there any future plan to do so. C4C does include oData REST apis so via consulting sure you can figure out how to push tickets into C4C as well as pull them out via simple API based integration.
Hello Pavan,
I checked the transaction SM58 in ECC and I found the following error :
The question now is... From where this issue is coming? Wrong settings in the ECC Partner profile?
Thanks for your support!
Kr,
JP
Hi All,
We have implemented the Note 2208461 successfully. We have done the pre-implementation steps for the note 2211080 as well but the while doing the post implementation of this note, our Basis Consultant was unable to import the zip files SYST and CUST files provided by SAP. Please see the below screenshot from the t-code STMS_IMPORT in our sandbox system which is currently on EHP7 and release 604 with Sub component level 75.
Any suggestions?
Also, wanted to know what are the master data requirements for this ACA reporting solution from SAP.
Regards,
Satish
Sorry for responding late. But this worked for me. Thanks a lot Amit!
Marco,
As Eduardo said, I also believe that is not possible through customizing.
In my view, if you set up any field as mandatory for tcode MI01 through customizing, you'll impact the Sessions (MI31, MI32, MI33, ...), due to the fact that all of them use MI01 to process the batch input session.
One example is that the field ISEG-GRUND is not avaliable in the MI01.
You should try even SHD0.
Regards,
Fabio
Yes. Execute is enough.
I just assigned more privileges to the first in order to compare which one was referring to the design time and runtime versions.
Thanks!
Hi Chaitanya
if you have sap EWM system, check del and check which warehouse process type is there.
go to customization find cross process setting then go to warehouse task and then find your wpt and then check storage control. and go to pOSC and find step for same sc>>
Regards
Suraj
Hi Pieter,
For doing the ALTER TABLE DROP, do you have the database option "select into" set or are you using the "full logging for alter table" setting?
In general, I think you are probably right that much of the growth in the log has to do with the compiled objects. The ALTER TABLE would mark those objects to be renormalized (and thus then recompiled) the first time they are executed. The compilation (creation of a new query plan in procedure cache) does not grow the log, but the renormalization does rewrite the query tree stored in sysprocedures, which involves (on a 2k page size server, anyway) about 2K of log for each row in sysprocedures for the object. There can be a surprising number of such rows, something as simple as "create procedure p select c1, c2 from t1" produces 7 rows.
(sysprocedures rows are wider than they look, they have a hidden column that contains the query tree in binary form).
These log records would be generated as each object is executed for the first time after the alter, so that probably generates a lot of activity very quickly, then trails off.
Each of these would be separate transactions, so it should be generally possible to do a DUMP TRANSACTION to truncate the log after the ALTER (and perhaps some of the more immediate activity) has finished.
Here is a little demonstration:
Thats the first thing I tried many months ago.
Nothing in SU53.
Which isn't surprising really as there is no errors. The projects simply don't show up in the search.
1> create table t1 (c1 int, c2 int)
2> go
1> insert t1 select id, id from sysobjects
2> go
(32 rows affected)
1> create procedure p as select c1 from t1
2> go
1> dump tran test with truncate_only
2> go
1> select count(*) from syslogs
2> go
-----------
20
(1 row affected)
1> alter table t1 drop c2
2> go
(32 rows affected)
1> select count(*) from syslogs
2> go
-----------
79
(1 row affected)
1> execute p
2> go
c1
-----------
1
2
[snip]
752002679
(32 rows affected)
(return status = 0)
1> select count(*) from syslogs
2> go
-----------
110 <---- execution of p grew the log by 41 records due to rewriting the query tree
(1 row affected)
Hi Experts,
We have SAP ECC6 EHP7 system on windows, we have planed to integrate with SAP C4C, Can you please provide complete guidance and cost effect.
If it is available for trail let me know.
Thanks in Advance
Jana
Hello,
I have poured through the discussions and have not found an answer to this particular question.
What I want to do is in a Function Module, is build a structure of a SAP table based on the table name pass to the function module. I do not want to pass back a table nor XML. Just EXPORT the structure like if you were defining the parameter in the Function Module with an Associated Type.
Can someone help me?
Regards, Dean.
Hello Kenneth,
If that can be accessed through ODBC then maybe another option is to use SDA + Generic ODBC adapter to access remote data within HANA.
BRs,
Lucas de Oliveira
Compañeros, los consulto con la intención de que me compartan su conocimiento respecto al reporte: "Diferencias de tipo de cambio".
La verdad es que nunca lo he ejecutado y no tengo un panorama claro sobre para que sirve, en que ocasiones se ejecuta, que parámetros hay que utilizar, etcétera.
Estaré muy agradecido con sus opiniones y experiencias.
Gracias.
Look at the standard SAP help for putaway strategy P, Bin section related information is already supplied there with an example
http://help.sap.com/saphelp_470/helpdata/en/c6/f844c44afa11d182b90000e829fbfe/content.htm
Hello Matthias,
HANA Data Size and Performance is a very subjective. If it were something related to HANA One performance we could go into further details.
Have to recommend to explore more help.sap/com/HANA. Specifically Performance and Analysis Guide.
thanks,
dhruman
Hi Piyush,
InfoObjects and other targets are the same in 3.x and in 7.x. What varies between versions is
1) The way Datasources metadata is replicated to BW
Datasources are the same on the source system (that is: on ECC there isn't a 3.x vs. 7.x. distinction). It's at BW where the datasource metadata is replicated either as 3.x (ISFS object type) or as 7.x (RSDS object type)
2) The type of flow for loading data (3.x or 7.x)
Try the following
1. Delete your current BW's DataSource 3.x (ISFS) replica. Flow to 0VENDOR will be automatically deleted.
2. Replicate 0VENDOR_ATTR's application component metadata again. "Metadata replication" pops up. Accept and in "DataSource modifications" window deselect all datasources but 0VENDOR_ATTR so that only this DS is created (replicated). Verify objects' type is RSDS.
3. If DS succesfully replicates to BW as RSDS, all that is left to do is connect the DS to 0MATERIAL with a "common" 7.x transformation, create DTP, etc. You will no longer need 3.x flows.
I hope this helps solving your problem
Fernando
