Rights to modify sales employee on sales opportunities

Is there a way on sales opportunities to prevent users changing the sales employee field?
"Change sales employee" in general authorizations is working only for documents, but not for sales opportunities.
May it be done for example with a stored procedure comparing the actual and the previous value of the field before an update?

You may post it here in order to become a candidate for next B1 version:
/community [original link is broken]
Thanks,
Gordon

Similar Messages

Change sales employee authorization for sales opportunities

"Change sales employee" in general authorizations is working only for documents, but not for sales opportunities.
There should be an authorization alos for sales employee on sales opportunities.
Not only for itself but also to make a sense to authorization of sales employee on documents, because having full rights to sales employee on sales opportunities make easy to set sales employees on documents even if not authorized, just by adding the document from a sales opportunity from where it will inherit any sales employee.

Hi Sean,
Your request is very reasonable. I am supporting this DRQ. It would be better to be include in the new release soon.
What is your B1 version? Have you checked the latest version?
Thanks,
Gordon

Sales Opportunities

Hi
In one of client's company there are a few number of sales employees.And they handle diffrent products.After they capture the leads in sales opportunities,the sales employees from other product division should not access their opportunities.Is there a way to do this?
Regards
Louis

Hi Louis,
Data ownership is the option for you out of B1 box. However, you may find this function not good enough for you to completely block some other non-authorized users to view certain documents.
Try them first, if you are not satisfied with the result, you have to go through SDK or add-on to get what you want exactly.
Thanks,
Gordon

Sales Opportunities and Follow Up Activities

Hi Experts.
We have a customer who uses Sales Opportunities and Activities extensively.
What they are finding is that when they create a follow up Activity from an Activity linked to a Sales Opportunity, the fields Source Object Type and Source Object No. are not always populated with Sales Opportunity and the Sales Opportunity number. This data is showing on the original Activity.
Also, when you access Related Activities from the Sales Opportunity, the follow up Activity is not always show.
I would like to be able to send you some screen dumps of this.
Any suggestions?
Thanks for you time.
Julie Coppins

What is your B1 version and PL? It is probably a bug due to less demand to this function. Log a message to support team anyway to get their official answer.
Thanks,
Gordon

Modify Sales order Item additional tab B

I need to modify Sales order item additional tab B ...by removing the exisitng fields and should add some new fields ....which is ok. But does it have any impact becoz the same screen fields coulbe used in any of the other transaction .......i just wanted to know if we remove the fields from sale orde item additional tab B and some new details will have some impact

Hi,
Before making any modifications check "Where-used". If it is in some other program other than the VA01/02/03, then better consult your lead before modifying.
If you do not find, go ahead and make the changes confidently.
Regards,
Subramanian

Need to modify Sales order Item additional tab B

Hello all,
I need to modify Sales order item additional tab B ...by removing the exisitng fields and should add some new fields ....does it have any impact on this screen could be used in any of the other transaction .......i just wanted if we remove the fields and some new details will have some impact
Regards,
KK

Additional data B is used to add your own fields also known as custom fields in sales order.
Custom fields can be added to tables VBAK & VBAP (depending on header or item). Similarly you can remove fields if you don't require it anymore.
In short, your requirement can be met but you have to take help of ABAP consultant since it requires maintenance of user exits and modification of screens.

Issues with Sales Opportunities

Hello again!
Sorry to be a pest! I'm trying to put WebTools 2007 (628) through it's paces prior to training some of our staff in it's use for CRM purposes, and I've hit a few more snags, these in particular are related to Sales Opportunities.
1. Hitting the Refresh Button (F5) on Stages tab after adding a Stage duplicates that stage and can be repeated multiple times. In theory this creates stages that would not be possible in B1. This would also create a Synching issue because B1 wouldn't allow the overlapping stages.
2. "Associated Document Number" does not link to correct the sales document. For example a sales order in WT is totally a different BP, although it does appear correctly in B1. I know in the OPPR1 Table there is a docid (docentry) and docnum column, perhaps WT is synching on the wrong one, thus linking the wrong document.
3. Adding stages appear not to be Synching back to B1. The following error message occurs. Since the Close Date is not an exposed field in WT, there is no ability to go back to alter the close date of the prior stage before creating a new stage. Because of this there is no way to prevent the following Error:
-5002:Date deviates from permissible range [OPR1.OpenDate][line: 1]
at NetPoint.SynchSBO.WebToolsChildObjects.OpportunityStage.NetPointToSBO(NPQueueObject qData)
at NetPoint.SynchSBO.SynchObjectBase.Synch()
4. Adding/Deleting Stages which have a sales amount does not update the "Total Sale" Amount in the heard record as it would the Potential Amount on the B1 side.
5. Column headings are incorrect under Sales opportunity --> Stages. It shows "sale sPerson" and "Tota lSale" and each column is shifted over by one because the date column heading appears to be missing.
Thanks,
Jason Walters

Just checking to see if anyone has re-produced any of these issues...
Thanks!
Jason Walters

Update sales opportunities with DTW

Hi Experts,
I am trying to update sales opportunities with DTW but get the error below even with a file as simple as:
RecordKEy;SequentialNo;OpportunityName
RecordKEy;SequentialNo;OpportunityName
1;17803;Anything
2;17892;Anything
3;17894;Anything
The Reason of the error:
"CServiceData::VerifyPropertyWrite failed: Property 'SequentialNo' of 'SalesOpportunities' is read onlyoSalesOpportunities"
Do you have any idea what may be wrong?

Dear Martin Kamau,
By SDK help, the Source table of SalesOpportunities Object is OOPR, and SalesOpportunitiesLines is OPR1.
In B1 application Sales Opportunity form, you could check which field need to set for OOPR and OPR1, you could refer to SDK help file also.
Best Regards
Jane Jing
SAP Business One Forums team

Importing Sales Opportunities with DTW

Hello,
I am trying to import the sales opportunities with the DTW, but I keep on getting the following error
potential amount is missing [OPR1.MaxSumLoc][Line: 1][Application defined or Object- definederroroSalesOpportunities]
I am using SAP 2007A patch level 47.
I have the following one line that I have been testing with, after my previous inputs failed. Please assist.
RecordKey 1
CardCode L1004
ContactPerson 2
Dataownershipfield 14
SalesPerson 4
Date 20090419
Status sos_Open
TotalAmountLocal 100.00
Edited by: Martin Kamau on Apr 19, 2009 6:57 PM

Dear Martin Kamau,
By SDK help, the Source table of SalesOpportunities Object is OOPR, and SalesOpportunitiesLines is OPR1.
In B1 application Sales Opportunity form, you could check which field need to set for OOPR and OPR1, you could refer to SDK help file also.
Best Regards
Jane Jing
SAP Business One Forums team

How to Get SOAPElement BOM in SOAPMessage for Sales Opportunities

Hi experts,
I'm newbie in using Java.
I want to Update Sales Opportunities using SOAPMessage in Java.
So far, this is my sample code:
import javax.xml.namespace.QName;
import javax.xml.soap.MessageFactory;
import javax.xml.soap.SOAPBody;
import javax.xml.soap.SOAPConstants;
import javax.xml.soap.SOAPElement;
import javax.xml.soap.SOAPHeader;
import javax.xml.soap.SOAPMessage;
import javax.xml.ws.Dispatch;
import javax.xml.ws.Service;
import testws.salesopportunities.BOM;
import testws.util.MyHandler;
public void updateOppr() {
        Service service = Service.create(new QName("UpdateOpportunities"));
        QName portQName = new QName("UpdateOpportunities");
        QName elementbom = new QName("BOM");
        try {
            String endPoint = "http://192.168.56.102/B1WS/service.asmx";
            service.addPort(portQName, javax.xml.ws.soap.SOAPBinding.SOAP12HTTP_BINDING, endPoint);
            service.setHandlerResolver(new MyHandler());
            Dispatch<SOAPMessage> sourceDispatch = service.createDispatch(portQName, SOAPMessage.class, Service.Mode.MESSAGE);
            salesOpBOM = (new testws.salesopportunities.ObjectFactory()).createBOM();
            JAXBContext context = JAXBContext.newInstance(salesOpBOM.getClass().getPackage().getName());
            Marshaller marshaller = context.createMarshaller();
            SOAPMessage msg = MessageFactory.newInstance(SOAPConstants.SOAP_1_2_PROTOCOL).createMessage();
            // create header
            SOAPHeader header = msg.getSOAPHeader();
            SOAPElement elMsgHeader = header.addChildElement("MsgHeader", "", "http://www.sap.com/SBO/DIS");
            SOAPElement elSession = elMsgHeader.addChildElement("SessionID");
            elSession.addTextNode(sessionID);
            // create body
            SOAPBody body = msg.getSOAPBody();
            SOAPElement elCommand = body.addChildElement("UpdateObject", "", "http://www.sap.com/SBO/DIS");
            SOAPElement elBOM = elCommand.addChildElement("BOM");
            SOAPElement elBO = elBOM.addChildElement("BO");
            SOAPElement elAdmInfo = elBO.addChildElement("AdmInfo");
            SOAPElement elObj = elAdmInfo.addChildElement("Object");
            elObj.addTextNode("oSalesOpportunities");
            SOAPElement elQueryParam = elBO.addChildElement("QueryParams");
            SOAPElement elParam1 = elQueryParam.addChildElement("SequentialNo");
            elParam1.addTextNode("69");
            SOAPElement elslsOpLine1 = elBO.addChildElement("SalesOpportunitiesLines");
            SOAPElement elLineRow = elslsOpLine1.addChildElement("Row");
            elLineRow = elslsOpLine1.addChildElement("Row");
            elLineRow = elslsOpLine1.addChildElement("Row");
            SOAPElement elLineRowMaxTotal = elLineRow.addChildElement("MaxLocalTotal");
            SOAPElement elLineRowStageKey = elLineRow.addChildElement("StageKey");
            SOAPElement elLineRowStagePercent = elLineRow.addChildElement("PercentageRate");
            elLineRowStagePercent.addTextNode("85.00");
            elLineRowStageKey.addTextNode("5");
            elLineRowMaxTotal.addTextNode("1000000.00");
            marshaller.marshal(salesOpBOM, elCommand);
            msg.saveChanges();
            SOAPMessage response = sourceDispatch.invoke(msg);
            //End UpdateObject (Update Document / Add Document Lines)
        } catch (Exception ex) {
            ex.printStackTrace();
Edited by: Siddharta on Mar 4, 2011 10:31 AM

After I Debug this code, i get an error message (SOAP Request were trimmed):
Update sales opportunities
<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">
     <env:Header>
          <MsgHeader xmlns="http://www.sap.com/SBO/DIS">
               <SessionID>D8419D24-4E71-4D10-A425-1ADCCD6020C3</SessionID>
          </MsgHeader>
     </env:Header>
     <env:Body>
          <UpdateObject xmlns="http://www.sap.com/SBO/DIS">
               <BOM>
                    <BO>
                         <AdmInfo>
                              <Object>oSalesOpportunities</Object>
                         </AdmInfo>
                         <QueryParams>
                              <SequentialNo>69</SequentialNo>
                         </QueryParams>
                         <SalesOpportunitiesLines>
                              <Row/>
                              <Row/>
                              <Row>
                                   <MaxLocalTotal>1000000.00</MaxLocalTotal>
                                   <StageKey>5</StageKey>
                                   <PercentageRate>85.00</PercentageRate>
                              </Row>
                         </SalesOpportunitiesLines>
                    </BO>
               </BOM>
               <BOM xmlns="" xmlns:ns3="http://www.sap.com/SBO/DIS"/>
          </UpdateObject>
     </env:Body>
</env:Envelope>
javax.xml.ws.soap.SOAPFaultException: Invalid XML Stream
        at com.sun.xml.internal.ws.fault.SOAP12Fault.getProtocolException(SOAP12Fault.java:210)
        at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:111)
        at com.sun.xml.internal.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:176)
        at com.sun.xml.internal.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:195)
        at testws.Main.updateOppr(Main.java:173)
        at testws.Main.main(Main.java:43)
Why there is 2 SOAPElement for <BOM> ?
If my code is wrong, please can you help me?
Is there a way to get SOAPElement <BOM> in SOAPBody so i can update Sales Opportunities Document without addChildElement for <BOM>?
Thanks a lot.
Edited by: Siddharta on Mar 4, 2011 10:38 AM

Can we modify sales order line item before its booked through API?

can we modify sales order line item before its booked through process_order API?
here we have a situation where related item should be substituted for actual order item when user selects the related item , So looking for a way to modify the ordered item on sales order line .
Thanks,

Hi
There is an API to update the Related Item on the line level in the Sales Order.
PROCESS_ORDER API can be used for this purpose. It is part of OE_ORDER_PUB.
Below are the fields on line table type that will be assigned to create an order line with related item and original ordered item.
ORIGINAL_ORDERED_ITEM : Original Item
ORDERED_ITEM : Related Item
ITEM_RELATIONSHIP_TYPE : Type of Relationship.
Please go ahead and try to create it like this. I am pretty sure that it will get the order created with related items.
Note: Please make sure the profile option
OM: Enable Related Items
should be enabled.
Please mark the response as helpful or correct if it provides you the solution.
Thanks
Mirza Tanzeel

User exit to modify sales order pricing condition

Hi Experts,
I need ot modify Sales Order Header Condition (ZFRH), Condition Value (KWERT) for Transaction VA01 & VA02
I agree there are many user exits which will modify XKOMV-KWERT structure and can populate what ever value we insert.
But the value we insert is inserting into line item condition and the total of all line items is populating in Header .
I need to modify only Header condition without populating Line items
Thanks ,
Basheer .

Hi:
Program : MV45AFZZ
search for USEREXIT_NUMBER_RANGE.
BR,
Manthana

Sales Opportunities and Activities Import

We need to import the attached into SAP as Sales Opportunities and related Activities.
I believe the mappings are roughly as follows:
Opportunities
Source     Destination
SalesCode     OOPR.CardCode
Createdate     OOPR.StartDate
Description     OOPR.OpportunityName
Opportunity_Value     OPR1.MaxLocalTotal
Acct. Manager     OOPR.SalesPerson (id lookup)
Activities
Source     Destination
Contact Name     OCLG.ContactPer
SalesCode     OCLG.CardCode
Description     OCLG.CntctSbjct
Call Back Date     OCLG. CntctDate
What I canu2019t see is how to link the activity to an opportunity.
NB: Where there isnu2019t a contact name and call back date, there is no activity to be created.
Regards,
Juan

Hi Juan,
To link Sales Opportunities with Activities, you need to assign OCLG.parentType = 97 and OCLG.parentID=OOPR.OpprId
Thanks,
Gordon

Sales Opportunities Activity

Dear Experts,
Is it possible to upload an activity using DTW and link it to a sales opportunity?
Regards,
Jimit

Dear Jimit,
Yes. You may try oContact template for DTW activity. Then update your Sales Opportunities to link them.
Thanks,
Gordon

Sales opportunities (source) -- sales report (sales analysis) link, help!

Hello,
Should be a simple quetion but I just can't work it out, please help!
On our sales opportunities we record the source. Ie where we advertised to get that opp through the door.
On Sales Reports>Sales Analysis I can see the totals for the month and the gross profit.
What I'm trying to do is map the totals for the month and gross profit against the source. Ie to see which sources make us the money that keeps us going as a company
But I can't seem to find the links anywhere to do a custom query.
Can anyone help?
many thanks

Hi.......
You can get this link very easily......
Its there in standard report.
When you punch the Sales Opportunity and conclude the same by attaching the document reference like Sales Quotation or Sales Order or any sales Doc. After that if your refer any Opportunity report (Sales Opportunity--> Sales Opportunity Reports) then you have to select the document tick. It will give you the document wise opportunity status.
Hope this will help you.....
Regards,
Rahul

Rights to modify sales employee on sales opportunities

Similar Messages

Maybe you are looking for