Building Block Information774: Customer Order Management at POSBuilding Block InformationAdministrational DataLocalized CountryGermanyUSAChinaAustraliaAustriaBelgiumBrazilCanadaChileColombiaCzech RepublicDenmarkEstioniaFinlandFranceGreeceHungaryIndiaIndonesiaIsraelItalyJapanKoreaLatviaLithuaniaMalaysiaMexicoNetherlandsNorwayPeruPolandPortugalRomaniaRussiaSaudi ArabiaSerbiaSingaporeSpainSwedenSwitzerlandSlovakiaSloveniaSouth AfricaThailandTurkeyUKUkraineVenezuelaVietnamName of the Building Block774: Customer Order Management at POSRACIResponsibleTim IbeTim IbeBB Release InformationBasis ReleaseSAP ERP 6.0 EhP3Released in Edition2008-4VersionV1.603BB System Data Container/SMB99/ALL_H001_J01Country InformationCountry of developmentUSReleased for countriesXNamespaceSMB91DeliverablesBB Description774_EN_US.htmDocumentationConfiguration Guide774_BB_ConfigGuide_EN_US.docUser rolen/aTraining Materialn/aTest Catalogn/a

&L&"Arial,Bold"&14SAP Best Practices: Development Master List&LCopyright 2003 SAP AG All rights reservedName of local BB ownerRequiredThis sheet contains information that in general is not content-related or leads to superordinate information.All data is seen mostly for administrational purposes.RequiredUnique name of the building block.Required'RACI' concept. Interaction with BU SMB Quality Management is probably required, here.REQUIREDEnter global owner of the building block. The local owners have to be entered in country columns.REQUIREDName of global BB ownerRequiredName of local BB ownerRequiredRelease informationRequiredBasis release of the component on which the BB was developed or localized (e.g. ECC 5.0)RequiredBP edition (e.g 2005-3)RequiredBP version (e.g. V1.500)RequiredOptionalMainly to determine country related validity of the building block.Additional input here possible based on the result of the Localization Project.RequiredCountry for which the building block was developpedRequiredRelease of BBs by local teams according RACI concept.RequiredTechnical name of the user role. Please follow the naming convention for technical objects.

Building Block Implementation774: Customer Order Management at POSCSCENewPhaseActivitySystemChangedXRNRLevel 1Level 2Level 3Level 4Level 5DeletedNRRNRNRNRNRNRNRNRNRNRNRNrNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRReferenced BBDocumentationStatusStatusDetailsRemarksBC-SetECATT: Test ConfigurationECATT: Test ScriptECATT: External VariantBC-SET: External VariantTechnical name of docu object in BPIABPIA Manual TaskManual Task Object Name (BPIA)TransactionIMG ActivityDemo Data (& Dependent Configuration)GermanyUSAChinaAustraliaAustriaBelgiumBrazilCanadaChileColombiaCzech RepublicDenmarkEstoniaFinlandFranceGreeceHungaryIndiaIndonesiaIsraelItalyJapanLatviaLithuaniaMalaysiaMexicoNetherlandsNorwayPeruPolandPortugalRomaniaRussiaSaudi ArabiaSerbiaSingaporeSpainSwedenSwitzerlandSlovakiaSloveniaSouth AfricaSouth KoreaTurkeyUKUkraineVenezuelaVietnamPrint FormTesting: Test caseLocalization InformationTranslation InformationLocalization CommentsPreparationInstallation of the Best Practices Installation AssistantInstallation of Baseline Building Blocks (Layer 0):100 - SAP BP InstallationERP100XX101 - Organizational StructureERP101XX102 - External Financial AccountingERP102XX103 - Basic Overhead Cost ControllingERP103XX104 - Materials ManagementERP104XX105 - Sales and DistributionERP105XXInstallation of Industry Building Blocks:701 - Retail OrganisationERP701XX711 - Item ManagementERP711XX712 - Retail PricingERP712XX713 - Assortment OperationsERP713XX721 - Demand-driven ProcurementERP721XX726 - Invoice VerificationERP726XX741 - Warehouse and DC Management (Lean WM)ERP741XX731 - Sales Order ManagementERP731XX733 - Store ConnectivityERP733XX735 - Promotion ManagementERP735XX750 - ECR Compliant Procurement ProcessesERP750XX732 - Cross Channel Customer Order ManagementERP732XX734 - In-Store Merchandise and Inventory ManagementERP734XX761 - BI Retail: ConnectivityBI761XX775 - SAP POS Integration: ERP ConfigurationERP775XX762 - BI Retail: Integration and Content ActivationBI762XX776 - SAP POS Integration: PI ConfigurationPI776XX777 - SAP POS ConfigurationPOS777XX778 - SAP POS Integration: POS DM ConfigurationPOS DM778XX780 - Retail Master Data GenericERP780XX781 - Retail Master Data FashionERP781XX782 - Retail Master Data FoodERP782XX783 - Retail Master Data HardgoodsERP783XX763 - BI Retail: Customizing and Master Data ExtractionERP763XX773 - BI Retail: POS AnalyticsBI773XXInstallationNo specific configuration requiredTest/Evaluation/Training

&L&"Helvetica,Bold"&16SAP Best Practices: Development Master List&LCopyright 2005 SAP AG All rights reservedDescription of the activity that needs to be carried out or taken into account in the installation process. The listed installation activities correspond to the activities in the installation role.Each document and object that is delivered has to be assigned to an activity.The levels represent a structure that follows a content-related hierarchy.Objects can be assigned to each level (that means to a hierarchy node as well, e.g. if a document refers to a group of activities).Reduce the number of levels to a minimum. Consider the phase (in column A) as level 0!Phases are the different stages of the installation process of a building block. They group the activities and prerequisites for the installation and use of a building block in chronological order and usually include the phases - Preparation- Installation / Configuration- Test/ EvaluationHide column if not required

Description or name of another building block if an activity is linked to a different building blockTechnical name of a BC Set used in a building block. Please follow the naming convention for technical objects.Technical name linked to component libraryPrint forms / Smart FormsFor localization relevant objects only.If the object is relevant for localization, flag this cell.Here, you can enter important remarks, such as " BC Set has to be activated twice"'R' means released with the latest editiond.

'NR' means not yet released

Note: Release Country before creating the BPIA BB file.Add status details:

- Responsible team: e.g. US- Date: DD.MM.YYYYThe status field has to be filled as follows:

- NEW (if a new activity has been added)- CHANGED (if an activity has been changed)- DELETED (if an activity has been deleted)

This field is not designed for handling the complete change administration and does not show the complete change history.

It is only an indicator that the activity has been changed, added, or deleted.

--> only indicates to the responisble localization team that the activity needs particular attention.Relevant for autmated test casesdo not delete this cell - text for validationCS= country start CE = country end

do not delete these flags - required for autmatic creation of BPIA file.do not delete this cell - text for validationdo not delete this cell - text for validationdo not delete this cell - text for validationdo not delete this cell - text for validationHide column if not required

for each configuration object general documentation --> not maintained in pastEnter the following value if the activity is in scope:

X = in scope, use documantation object in column "Technical name of docu object in BPIA", mandatory, background

The following other entries are also possible and will be evaluated and considered by the macro that automatically creates the BPIA file.

X:O:B = in scope, documentation object in column "Technical name of docu object in BPIA", optional, background

X:M:F = in scope, documentation object in column "Technical name of docu object in BPIA", mandatory, foreground

X:O:F = in scope, documentation object in column "Technical name of docu object in BPIA", optional, foreground

Name of documentation object = implies manual step which is always mandatory and in the foregroundTechnical name of the IMG ActivityPlease enter the system where the configuration activity has to be executed.Choose a sytem from the following list:- ECC- CRM- BI- SCM- SRM- XICS= country start CE = country end

do not delete these flags - required for autmatic creation of BPIA file.Use this column to flag demo data nnd any configuration activities that have demo data as a prerequisiteFor localization relevant objects only.If the object is relevant for translation flag this call.

Comment: localization teams get the information that this file has to be translated.do not delete this cell - text for validationFor localization relevant objects only.If the object is relevant for localization, enter what specifically needs to be localized.

Comment: localization teams can use this to communicate with each other and within a localizationRequired for Direct BC-Set activation. Leave blank (and highlight grey) if you want to keep Ecatt based BC-Set activation, e.g. Scripting required.