Creation of Sales Activity type

Hi,
I am creating a new Sales activity type (say: ZEEE)
In SPRO I have defined this sales activity type but few fields are greyed out. I have to fill 'TextDetermProc' under TEXTS section and 'Partner det' under PARTNERS section but both are greyed out.
Can some one pls guide me how to fill these two fields?
Thanks and regards,
Pankaj Bist.

Hi Marcin,
Text determination Procedure and Partner determination procedure is already defined in BASIC FUNCTION.
But my problem is: how can i assign a particular text/partner determination procedure to my activity, as these two fields are GREYED-OUT in the sales activity creation screen.
Regards,
Pankaj Bist.

Similar Messages

  • Authorization need in Sales Activity Type

    An Account(Customer) moved to discarded (Sales Activity Type), can be brought back to Active, but only thr' Authorization of GM.
    How we can do it?
    This all about Real Estate - Where Sales Activity Type is Created. Sales Activity Types Can be -- New, Hot, Negotiation, Pending Brochure, Discard, Pending Decision, Sales Completed....etc
    There is Authorization for Partner Function in Sales Activity - For Change or Display Sales Activity. But it doesn't solve the problem.
    Client needs Authorization, by which anybody can be able to change the customer's Discard Activity Type (If he turns back, to buy the Villa again) to Other Type.
    Regards
    Veneet.

    There is an OSS [Note 818276 - Sales activity change: incorrect language for messages|https://service.sap.com/sap/support/notes/818276] that may help you to solve your problem.
    Regards

  • Immediate Transfer Order Creation not occuring for Sales Document Type

    Hello gurus,
    I have a situation where a transfer order is not being created immediately for a specific sales document type.
    Here is an example document flow of a desired scenario where the system is working:
    Sales document type:  ZOR
    >  Delivery type:  LF
    >  WMS transfer order
    The Item Category in this scenario is TAN.
    Here is an example of the document flow in the current scenario where the system is not working:
    Sales document type:  ZPRD
    > Delivery type:  LF
    The Item Category is also TAN in this scenario.  The only identifiable difference in these scenarios is the sales document type.  For the ZOR SaTY, a Transfer Order prints immediately once the delivery is created.  For the ZPRD SaTY, a Transfer Order needs to be manually created after delivery creation.
    Is there a configuration setting that is controlling this?  Any help would be greatly appreciated.

    Thank you very much for the link.  When I insert the WMTA output type in the delivery output header, the Transfer Order is automatically created.
    The problem I'm running into now is the configuration setting that controls this.  I thought I figured it out when going to this IMG path:
    SAP Customizing Implementation Guide  -->  Logistics Execution -->  Shipping -->  Basic Shipping Functions  -->  Output Control -->  Define Print Parameters Shipping
    When selecting the Delivery Note, the shipping point I was using was not configured in this location.  I added the shipping point into this transaction, saved, and created a new order & delivery.  However, the WMTA output type still was not automatically inserted into the delivery when saving.  Is there another location I should be looking to fix this so that when I enter an order with a particular Shipping Point, the WMTA output type automatically appears in the delivery?

  • Blocking creation of particular sales order type

    HI  ,
    I initially my sales order type was ZMF , so many sales order are open  , as of now I want to block the creation one new sales order of type ZMF,
    Please guide me

    Hi Sunaina,
    Simply go to the details of ur doc. type (i.e in Define Sales Doc. types in SPRO) & put "X" in the "Sales Document Block" field on the top right of the order type.
    This will block d usage of this particlar doc type.
    Hope it helps. Plz close the thread if answered.
    regards

  • Approved activity types per sales unit/organisation in 2009

    Hello and nice days between christmas and new year,
    I would like to see which activity types are approved for the different sales unit/organisation.
    There is the T-Code KP25 and KP26 to see the planned activity types but can I get a list of the planned activity types associated with the sales units?
    Thank you very much in advance,
      Vanessa

    Hi,
    Hi,
    The T-code-KE27-Run Periodic Valuation of Actual data is actually meant for actual data related postings for CO-PA. Periodic valuation makes it possible for you to select and valuate actual data which has already been posted to Profitability Analysis (CO-PA). It uses a valuation strategy defined especially for the point of valuation 02 (Periodic actual valuation). This function is available for the record types A (incoming sales orders) and F (billing data) as well as user-defined record types.
    Periodic valuation is useful, for example, if you posted line items to CO-PA at the beginning of the period using the standard cost of goods manufactured, and want to evaluate them again later using the most up-to-date costs or using the actual costs of goods manufactured determined in Material Ledger.
    The system posts the difference between the original values of the line item and the new values in a new, separate line item. If you perform periodic valuation more than once for a single line item, the system posts a new "difference" line item each time the values change.
    Once you have performed periodic valuation, you can display the new values in the information system.
    For valuation using material cost estimates, you can choose the alternative option of displaying the periodically calculated values separately from the original values. To do this, you need to define special value fields into which to store the values from periodic valuation.
    Only values that are calculated in CO-PA during valuation can be recalculated in periodic valuation. However, those quantities and values that are stored according to the same value field assignment found in SD pricing when transferred from sales orders and billing documents remain unchanged
    CKMLCP is not must for KE27.
    Revert for clarification.
    S.Subbiah.

  • User-Exit for Checking Customer and Sale order type in Sales Order Creation

    Hi Experts,
      While creating the Sales Order once i enter sold-to-party and enter line item, i have to check the customer against the sales order type.
    Please suggest me if any user-exit or enhancement or BADI available for it.
    Thanks & Regards,
    -VM

    Hi
    Follow the below steps to find out what all BADI's are called when you press any button in any transaction.
    1) Goto se24 (Display class cl_exithandler)
    2) Double click on the method GET_INSTANCE.
    3) Put a break point at Line no.25 (CASE sy-subrc).
    Now
    4) Execute SAP standard transaction
    5) Press the required button for which you need to write an exit logic, the execution will stop at the break point.
    6) Check the values of variable 'exit_name', it will give you the BADI name called at that time.
    7) This way you will find all the BADIs called on click of any button in any transaction.
    mark if helpful
    Regs,
    Tushar Mundlik

  • Regd creation of New Sales Order Type - Credit Memo Request

    Hello Gurus,
    I have created a New Sales Order Type as per the given requirements. This is a Credit Memo Request. I have done all that are needed from SD perspective.
    Can you please let me know what needs to be done from FI-CO perspective when a New Sales Order Type is created and this is a Credit Memo Request. If some one can let me know the customizations that needs to be done it will be very helpful for me.
    Thanks,
    SNK.

    Hi,
    As per my understanding, there is nothing to be required from FI-CO perspective, in case when you defined a document type in SD.
    During the sales order processing the SD-FI interface happenes for following activities
    1) Credit check (In case you use Credt management)
    2) Tax determination
    For more knowledge
    go through the link given below.
    http://www.sap-img.com/sap-sd/link-between-sap-sd-mm-and-fi.htm
    Hope it helps,
    Regards,
    MT

  • Automatic Billing Creation Through Sales Order Output Type

    I have requirement to create Automatic Billing document when Sales Order has been created.
    Any Suggestion.
    Regards
    Vijay Maurya

    Hi,
    it is not supported by standard SAP.in cash sales and rush orders, delivery will be created automatically because of the settings assigned in their respective sales document types.u please check VOV8 t-code.go to the details of BV(CS) and RO.there, Create Delivery field is there and shipping conditions should be 10.
    for ur requirement, u contact ur ABAPer and ask him to put one field like Create Billing Automatically in ur sales document..then it may be possible..
    hope it helps..
    regards..
    yogi..

  • Reg:  activity type creation

    hi,
    i have created secondary cost element with category 41(over-head rates).
    when i tried creating  an activity type i am gettin an error
    stating the cost element is not an allocation cost element of type'43' .

    Hi,
    Please select 43 overhead rates in activity type also.
    Thanks and regards,
    Ravi Vruddhula

  • Va01 creation of sales order

    Hi
    can i create sub screen  in creation of sales order item
    in user exit mv45afzz
    my requirement is when user click on any line item than than i need to call subscreen with some information
    pls guide me on this

    HI
    <b>
    Sales realated exits</b>
    SDTRM001 Reschedule schedule lines without a new ATP check
    V45A0001 Determine alternative materials for product selection
    V45A0002 Predefine sold-to party in sales document
    V45A0003 Collector for customer function modulpool MV45A
    V45A0004 Copy packing proposal
    V45E0001 Update the purchase order from the sales order
    V45E0002 Data transfer in procurement elements (PRreq., assembly)
    V45L0001 SD component supplier processing (customer enhancements)
    V45P0001 SD customer function for cross-company code sales
    V45S0001 Update sales document from configuration
    V45S0003 MRP-relevance for incomplete configuration
    V45S0004 Effectivity type in sales order
    V45W0001 SD Service Management: Forward Contract Data to Item
    V46H0001 SD Customer functions for resource-related billing
    V60F0001 SD Billing plan (customer enhancement) diff. to billing plan
    V46H0001 SD Customer functions for resource-related billing
    V45W0001 SD Service Management: Forward Contract Data to Item
    V45S0004 Effectivity type in sales order
    V45S0003 MRP-relevance for incomplete configuration
    V45S0001 Update sales document from configuration
    V45P0001 SD customer function for cross-company code sales
    V45L0001 SD component supplier processing (customer enhancements)
    V45E0002 Data transfer in procurement elements (PRreq., assembly)
    V45E0001 Update the purchase order from the sales order
    V45A0004 Copy packing proposal
    V45A0003 Collector for customer function modulpool MV45A
    V45A0002 Predefine sold-to party in sales document
    V45A0001 Determine alternative materials for product selection
    SDTRM001 Reschedule schedule lines without a new ATP check
    SDAPO001 Activating Sourcing Subitem Quantity Propagation
    https://www.sdn.sap.com/irj/sdn/wiki
    Check this link
    Sail

  • Assign sales order type to Sales Area

    Hello everybody,
    I am trying to assign a sales order type to my sales area, and i have an error : the system tells me that my sales area is not defined. What can i do?
    I already defined my sales area, and i can see it in IMG->Entreprise Structure->Assignment->Sales and Distribution->Set up Sales Area.
    whwn i try to assign my sales order type to the predifined Sales Area it works. what am I supposed to do to be able to assign a document type to my sales area.
    Thank you in advance,
    Silvia

    <b>1.</b> Defining Common Distribution Channels for Master Data
    Use
    The purpose of this activity is to define distribution channels which have common master data..
    Procedure
    Access the activity using one of the following navigation options:
    IMG Menu -> Sales and Distribution -> Master Data -> Define Common Distribution Channels
    Transaction Code: VOR1
    <b>2.</b> Defining Common Divisions for Master DataUse
    The purpose of this activity is to define distribution channels which have common master data..
    Procedure
    Access the activity using one of the following navigation options:
    IMG Menu -> Sales and Distribution -> Master Data -> Define Common Division
    Transaction Code: VOR2
    <b>3.</b> Assign Sales Area To Sales Document Types:
    <b>A.</b><u><i><b> Combine sales organizations / Combine distribution channels / Combine divisions: Ensure to maintain these, else Sales Order creation will give error.</b></i></u><b>B.</b> Assign sales order types permitted for sales areas: Assign only required Sales Order Types to required Sales Area. This will minimize selection of Sales Order Type as per sales area.
    Check the above configuration. It should resolve the error once it is maintained appropriately.
    Regards,
    Rajesh Banka
    Reward points if helpful.

  • No commitment Item Update while creation of Sales order

    hi,
    I have  maintained Derivation Rule
    Co Code / GL/ BA/ Plant / S Loc/ = Fund / Comitement / Fund Center.
    Stil in that case at the time of creation of Sales order, systeme is giving error (++No commitment Item Update M V2225++)
    And also i have maintained the Comitement Item in GL master.
    Could you give me some solution.
    Thanks
    Nilesh R

    Hi Nilesh R,
    Please check the following information of Consulting Note 1268001 (the same for funds center is valid to commitment item):
    1.  You receive the error message in a Sales Order (SD) process.
       a) SD customizing settings for FM objects.
       You can set "commitment item" as an optional entry in SD customizing settings for field status. This can be checked in the IMG path: SPRO -> Public Sector Management -> Funds Management Government-> Actual and Commitment Update/Integration -> Integration ->
       Maintain Field Status for Assigning FM Account Assignments
       You should have a record with Object type = '04' (sales order).
       It is not necessary to have the field as required (unless you want to insert it in the origin process) due to the fact that
       this can avoid the account assignment derivation between CO objects and FM objects. The field can not be hidden otherwise it will be not derived.
       For more information, check note 572729.
    The system response depends on how you defined the fields of the FM dialog box using Customizing activity 'Maintain Field Status for Assigning FM Account Assignments':
         -  The fields of the FM dialog box are defined as ready for input ('Opt. entry' or 'Req. entry') in Customizing:
            If you change the reference object in the sales order, the system does not re-derive FM data automatically. For that, you
            must navigate to the FM dialog box and, by choosing icon 'Redetermine account (F5)', trigger the derivation manually.
         -   The fields of the FM dialog box are defined as not changeable ('Display') in Customizing:
             If the reference object is changed in the order, FM data is redetermined automatically.
         -  The fields of the FM dialog box are defined as not displayable ('Hide') in Customizing:
             FM data is not determined.
    Therefore, set the field status to optional permit the user to enter the FM objects manually and still benefit from the possibility to
    automatically derive the FM objects from a CO object.
    For more information on integrating Plant Maintenance, Sales and Distribution and Project System, see the SAP Library Accounting -> Public Sector Management -> Funds Management -> Actual and Commitment Update -> Integration with Plant Maintenance, Integration with Sales and Distribution and Integration with Project System (Network).
    You can also check the documentation available in the IMG menu of the status (written above).
       b) If you do not want to integrate sales order process within PSM-FM, you should consider to deactivate this integration in
          customizing transaction OFUP. In release EA-PS 1.10 and 2.00 modification note 591573 is available.
    Please also check consulting note 1267998 and let me know if you have used FMDERIVE trace tool.
    If you want to have SD integrated to FM, please check if in OFUP the flag of this integration is accordingly set.
    If you work with free-of-charge sales order line items mixed with line items having value, please consider to apply note 1441847 (if it is valid to your current release/package).
    I hope this answer your inquiry.
    Best Regards,
    Vanessa Barth.

  • Preventing update to COPA tables for a particular Sales order type

    Hi ,
    We need to have incoming sales order transfer to COPA activated only for one particular sales order type activated.
    Earlier we implemented note 571697  for user exit to allow COPA update only for particular sales order type.
    This prevented the transfer of SO to actuals table, but off late the performance for VA01 and VA02 has decreased substantially.
    Upon checking, we found this is happening because of other CE4XXXX tables (excluding CE1XXXX) which are getting updated during creation/ change of SO. as the data in these tables is huge .
    If possible, please advise, right userexit to prevent update to these tables.
    Thanks.
    Neeraj

    Thanks for your inputs..I have few more queries on same.
    Initially we had incoming sales order activated in KEKF allong with implemented SAP note 571697, which helped us to update CE1XXXX only for a particular sales order type. This was initial requirement to have system updating COPA values only for one particular sales order type.Also, KEQ3 was also activated which resulted in updates to CE4XXXX. This was not a problem initially since we had few sales orders now that plant has grown old with more sales order (resulting in huge size of CE4XXXX) VA01 is impacted..
    Currently ,since we have KEQ3 activated so, Segment is created the moment we create sales order.. and table CE4XXXX is updated..
    As most of you have suggested to switch off sales order in KEQ3, i need to analyze the impact of this..
    From what i understand CE1XXXX will continue with updation for that order type... and CE4XXXX won't be updated in future..Please correct me if i am wrong..
    Also, please advise what all can be possible impacts on COPA reporting if I switch off from now onwards (client has been using this since long) , and what all should be the precautions that i should take while doing this.
    Thanks

  • How to block sales order creating manually for a sales order type

    Hi SD gurus,
    My client wants for EDI orde type, the sales order should not be processed manually
    how can i restrict this. I know to i can restrict this by not giving authorization
    I want globally to maintain this.
    thanks

    Hi.
    I think that the best way to do this is to create a field exit to data element AUART.
    You will need an ABAP'er to create this field exit and associate the field exit to program SAPMV45A.
    Doing this, you need create a customized table to maintain the sales order type permitted to manual creation.
    You can use the program RSMODPRF to see all active field exits.
    I believe that EDI orders in your process are created through BAPI, correct?
    Waiting for response.
    regards.

  • HOW TO CONTROL ON CREATION OF SALES ORDER WITH REFERENCE TO EARLIER SO?

    Dear All,
    I want to contol on creation of Sales order with reference to earlier SO?  While creation of sales order our enduser are creating sales order with reference to earlier month SO which I want to restrict. Recently I made changes in sales order like payment terms is grayed, system will atomatically pick pay terms from customer master.Now I am getting correct data also but enduser is using old SO no while creating new SO and old payment data is reflecting in fbl5n.
    I want to restrict enduser while creating new SO with ref. to old SO. Only for returns they should be able to use Billing refrence. Pl. suggest how to control the with reference to ealier SO.
    Nikhil

    Nikhil Deshpande,
          If you dont want allow create a sales order in referent to other one, just delete the copy control between these sales order type, so when the user tries to create a SO in reference to other one a message is displayed that is not possible.
    Thanks,
    Mariano.

Maybe you are looking for

  • Signatures created in Acrobat X, using Acrobat reader

    I've created a form in Acrobat X with no security and all of the restrictions allowed and saved the document as a "reader extended PDF", "enable forms fill-in & save in adobe reader", but when I open it in reader, it won't allow me to do signatures.

  • 30 inch vs unknown 2009

    Hello there, I always wanted to have an 30 inch apple display. Love that thing... Now that i have found a two month used one, in good conditions i am afraid of byuing it. Mostly because i don't know if there are going to be new cinema displays on 200

  • Problem with imported movies from Sony Cyber Shot

    Hello all, I have an unusal problem. My mate has got a brand new sony cybershot camera which does movies. These movies import into iPhoto no problem with sound. However if I then use that clip in iMovie there is no sound, it does not matter how I try

  • Regex in WhlFiltAppWrap_HTTPS

    I want to replace some HTML code from SharePoint 2010 pages. Two sample lines I want to replace: <ie:menuitem id="zz25_ID_Logout" type="option" menuGroupId="200" description="Logout of this site." text="Sign Out" onMenuClick="STSNavigate2(event,'/_la

  • 'PDF only scenario' in WDA application

    Hi , experts, does anyone have any experience with the so called 'PDF only scenario' mentioned in note: 0000992492  Termination when using the PDF-only scenario  0000992493  Error in PDF-only scenario after importing Support Pkg 10  The note enables