sap培训时得到的

1、Logistics Master Data DesignTradeSAP Best PracticesProduct HierarchyLogisticsThis data is created in BB 10400001Top Level00001B0001Products A(Manufact./Trade)00001B0002Products B(Services)00001B Products A.01 (MTO)00001B Products A.02 (MTS)00001B Parts A.0300001B Products B.0100001B Products B.02Lev

2、el 1Level 2Level 3Product Hierarchy Level 3 Product GroupLevel 2CO-PASOP InterfaceAll material master records assigned to product hierarchy level 3ClassificationClass & Characteristics for BatchesThis data is created in BB 117Class - 023 YB_EXP_DATE_001 Batch Products with Expiration DateChar.LOBM_V

3、FDATExpiration date, shelf life Char.YB_SUPPLIER_BATCH_NUMBERVendor Batch NumberClass - 023 YB_BATCH Batch FIFO 1Char.YB_BATCH_NUMBERBatch NumberChar.LOBM_VFDAT Expiration date, shelf lifeClass - 023 YB_EXP_DATE_002 Batch Search class with expiration dateChar.LOBM_LFDATBatch Determin. Delivery DateC

4、har.LOBM_RLZ Remaining Shelf Life for BatchUsed in all processes which are using batch materialsClassificationClass & Characteristics for PO ReleaseClass 032R2R_CL_REL_CEKKOPO Release at Header LevelCharR2R_PURCH_ORD_TYPEOrder type (Purchasing)CharR2R_PURCH_ORD_VALUETotal net order valueValuesFO Fra

5、meworkNB Standard POUB Stock transport orderValuesAmount and Local CurrencyValuesPurchase Group CharR2R_PURCH_GRPPurchasing groupProcurement Processes using PO release strategyThis data is created in BB 104Trading GoodsProduct StructureThis master data is created in BB 152Batch ManagementBH11Trading

6、 Good, Reg.Trading (HAWA-PD)H12Trading Good, Reorder Point, Reg. Trading (HAWA-VB)H20Trading Good, Reorder Point,Batch-FIFO(HAWA-VB)H21Trading Good, Reorder Point, Batch Exp.Date(HAWA-VB)SNSerial NumbersH14Trading Good, Bought-In(HAWA-PD)Used in Sales Bought in ItemUsed in Third Party w. / w/o Shipp

7、ing NotificationBBH20Trading Good, Reorder Point, Serial No(HAWA-VB)SNUsed in all MM/SD Scenarios for Trade*H11Trading Good, Third Party(HAWA-PD)H12Trading Good, Reorder Point, Third Party (HAWA-VB)* Except Scenarios: Third Party Order Proc. and Sales Bought In item Used in all MM /SD Scenarios for

8、Trade showing (Serial Nos)Used in all MM /SD Scenarios for Trade (Batch Man. Funct.)Master Data Enhancement in BB (126 Layer 2Master Data Enhancement in BB (117 Layer 2ReturnablesProduct StructureL001Empties (LEIH-ND)Returnables ProcessingThis master data is created in BB 152LegendSymbolDescriptionU

9、sage CommentsTo next / From last Diagram: Leads to the next / previous page of the DiagramFlow chart continues on the next / previous pageHardcopy / Document: 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 ge

10、nerated by a task step; this shape does not have any outgoing flow linesFinancial Actuals: Indicates a financial posting document 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 linesBudg

11、et 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 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

12、 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 the process flow. Existing Version / Data: This block covers data that feeds in from an external process Does not generally correspond to a task ste

13、p 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 Decision: 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

14、reflect an automatic decision by the system that is made after a step has been executed. External to SAPBusiness Activity / EventUnit ProcessProcess ReferenceSub-Process ReferenceProcess DecisionDiagram ConnectionHardcopy / DocumentFinancial ActualsBudget PlanningManual ProcessExisting Version / Dat

15、aSystem Pass/Fail DecisionSymbolDescriptionUsage CommentsBand: Identifies a user role, such as Accounts Payable Clerk or Sales Representative. This band 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 h

16、ave 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 that 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 di

17、rection 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 documents involved in the process flow.Connects two tasks in a scenario process or a non-step eventBusiness Activity / Event: Identifies an action th

18、at 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 scenario referen