loader
  • ASAP Methodology Documentation

    The SCN (SAP Community Network) is growing exponentially and it wont be too long before locating good tips/documents becomes as difficult as finding a good app on iTunes. (http://scn.sap.com/welcome)  If you have some links to great references please share them.

    Here is the latest piece of gold I have been using from SCN:

    Now in version 7.2 the ASAP Methodology for Implementation is a well refined and structured plumb-line for SAP projects and implementations, with which to measure themselves.

    You can access the entire ASAP methodology in MS excel which shows the phases and sub phases as well as the required resource roles, core subjects and project document template names from here:

    ASAP 7.2 Excel

    If you are looking for the descriptions of the phases as well as the standard project phase document templates you can access them from this hierarchy:

    ASAP Documentation

  • Monitor changes to a business object

    Do you want to be notified if a sales document has been changed?

    This may be activated simply by using a function within the “Services for object” icon. You can activate the services for Object icon with the user parameter “SD_SWU_ACTIVE” and the value “X“.

    You may then subscribe to changes to that object, by going into the sales document in change mode and selecting the icon in the top left and the menu path: My Objects–>Subscribe/Cancel Object.

    The result: Any modification to the order will result in a notification to your Business Workplace. (Transaction SBWP). This is a great tool for monitoring of sensitive sales documents.


    Thanks to user – Måns Nilback for this tip!

  • Pricing procedure performance improvement

    Often people think of price procedure optimization and performance improvement only when they are forced to. Here is one of the many methods to improve the speed of sales document processing specifically related to pricing.

     

    Activate the “Optimize accesses” functionality in the IMG. By using the following IMG path:

     

    SAP Customizing Implementation Guide–>Sales and Distribution–>Basic Functions–>Pricing–>Pricing Control–>Define Access Sequences–>Optimize accesses

     

    What does this do: This functionality will default an access step/s for the access sequence for a specific condition type. If no condition record is found for this access step/s, then the condition type will be ignored in the item processing of the pricing procedure.

     

    An example of how this may help you: Picture the scenario you have 100 items in a sales document. You have an item discount set for specific customer group only. If you use this pre-step optimization, you validate the customer group is a valid value for the condition record. Therefore the price procedure will use the item discount condition type. Alternatively if the pre-step optimization does not locate a valid condition record, for this header field value, it will ignore the multiple item calls to the condition type and its condition tables in the access sequence at item level in the price procedure. This is an even more optimised solution than using a condition type specific requirement in the pricing procedure.

     

    Run ECC6 and want a report to help you: See OSS Note 1423737

  • How do you change default partners in MASSD

    Issue: You have a default partner for example contact person for a range of customers. You need to find a method of extracting all those partners, selecting the correct partner to change and change the partner number.

    Solution: You could use an LSMW, a CATT, a batch input, or a custom program, but the easiest solution is to simply use “Mass change” – the transaction MASSD.

    Proceed as follows:

    TransactionMASSD

    Object:  KNA1-Customers

    Selection Options:

    • Customer Master Sales Data – KNVV – CustomerCustomer Master Sales Data – KNVV – Sales Org.Customer Master Sales Data – KNVV – Distr. Channel
    • Customer Master Sales Data – KNVV – Division
    • Customer Master Partner Functions – KNVP – Part.funct.
    • Customer Master Partner Functions – KNVP – Personnel No.

    Component to be changed:

    • Customer Master Partner Functions – KNVP – Default partner
    • Customer Master Partner Functions – KNVP – Personnel No.

    Screen navigation:

    • Change with display – this permits you to see the values (only really worthwhile doing if you have no more than +- 1000 records to change)
    • Set your new default values which will be applied to all records. (Note this is a mass change of default values not a variable value. For variable values use an LSMW)
    • Select the “Make changes” icon,
    • Save in the background. (you can go to SM37 to view the background job).
  • Language Issues and BW

    Do you have a worldwide or global SAP template that is being rolled out? Or do you have the need to cater for multiple languages within your SAP BW reporting model, ranging from western characters, through Cyrillic to Mandarin or Japanese Kanji?

    The solution you need to extract, import and load these language characters is much easier now with the use of Unicode, as opposed to individual code pages that systems and communications had to reply upon prior to release R/3 4.7

    As a solution, simply:

    a) Check your BW system and RFC connection to the source system uses Unicode. (right click on source system in RSA1, select change, and check special options tab.)

    b) Check your source RFC system uses Unicode. (simply press F5 from the above screen.)

    c) Ensure you have the parameter “ALL_CAPITAL” in transaction RSKC.

    d) Ensure you do not convert the text to upper case, that is mark your InfoObject in RSA1 as having lowercase letters on the general tab.

    Some tips:

    1) A simple explanation for d is simply that some characters do not have a representative upper case to convert to.  (I am sure there are more reasons).

    2) I have not found a requirement for other parameter values in RSKC, if you do find a reason, please share.

    3) If you are not using Unicode, your text will be language dependent either on the logon language of the user name in the extractor or the language associated with the InfoObject. Either way you will need a custom process or solution.  Do a search on MDMP (Multi Display Multi Programming) in SCN.

    4) Unicode currently supports more than 98000 characters with space for more than 1 million values.

    5) If you want to test unusual characters in your SAP systems and you do not have the appropriate keyboards simply enter “charmap.exe” in the Windows Start–>Run command.