Hi,
I have created the custom form in screen painter.
I am opening the custom form by using foll code.
public void LoadFromXML
{
System.Xml.XmlDocument oXmlDoc = null;
string sPath = null;
oXmlDoc = new System.Xml.XmlDocument();
sPath = System.Windows.Forms.Application.StartupPath + "Form1.srf";
oXmlDoc.Load(sPath);
string sXML = oXmlDoc.InnerXml.ToString();
oApplication.LoadBatchActions(ref sXML);
}
But it is giving me error:
Form - already exists [66000-11]. Form Unique Id : 'Form1'
Hi
Steffi,
please how do you control the number range of the user that are created on the UI,
because on the UI we can fill any number.
EG
from the HR system the user is automated created 0001, 0002, 0003
when you create ID using the UI how do you know whats the emprty that the next ID (in this example 0004)
do you extact a report
Dear Chris,
I am using the latest version (10.4) and have no issues. If you run ALD standalone, do you still have the issue?
You can copy the complete XML source to notepad and save it as an xdp file. Re-open it with the standalone version and try if you still have the same issue.
If it still occurs, create a support call @ Adobe. That should be a ALD bug then. There might be patches for ALD on SAP marketplace as well...
Good luck!
Noel
PS. In notepad (or notepad++) you can remove the strange event codes and combine it together. But that can be tricky, so make a backup often!
Hi,
In current project delivery, other than standard case’s attributes, we has also developed some customised field which sit on different table than standard SCMG_T_CASE_ATTR.
One of the requirement is creating a linked object in the case detail. We have successfully established the linked object and
relationship, however when we try to use “Find” activity in the “Linked Object” screen it only bring the field from the standard table. How can we add-in our customised fields into this search functionality or alter the "Case Find" field search?
Please refer to the screenshot in the attachment.Pics 01, Accessing the linked object from Case Management transaction (SCASE). Pics 02, Case Find screen that we need to enhance.
The linked object is created using ELEMENT ID, derived from SCMG_SP_CASE. We are currently using SAP CRM 5.0; and transaction code: SCASE in the SAP GUI.
Assessment effort that we have done: We try to enhance class CL_SCMG_CASE_QUERY_WIN. It is not working, since SAP defaulted the search to standard table SCMG_T_CASE_ATTR.
Any advise is appreciated.
Thanks,
Eddy
Hi Julius,
This functionality, i.e. Alert Mails for only Red Alerts are available from SolMan 7.1 SP9, not before than that.
For lowere versions, if you want to enable this capability, you need to implement a BADi, but have not heard of any success stories around this BADi approach, so far.
So, please wait for SP9, as I am 
Thanks,
Hanfi
Hi Jaydeep,
Firstly, the data will definitely make the difference even if we go by u'r estimate of 10%.
Secondly, for performance, the SELECTs within a loop is a strict No untill and unless the requirement cannot be achieved without the above approach.
You could follow below steps to help maintainance and increase performance :
1. Populate whole data using SELECTs outside the loop. Do more of processing of internal tables according to your requirement of data.
2.Within the loop, u can use the below pseudo code approach :
Loop 1
Loop 2
Read statement internal table
Endloop.1
Endloop 2
3. Using above pseudo code, if no of records in Loop 2 > no of records in Loop 1 , then use Parallel cursor processing technique,
4. For SELECTs ( which u'll use outside the loop ) , plz make sure that the fields u r fetching are either primary key fields or they being used as indexes.
5. make use of ST12 for Optimizer analysis
If you still face performance issue, u can share u'r code and Trace analysis.
Thanks
Vivek
Hi Shankar,
One reason for your problem may be because the statement is not getting executed.
Check if entries are available in internal table gt_proj_guid.
if gt_proj_guid[] is not initial. "This checks if whole internal table is empty
SELECT * FROM dpr_task INTO TABLE gt_dpr_task
FOR ALL ENTRIES IN gt_proj_guid
WHERE guid = gt_proj_guid-guid.
endif.
Regards.
Hello Konstantin,
It worked. Thanks..
Br,
Shridhar.
This is resolved. Access to the file is not provided and that caused the issue.
Hi Vams, thank you for your reply.
I tried it, but the entity I obtain in the result object is initial.
I think that the Quotation Business Object is ERPOrder. Is it possible that this BO could receive the info from ECC system?
Here is my code:
lr_query = CL_CRM_BOL_QUERY_SERVICE=>get_instance( iv_query_name = 'ERPOrder' ).
WA_PARMS-NAME = 'VBELN'.
WA_PARMS-VALUE = <lv_value>.
Append WA_PARMS to IT_PARMS.
* Add the selection parameters
CALL METHOD LR_QUERY->SET_QUERY_PARAMETERS
EXPORTING
IT_PARAMETERS = IT_PARMS.
*Get the result list
LR_RESULT = LR_QUERY->GET_QUERY_RESULT( ).
*Get the first object(entity) in the result list
LR_ENTITY ?= LR_RESULT->GET_FIRST( ).
Thank you again.
Shifting a query from one space to another space requires Moderator Authority. Only the space specific moderators can shift the content to appropriate space.
My guess, initially, PM, QM might have also been covered under this same forum. Later stage, separate space might have been opened. But still many people don't have that awareness or because of their urgency, they may be posting in different space. Also new people for SCN can't understand the forum rules about exact space where they need to raise their thread.
Now PLM covers the process of R & D, Laboratory where new products will be developed & their life cycle activities.
http://wiki.sdn.sap.com/wiki/display/PLM/SAP+Product+Lifecycle+Management+(PLM)
In addition to above, total Product lifecycle includes Quality Management of that new product, Maintenance of those Laboratory Equipment, Material Master, Bill of Material for that Product, Project by which the R & D project can be handled, etc., It covers complete business processes of Procuring, R & D, Actual Production, Maintenance of Equipment, Quality Inspection for that Product, etc.,
So, it is not harm to open other topic related queries in this space, still we can use appropriate space to get more & better views.
Hi Dustin
SAP Lumira is not included in the BI 4.x (BI 4.0 or BI 4.1) Platform installation files. SAP Lumira is downloaded separately and installed on a user's pc/laptop as it is client software.
Regarding the license for SAP Lumira, it depends on how your BI 4.x platform is licensed, if you have the BI 4.x premium license, then SAP Lumira is included otherwise you have to buy a separate license for SAP Lumira. You'll have to check with your SAP Account representative as to which license you hold for BI 4.x and what is included in the license.
Depending on how the user id was setup on the BI 4.x platform either as a named or concurrent user, when connecting to the BI 4.x Platform from SAP Lumira, a seat will be consumed, so if your user id was setup as a concurrent user, then a concurrent seat will be used.
Regards
Derek
HI Praveen,
You can test that with BIC mapping designer tool, that you can deploy on PI 7.31 and use modules in file adapter to convert the 850 EDI to XML, BCI mapping designer comes as package with seeburger.
Thanks,
--Kishore
Hola Samara,
Mira aquí en los trainings gratis de SAP, seguro que te dan una buena idea:
http://scn.sap.com/docs/DOC-8514
Saludos,
Victor
Hi Suresh,
Though you have the sales order shown as full value, you can always edit to the vaue as required - Please check.
However, once your second sales order is created for 20,000 then the Sales Contract will have 60,000 as its remaining value (Sales Order 1 = 20,000 + SAles Order 2 = 20,000 -> = 40,0000). Once sales orders are created for 1,00,000 then you cannot create further sales orders.
Regards
Hi,
Document types are designed /created based on different procurement processes in an organization not based on company code.
In your case, you can create purchasing groups PGA for User A for company A, PGB for User B Company B and PGC for User C for company C.
Consult Basis Consultant and based on purchasing groups you can restrict creation of purchase order with purchase order document type by authorization with authorization object as following:
1. 1. Creation of purchase order for document type 1-3 for purchasing groups PGA with company A with help of authorization.
2. 2. Creation of purchase order for document type 4-6 for purchasing groups PGB with company B with help of authorization.
3. 3. Creation of purchase order for document type 7-9 for purchasing groups PGC with company C with help of authorization.
Regards,
Biju K
I have done this in my environment it is possible to accomplish.
So lets say by default the SMD installation wants to use DAA for your SID, I suggest you setup a DAB and point it at the other solution manager.
The only limitation is that you have to SMD agents and the memory foot print they leave on the system; which IMHO isn't large enough to be a huge concern.
I thought that at first, but then thought - if someone asked me what would happen in this situation, I wouldn't have known without writing the code. So I decided the question, while basic, was sufficiently interesting to let pass.
Moderation is always a subjective judgement call. I've no objection to newbies asking reasonable basic questions. It's the ones that are answered easily be searching or having had done BC400 that will get rejected.
Hi,
As Bijay explained a purchasing document is not configured at plant or company code level.
You need to understand what kind of data is existing at which level in the SAP system.
Purchasing document types are at the highest level and should represent the type of process that is used.
Same thing goes for the purchasing group so you are not able to restrict the selection options on these settings and the only thing that you can do is restrict access via authorization settings.
If a user selects the wrong document type and the system returns an error on saving the user can change the document type at that moment. It will not delete all the data, some data could be removed or needs to be changed based on the field selections that are set for each document type.
Only other solution is to create transaction variants to restrict the selections via these transaction variants.
Regards,
Peter
I take it you were looking for this: http://help.sap.com/saphelp_nw70ehp2/helpdata/en/49/23501ebf5a1902e10000000a42189c/frameset.htm
