sap培训时得到的

1、Sales Processing using Third Party (w. Shipping Notification)SAP Best PracticesPurpose, Benefits, and Key Process StepsPurpose In third-party order processing, your company does not deliver the items requested by a customer. Instead, you pass the order along to a third-party vendor who then ships th

2、e goods directly to the customer and bills you. The standard sales order automatically creates a purchase requisition for the materials to be delivered by the third-party vendor. Benefits Reducing stock and cost, increasing efficiency Handover of customers requirements directly to external supplierI

3、nvoice from trader to customer bases on quantities from supplier invoiceFulfillment of customers requirements despite material shortage Key Process StepsThird Party Sales OrderConvert Purchase Requisitions to Purchase OrderApproval of Purchase Orders Post Statistical Goods Receipt Invoice verificati

4、on BillingRequired SAP Applications and Company RolesRequired SAP ApplicationsSAP enhancement package 5 for SAP ERP 6.0Company RolesSales AdministrationWarehouse ClerkAccounts ReceivableBuyerPurchasing ManagerSales BillingAccounts PayableDetailed Process DescriptionSales Processing using Third Party

5、 (w. Shipping Notification)In this scenario, the vendor sends a shipping notification. The ing invoice from the vendor updates the billing quantity, so that the customer-billing document is only possible after entering the invoice from the vendor. In this scenario, the vendor sends a shipping notifi

6、cation. After that a statistical goods receipt is posted. The ing invoice from the vendor updates the billing quantity, so that the customer-billing document can only be created after entering the invoice from the vendor.Process Flow DiagramSales Processing using Third Party (w. Shipping Notificatio

7、n)Sales AdministrationPurchasing Manager / BuyerAccounts Payable / ReceivableVendorWare-house ClerkCustomerBillingDrop Ship Product to 3rd PartySend Shipping Notification/ Confirmation ing Vendor InvoiceCustomer Request for MaterialOrder ConfirmationCreate Sales OrderAuto-generates a RequisitionQuot

8、ation for Procurement (128)Display List of Purchase Requisitions to Be AssignedConvert Assigned Requisitions to Purchase OrdersApproval of Purchase OrdersAPOutgoing Payment (158)COGS VendorInvoice ReceiptPost Statistical Goods Receipt(Optional)Change Order QuantityAP = Accounts Payable, COGS = Cost

9、of Goods Sold, GR = Goods ReceiptAR ing Payment (157)Billing DocumentSales: Period End Closing Operations (203)Sales BillingLegendSymbolDescriptionUsage CommentsTo next / From last Diagram: Leads to the next / previous page of the DiagramFlow chart continues on the next / previous pageHardcopy / Doc

10、ument: Identifies a printed document, report, or form Does not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not have any outgoing flow linesFinancial Actuals: Indicates a financial posting document Does not correspond to

11、 a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not have any outgoing flow linesBudget Planning: Indicates a budget planning document Does not correspond to a task step in a document; instead, it is used to reflect a document generated

12、by a task step; this shape does not have any outgoing flow linesManual Process: Covers a task that is manually done Does not generally correspond to a task step in a document; instead, it is used to reflect a task that is manually performed, such as unloading a truck in the warehouse, which affects

13、the process flow. Existing Version / Data: This block covers data that feeds in from an external process Does not generally correspond to a task step in a document; instead, this shape reflects data coming from an external source; this step does not have any ing flow lines System Pass / Fail Decisio

14、n: This block covers an automatic decision made by the software Does not generally correspond to a task step in the document; instead it is used to reflect an automatic decision by the system that is made after a step has been executed. External to SAPBusiness Activity / EventUnit ProcessProcess Ref

15、erenceSub-Process ReferenceProcess DecisionDiagram ConnectionHardcopy / DocumentFinancial ActualsBudget PlanningManual ProcessExisting Version / DataSystem Pass/Fail DecisionSymbolDescriptionUsage CommentsBand: Identifies a user role, such as Accounts Payable Clerk or Sales Representative. This band

16、 can also identify an organization unit or group, rather than a specific role.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.Role band contains tasks common to that role.External Events: Contains events tha

17、t start or end the scenario, or influence the course of events in the scenario.Flow line (solid): Line indicates the normal sequence of steps and direction of flow in the scenario.Flow line (dashed): Line indicates flow to infrequently-used or conditional tasks in a scenario. Line can also lead to d

18、ocuments involved in the process flow.Connects two tasks in a scenario process or a non-step eventBusiness Activity / Event: Identifies an action that either leads into or out of the scenario, or an outside Process that happens during the scenarioDoes not correspond to a task step in the document Unit Process: Identifies a task that is covered in a step-by-step manner in the scenarioCorresponds to a task step in the document Process Reference: If the s