Batch Recall SAP Best Practices Baseline Package (Vietnam)

Document Sample
Batch Recall SAP Best Practices Baseline Package (Vietnam) Powered By Docstoc
					Batch Recall
SAP Best Practices Baseline Package
(Vietnam)




SAP Best Practices
Scenario Overview – 1


    Purpose and Benefits:

     Purpose
          A defect batch is identified and must be recalled from customers and prospects
           who have received the batch.

     Benefits
          Integrated follow-up process to the former delivered batch
          return stock managed separately from the rest of your stock

     Key process flows covered
          Creation of direct mailing to customer
          Preparing follow-up process for the return of the batch
          Receiving of returned batch into return stock
          Decision of further usage of the returned stock
          Creation of credit memo for customer
Scenario Overview – 2

     SAP Applications Required:
        Required
             EHP3 for SAP ERP 6.0

        Company roles involved in process flows
             Sales Administration
             Warehouse Clerk
             Quality Manager
Scenario Overview – 3

    Detailed Process Description:
      Batch Recall

      A program is executed to identify all customers who received a defect batch. The user
      then chooses the addresses of the appropriate contact persons, and the system prints
      a standard letter to each customer to inform them of the recall. The subsequent
      activities for each customer are stored in the system. Return deliveries are also
      entered and documented, if necessary.

      To ensure that you contact all customers affected by a defect batch, you must identify
      if subsequent batches are affected by the defect batch. For this purpose, you can use
      the standard system function “batch where-used list” that is described in detail in the
      standard SAP ERP documentation. This scenario recalls a batch from a finished
      product or wholesale product. Therefore you can simply find all customers who
      received these products. However, a vendor could report that a raw, semi-finished,
      trading, or other material used in your production, does not meet quality standards. In
      this case, you must determine which finished or trading materials were produced with
      these defect batches.
Process Flow Diagram
  Batch Recall
    Event




                     Sales Order            Defect Batch                                                                                           Accounts                   Closing
                     Processing:              Must Be                                                                                              Receivable                Operations
                      Sale from               Recalled                                                                                               (157)                    SD (203)
                     Stock (109)
    Customer




                                                                    Customer                               Customer
                                                                     Letters                                Returns
                                                                                                            Material




                                           Direct Mailing –           Generate                                                                                      Invoice Financial
 Administration




                                           Creating Basic         Follow-up Sales          Return Order                                       Credit Memo               Account
                                                Data                 Activities                                                                                        Profitability
                                                                                                                                                                        Analysis
    Sales




                                           Address List of            Process
                                             Customers            Follow-up Sales          Create Return
                                           Who Received            Activities for             Order
                                               Batch              Each Customer
     Sales Billing




                                                                                                                            Release Credit                      Billing
                                                                                                                            Memo to Billing
Clerk/Quality
 Warehouse
  Manager




                         Return Delivery
                                                                                                                                                   (Optional)                (Optional)
                                                                                                                                                    Rework                  Stock Usage
                                                                                                                           (Optional)             Processing                  Blocking
                                                 Assign Batches                Assign Serial                 Post Goods    Return to                (Stock-
                                                                                 Numbers                       Receipt    Vendor (136)               Manuf.                      and
                                                                                                                                                  Material)(151              Scrapping
                                                                                                                                                        )                       (131)
Legend

Symbol                         Description                                             Usage             Symbol                 Description                           Usage Comments
                                                                                       Comments

                               Band: Identifies a user role, such as Accounts          Role band                                To next / From last Diagram: Leads    Flow chart continues on the next /
                                                                                                                                to the next / previous page of the    previous page
   <Function>




                               Payable Clerk or Sales Representative. This band        contains tasks
                                                                                                                                Diagram
                               can also identify an organization unit or group,        common to
                                                                                                                   Diagram
                               rather than a specific role.                            that role.                 Connection
                               The other process flow symbols in this table go into
                               these rows. You have as many rows as required to
                               cover all of the roles in the scenario.
                                                                                                                                Hardcopy / Document: Identifies a     Does not correspond to a task
                                                                                                                                printed document, report, or form     step in a document; instead, it is
                                                                                                                  Hardcopy /                                          used to reflect a document
                               External Events: Contains events that start or end                                 Document                                            generated by a task step; this
   External
   to SAP




                               the scenario, or influence the course of events in                                                                                     shape does not have any outgoing
                               the scenario.                                                                                                                          flow lines



                                                                                       Connects two                             Financial Actuals: Indicates a        Does not correspond to a task
                               Flow line (solid): Line indicates the normal sequence                                            financial posting document            step in a document; instead, it is
                               of steps and direction of flow in the scenario.         tasks in a
                                                                                       scenario                    Financial                                          used to reflect a document
                               Flow line (dashed): Line indicates flow to              process or a                 Actuals                                           generated by a task step; this
                               infrequently-used or conditional tasks in a scenario.   non-step event                                                                 shape does not have any outgoing
                                                                                                                                                                      flow lines
                               Line can also lead to documents involved in the
                               process flow.

                                                                                                                                Budget Planning: Indicates a          Does not correspond to a task
                                                                                                                                budget planning document              step in a document; instead, it is
                               Business Activity / Event: Identifies an action that    Does not                                                                       used to reflect a document
                               either leads into or out of the scenario, or an         correspond to                Budget                                            generated by a task step; this
                Business       outside Process that happens during the scenario        a task step in              Planning                                           shape does not have any outgoing
                Activity /                                                             the document                                                                   flow lines
                 Event

                                                                                                                                Manual Process: Covers a task         Does not generally correspond to
                               Unit Process: Identifies a task that is covered in a    Corresponds to                           that is manually done                 a task step in a document;
                               step-by-step manner in the scenario                     a task step in               Manual                                            instead, it is used to reflect a task
                                                                                       the document                 Proces                                            that is manually performed, such
                Unit Process                                                                                                                                          as unloading a truck in the
                                                                                                                       s                                              warehouse, which affects the
                                                                                                                                                                      process flow.

                               Process Reference: If the scenario references           Corresponds to
                               another scenario in total, put the scenario number      a task step in                           Existing Version / Data: This block   Does not generally correspond to
                  Process      and name here.                                          the document                             covers data that feeds in from an     a task step in a document;
                 Reference                                                                                          Existing    external process                      instead, this shape reflects data
                                                                                                                    Version /                                         coming from an external source;
                                                                                                                                                                      this step does not have any
                                                                                                                      Data                                            incoming flow lines
                               Sub-Process Reference: If the scenario references       Corresponds to
                   Sub-        another scenario in part, put the scenario number,      a task step in
                               name, and the step numbers from that scenario           the document
                  Process      here                                                                                             System Pass / Fail Decision: This     Does not generally correspond to
                 Reference                                                                                          System      block covers an automatic             a task step in the document;
                                                                                                                    Pass/F      decision made by the software         instead it is used to reflect an
                                                                                                                      ail                                             automatic decision by the system
                                                                                                                    Decisio                                           that is made after a step has been
                               Process Decision: Identifies a decision / branching     Does not                                                                       executed.
                               point, signifying a choice to be made by the end        usually                        n
                  Proces       user. Lines represent different choices emerging        correspond to
                     s         from different parts of the diamond.                    a task step in
                                                                                       the document;
                  Decisio                                                              Reflects a
                    n                                                                  choice to be
                                                                                       made after step
                                                                                       execution