Wednesday, February 1, 2012

0

SAP Business Workflow Configuration Tips

  • Wednesday, February 1, 2012
  • abhi
  • 1.1   Workflow

    1.1.1  Maintaining Standard Settings for SAP Business Workflow

    Use
    This activity will maintain Workflow standard settings automatically. Checks are also performed to establish whether Customizing is complete with regard to further important settings.
    Procedure
    1.     Access the activity using one of the following navigation options:
    IMG Menu
    SAP NetWeaver ® SAP Web Application Server ® Business Management ® SAP Business Workflow à Maintain Standard Settings
    Transaction Code
    SWU3

    2.     On the Automatic Workflow Customizing screen, choose the Perform Automatic Workflow Customizing (F9) button (red and white circular button).

    1.1.2  Trigger Workflow Events via Change Documents

    Use
    This activity will enable the trigger of workflow events according to changes of the document status. For this purpose, change documents are used to uniquely identify changes. The change documents itself track and trace changes to fulfill legal requirements. In this scenario, this reflects changes to the business object for documents.
    Procedure
    1.     Access the activity using one of the following navigation options:
    SAP Menu
    Tools ® ABAP-Workbench ® Overview ® Development ® SAP Business Workflow ® Definition tools ® Events ® Event creation ® Change documents ® Linkage
    Transaction Code
    SWEC

    2.     On the Change View: "Events for change document": Overview screen, choose New Entries.
    3.     On the New entries: Details of Added Entries screen, enter the following values into the corresponding fields:
    Field
    Value
    Change document object
    DOKUMENT
    Object Category
    BOR Object Type
    Object Type
    DRAW
    Event
    CHANGE
    Trigger Event
    Select "on change"

    1.1.3  Creating Type Linkage

    Use
    This activity will create the type linkages. The type linkage describes the assignment of a receiver function module and a receiver type to a particular combination of object type and event.
    Procedure
    1.     Access the activity using one of the following navigation options:
    SAP Menu
    Tools ® ABAP-Workbench ® Overview ® Development ® SAP Business Workflow ® Definition tools ® Events ® Event linkages ® Type Linkages
    Transaction Code
    SWETYPV

    2.     On the Change View "Event Type Linkages": Overview screen, choose New Entries.
    3.     Enter the following values into the corresponding fields:
    Field
    Value
    Object Category
    BOR Object Type
    Object Type
    DRAW
    Event
    CHANGED
    Receiver Type
    WS90300001
    Receiver Call
    Function Module
    Receiver Function Module        


    Linkage Activated
    Yes
    Behavior Upon Error Feedback
    System default
    Receiver Status
    No errors

    4.     Enter the following values into the corresponding fields:
    Field
    Value
    Object Category
    BOR Object Type
    Object Type
    ECO
    Event
    TO_CHECK
    Receiver Type
    WS90300002
    Receiver Call
    Function Module
    Receiver Function Module        

    Linkage Activated
    Yes
    Behavior Upon Error Feedback
    System default
    Receiver Status
    No errors
    5.      
    6.     Choose Save.
    7.     Choose Back.
    8.     Save and go back.

    1.1.4  Maintaining Agent Assignment

    Use
    This activity will define the following tasks as a general task:
    ID
    Task
    Workflow
    TS90300002
    Find Approver of Workflow
    WS90300001
    TS90300005
    Send Mail to Approver
    WS90300001
    TS90300004
    Save Approver Text
    WS90300001
    TS90300008
    Send Approval Mail
    WS90300001
    TS90300007
    Send Rejection Mail
    WS90300001
    TS90300003
    Change Status of the Document
    WS90300001
    TS90300006
    Check If all reviewers approved
    WS90300001
    TS90300010
    Find ECO Approvers
    WS90300002
    TS90300011
    Changing status of ECO document
    WS90300002
    TS90300013
    Mail after approving Document
    WS90300002
    TS90300012
    Rejection Mail after rejecting document
    WS90300002
    TS90300009
    User Decision
    WS90300001

    Work items whose tasks are defined as general tasks and for which no responsible agents or default rules are defined are offered to all users of the SAP System for execution in their Business Workplaces.
    Procedure
    1.     Access the activity using one of the following navigation options:
    SAP Menu

    Tools ® Business Workflow ® Definition tools  Tasks/Task Groups ®Change
    Transaction Code
    PFTC_CHG
    2.     On the Task: Maintain screen, enter the following values into the corresponding fields:
    Field
    Value
    Task type
    Standard task
    Task
    TS90300003
    3.     On the Task: Maintain screen, choose Change.
    4.     On the Standard Task: Change screen, choose the Additional Data ® Agent assignment ® Maintain option.
    5.     On the Standard task: Maintain Agent Assignment screen, choose Attributes.
    6.     Enter the following values into the corresponding fields:
    Field
    Value
    General task
    Mark this field
    Classification
    Not classified
    7.     Choose Transfer.
    8.     Choose Back.
    9.      On the Standard task screen, from the menu bar, choose Standard task ® Other standard task.
    10.  On the Choose Standard task dialog box, enter the eight-digit number 92000014 in the field Search Term and choose Continue.
    11.  Repeat steps 4 to 10.
    12.  On the Choose Standard task dialog box, enter the eight-digit number 92000011 in the field Search Term and choose Continue.
    13.  Repeat steps 4 to 10 again.
    14.  On the Standard Task: Change screen, choose Save.
    15.  Choose Back.

    1.1.5  Maintaining Settings for Approval Workflow

    Use
    This activity will define the document type, for which an ad-hoc review and approval will be enabled.
    Procedure
    1.     Access the activity using one of the following navigation options:
    SAP Menu
    Tools ® ABAP-Workbench ® Overview ® Data Browser
    Transaction Code
    SE16
    2.     On the Data Browser: Initial screen, enter the name of the table: ZPH_DOKARS_APPRO/ ZECM_APPROVAL  and choose Table contents.
    3.     On the Data Browser: Table ZPH_DOKARS_APPRO/ ZECM_APPROVAL: Selection screen, choose Execute.
    4.     On the Browser: Table ZPH_DOKARS_APPRO/ ZECM_APPROVAL: Select Entries screen, choose Create and enter the name of the document type (field DOKAR) YPD.
    5.     Save the setting and go back.
    Result
    You will see the Reviewers/Approvers tab on your display document screen. You can access it with one of the following navigation options:
    SAP Menu
    Logistics ® Central Functions ® Document Management System ® Document ® Create or Display
    Transaction Code
    CV01N or CV03N

    read more

    Tuesday, January 31, 2012

    0

    MRP: PR to PO Conversion in SAP MM

  • Tuesday, January 31, 2012
  • abhi
  • MRP: PR to PO Conversion

    Go to Transaction SU3 and under Parameters Tab find the Parameter ID "EVO" and check if any value is assigned. If so, make a note of the value.
    Now go to transaction SPRO
    Click on SAP Reference IMG -> Material Management -> Consumption-Based Planning -> Procurement Proposals --> Define Conversion of Purchase Requisition into Purchase Order (as shown below)



    Following screen appears:

     
    Check for the value we have noted earlier (the value of the parameter EVO in SU3). Select the read and check the check boxes appropriately.  We have to select at least one of the check boxes from RefPRs or A/P PR to have all all items copied to PO. Please use the F1 help for detailed information on the check boxes.


    read more
    0

    SAP MM Table Links

  • abhi
  • SAP MM Table Links




    read more
    0

    Deactivation/Deleting a Movement Type in SAP

  • abhi
  • Deactivation/Deleting a Movement Type

    Solution 1 (Preferred):
    • Go to Transaction OMJJ
    • Select the Movement type to be activated
    • Remove all the transaction codes mentioned against this movement type under allow transaction tab.
    Solution 2:
    Consider this solution only if the above solution doesn't work.
    Delete the movement type from the standard table. Ensure that you really don't want to use this movement type before deleting the entry or would never want to recreate the movement type. 
    It is possible to recreate the deleted movement type, but needs to be imported either from the client 000 or from the client this movement type is not deleted. You can not manually create/recreate the movement types in the standard SAP number range by creating them again.
    read more
    1

    Setting up the Release Procedure at item level for the Purchase Requisition in SAP MM Config

  • abhi

  • Setting up the Release Procedure at item level for the Purchase Requisition in SAP MM Config

    Scenario:
    This tutorial focuses on setting up the release strategy at item-level instead of overall release 
    Procedure
    Go to transaction SPRO => Materials Management =>Purchasing => Purchase Requisition => Define Document Types  


    Following screen appears:  


     
    Ensure that for the required document type, the field OverReqRel is unchecked. 
    Now go to transaction SPRO => Materials Management =>Purchasing =>Purchase Requisition =>Release Procedure =>Procedure with classification =>Set up Procedure with Classification 

      
    Following screen appears:

    Now click on Release Group. 
    In the following screen, uncheck the field OverReqRel for the corresponding Release group and save your entries. 



    read more
    1

    Creating one GR document for multiple POs in SAP MM

  • abhi
  • Creating one GR document for multiple POs

    Creation of one GR document for multiple POs can be achieved using the transaction MIGO / MB01, provided all POs belong to one vendor.
    In MIGO transaction, Enter the PO's one by one. Once you enter a PO, the line items would get copied and the PO field would become blank. This way, we can enter multiple PO's belonging to a single vendor.

     

    read more
    0

    Difference between purchase organization, reference purchase organization and standard purchase organization

  • abhi
  • Difference between purchase organization, reference purchase organization and standard purchase organization

    Normal Purchase organization is to procure either for the plant/entire company code/cross company level based upon assignment settings in SPRO.

    For Reference Purchase organization, it will be simply assigned to other normal Purchase organizations only but neither assigned to any plant or company code. This is useful to enjoy the corporate contracts and their price benefits.

    Regarding Standard Purchase organization, it is to handle procurement of special stocks
    read more
    0

    Configuring stock transfer from one storage location to another within a Plant

  • abhi

  • Configuring stock transfer from one storage location to another within a Plant


    Sometimes there might be a requirement for transferring stock from one storage location to another storage location within a Plant. This tutorial would detail the setting required in doing the same:
    Go to Transaction SPRO.
    Click on IMG -> Material Management -> Purchasing -> Purchase Order -> Set up Stock Transport Order -> Set up Stock Transfer between Storage Locations -> Activate Stock Transfer between Storage Locations


    Following screen appears:


     
    Check the above check box to make the stock transfer between storage locations active.


    read more

    Sunday, December 11, 2011

    2

    SAP IDES ECC 6.0 Free Online

  • Sunday, December 11, 2011
  • abhi

    • If you don’t have a user id, you can request one by doing these steps:
      • Go to http://www.ides.consolut.eu/user_request
      • It will redirect you to http://www.ides.consolut.eu/sap/bc/gui/sap/its/zuser_req
      • Fill the form on that page like the below image

        The above image is © SAP AG 2010. All rights reserved
      • Click the “execute” button on the above form, then it will show an information window like the below image.

        The above image is © SAP AG 2010. All rights reserved
      • Click the OK button. You will receive an email that tells you that your request will be processed within 2 business days. But, from my experience, they will process it on the same day.
      • After the registering process, you will receive an email that tells your User ID. You need to request the password daily, because they will change it every day at 00:01 AM CET (I think it’s not a big deal for the free access they give us).
    • If you’ve already had a user ID, you need to request the password daily by doing these following steps:

    read more

    Tuesday, August 2, 2011

    1

    Procurement Cycle In SAP MM-- Raw Material Domestic Procurement

  • Tuesday, August 2, 2011
  • abhi
  • 1.1 Procurement of Raw Material -Local

    1.1.1 Definition of the Process

    This process explains the procurement of raw material example electronic /electrical /Mechanical raw material/spares parts from Domestic Vendor.

    1.1.1.1 Purpose

    Create / amend / approve / print Purchasing documents for procuring raw materials, spares, consumables and send them to Vendor

    1.1.1 Explanation of Process Flow

    · Requirements Determination


    Basically, how do we know we need something? The Marketing department provides PPI inputs. The request for materials as mentioned in procurement BOM usually comes in the form of a purchase requisition. Also
    Purchase requisition are created by different department
    Purchase requisition is subjected to release strategy based on the Approval Matrix Approval are based on the value of the Purchase requisition and also on the nature of purchase and value of Material

    · Source Determination

    The source of supply is determined for the needed item by the purchasing department Enquiries are sent to the suppliers .Enquiry contains the details of the material specification, terms and conditions, quantity of materials etc. Out of SAP


    · Vendor selection

    Quotations provided by the different suppliers are evaluated in terms of content i.e. Price, Taxes & Duties. Vendors are compared based on the Landed price which includes basic price & Duties .Comparative statement is prepared based on the Landed price and vendor is finalized.

    · Purchase order /Scheduling Agreement are prepared for Vendor.

    There are two types of text applicable In Indian Scenerio.

    GTC General Terms applicable for entire Purchase order.

    Item specific text which is applicable for the particular item.



    The different pricing components applicable in case of Local Purchase (Indian Scenerio):

    § Basic Price

    § Freight

    § Basic Excise Duty

    § Cess on Excise duty

    § Higher Education Cess on Excise duty

    § Central Sales Tax

    § Value Added Tax

    § Insurance

    § Development Charges

    § Loading & Unloading Charges

    § Packing & Forwarding Charges

    § Octroi

    § Absolute Discounts (Value)

    § Discount %

    There are amortization charges applicable.

    · Payment Terms, Inco terms is captured and Purchase order is printed on pre-printed stationary.

    · Purchase order is subjected to Approval. Please refer to approval Matrix. Advance is paid to Supplier as per the Payment Terms. Request is sent to Finance Department for Advance Payment to Supplier.

    · Purchase Order is communicated to Suppliers via Email, Courier.


    Steps In SAP

    1. Purchase Requisition is Generated Using T-Code ME51n or Automatically Through MRP.
    2. Use T-code ME54N/ME55 Foe Releasing PR.
    3. After Approval RFQ is Created Using T-Code ME41 and send RFQ to Suppliers.
    4. Maintain RFQ(Filled by Vendors) using ME47 .
    5. Price Comparision using T-Code Me49 and Vendor is Finalised.
    6. Create/Change Purchase Order Using T-Code ME21N/ME22N.
    7. Release Purchase Order Using T-Code ME29N.
    8. Purchase Order Printout Using T-Code ME9F and Send To Vendor.




    read more

    Wednesday, July 20, 2011

    1

    Difference between LP & LPA document type in Scheduling Agreement in SAP

  • Wednesday, July 20, 2011
  • abhi
  • Without release documentation (in the standard system, document type LP)
    The delivery schedule lines have official character - that is to say, they are transmitted to the vendor as they are saved in the system. The system does not document in detail releases against the scheduling agreement that have been sent to the vendor. Therefore, in the case of the document type without release documentation, the message control facility should be set up in such a way that a message is immediately sent to the vendor if any changes are made to the delivery schedule stored in the system. All open scheduling agreements are always output.

    With release documentation (in the standard system, document type LPA)
    If you use scheduling agreements with release documentation, the delivery schedule lines are not transmitted directly to the vendor. Initially, the lines of the delivery schedule stored in the system for an LPA scheduling agreement are for internal information only. A message informing the vendor of your material requirements cannot be transmitted to the vendor until you explicitly create an SA release, that is, a forecast (FRC) or Just-in-Time (JIT) delivery schedule. Through this process, you can change the way the schedule lines are represented. With the release documentation, you can display the SA releases (delivery schedules) transmitted to a vendor over a certain period at any time. This enables you to trace precisely when you sent which
    information to the vendor.
    read more

    Tuesday, July 19, 2011

    2

    How can I open a previous MM period?

  • Tuesday, July 19, 2011
  • abhi
  • Transaction - MMPV
    Menu path - Logistics->Materials Management->MaterialMaster->Other-> Close Period
    USE MMPV AND MMRV FOR THE FISCAL PERIOD CLOSE AND DISPLAY.
    Use transaction MMPI . While doing so you will be asked to apply a SAP Note. That note is just to set parameter in your user thru transaction SU01.
    read more

    Subscribe