A78_Master_List_Global A78 - Make-To-Stock With Reservation

3
SAP Best Practices: Development Master List Copyright © 2003 SAP AG All rights reserved A78 - Make-to-Stock With Reservation Building Block Information Administrational Data Localized Country Germany USA China Australia Austria Belgium Brazil Denmark Finland France Greece Hungary India Israel Italy Japan Malaysia Mexico Netherlands Norway Poland Portugal Romania Russia Serbia Singapore Spain Sweden Switzerland Slovakia Slovenia South Korea Thailand Turkey Ukraine Name of the Building Block A78: Make-to-Stock With Reservation RACI Responsible Ying Diao Ying Diao BB Release Information Basis Release ECC 5.0 Released in Edition 2007-1 Version V1.600 Country Information Country of development DE Released for countries X Namespace SMB50 Documentation Configuration Guide A78_Config_Guide_EN_DE.doc User role n/a Training Material n/a Test Catalog n/a Czech Republic Saudi Arabia South Africa United Kingdom

description

SAP

Transcript of A78_Master_List_Global A78 - Make-To-Stock With Reservation

Building Block InfoA78 - Make-to-Stock With ReservationBuilding Block InformationAdministrational DataLocalized CountryGermanyUSAChinaAustraliaAustriaBelgiumBrazilCzech RepublicDenmarkFinlandFranceGreeceHungaryIndiaIsraelItalyJapanMalaysiaMexicoNetherlandsNorwayPolandPortugalRomaniaRussiaSaudi ArabiaSerbiaSingaporeSpainSwedenSwitzerlandSlovakiaSloveniaSouth AfricaSouth KoreaThailandTurkeyUkraineUnited KingdomName of the Building BlockA78: Make-to-Stock With ReservationRACIResponsibleYing DiaoYing DiaoBB Release InformationBasis ReleaseECC 5.0Released in Edition2007-1VersionV1.600Country InformationCountry of developmentDEReleased for countriesXNamespaceSMB50DocumentationConfiguration GuideA78_Config_Guide_EN_DE.docUser rolen/aTraining Materialn/aTest Catalogn/a
&L&"Arial,Bold"&14SAP Best Practices: Development Master List
&LCopyright 2003 SAP AG All rights reserved
This sheet contains information that in general is not content-related or leads to superordinated information.All data is seen mostly for administrational purposes.Required
Name of the BB, should be unique.Required
'RACI' concept. Interaction with BU SMB Quality Management is probably required, here.REQUIRED
Enter global owner of the building block. The local owners have to be entered in country columns.REQUIRED
Release informationRequired
Basis release of the component on which the BB was developed or localized (e.g. ECC 5.0)Required
Mainly to determine coutry related validity of the BB.Additional input here possible based on the result of the Localization Project.Required
Country for which the BB was developedRequired
Release of BBs by local teams according RACI concept.Required
Technical name of the user role. Please follow the naming convention for technical objects.
Name of global BB ownerRequired
BP version (e.g. V1.500)Required
BP edition (e.g 2005-3)Required
Name of global BB ownerRequired
&L&"Arial,Bold"&14SAP Best Practices: Development Master List
&LCopyright 2003 SAP AG All rights reserved
&L&"Arial,Bold"&14SAP Best Practices: Development Master List
&LCopyright 2003 SAP AG All rights reserved
&L&"Arial,Bold"&14SAP Best Practices: Development Master List
&LCopyright 2003 SAP AG All rights reserved
&L&"Arial,Bold"&14SAP Best Practices: Development Master List
&LCopyright 2003 SAP AG All rights reserved
&L&"Arial,Bold"&14SAP Best Practices: Development Master List
&LCopyright 2003 SAP AG All rights reserved
&L&"Arial,Bold"&14SAP Best Practices: Development Master List
&LCopyright 2003 SAP AG All rights reserved
&L&"Arial,Bold"&14SAP Best Practices: Development Master List
&LCopyright 2003 SAP AG All rights reserved
Building Block ImplementationA78: Make-to-Stock With ReservationCSCENewPhaseActivitySystemChangedXRNRLevel 1Level 2Level 3Level 4Level 5DeletedNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRReferenced BBStatusStatus DetailsBC-SetECATT: Test ConfigurationECATT: Test ScriptECATT: External VariantTechnical name of docu object in BPIABPIA Manual TaskTransactionGermanyUSAChinaAustraliaAustriaBelgiumBrazilCzech RepublicDenmarkFinlandFranceGreeceHungaryIndiaIsraelItalyJapanKoreaMalaysiaMexicoNetherlandsNorwayPolandPortugalRomaniaRussiaSaudi ArabiaSerbiaSpainSwedenSwitzerlandSlovakiaSloveniaSouth AfricaThailandTurkeyUKUkrainePrint FormTesting: Test caseLocalization InformationRemarksPreparationPrerequisitesPrerequisites in the Sales SystemInstallation of Baseline Project for AutomotiveB32 - SAP Best Practices InstallationERPB32XJ02 - Organizational StructureERPJ02XN69 - External Financial Accounting BasicsERPN69XN70 - External Financial Accounting LocalERPN70XN71 - Central Cost Center AccountingERPN71XJ05 - Material ManagementERPJ05XJ04 - Sales and DistributionERPJ04XJ06 - Production Planning and ControlERPJ06XJ18 - Product Cost PlanningERPJ18XJ17 - Profitability AnalysisERPJ17XJ19 - Batch ManagementERPJ19XJ21 - Cost Object Controlling - Make-to-StockERPJ21XInstallation of Industry-Generic Building Blocks:A01 - Automotive Basic SettingsERPA01XA05 - Master Data for AutomotiveERPA05XInstallation of Scenario specific Building Blocks (In Sales client)A23 - Vehicle Management SystemERPA23XInstallationInstallation in the Sales SystemMaster DataERPAUTO_DECreating Material MasterERP/SMB0V/MM01_ALL_VIEWS_O001_A05/SMB99/MM01_ALL_VIEWS_I015_J01SMB0V_MM01_ALL_VIEWS_O001_A78_SAL.TXTMM01XAUTO_DECreating Master WarrantyERP/SMB0V/BGM1_O001_A78/SMB0V/BGM1_I001_A78SMB0V_BGM1_O001_A78_SAL.TXTBGM1XAUTO_DEChanging Master Warranty Description for Targent Language/SMB0V/BGM1_O002_A78/SMB0V/BGM1_I002_A78SMB0V_BGM1_O002_A78_SAL.TXTBGM2XDescriptionMM and SD conditonsERPXAUTO_DECreating SD Condition records - VA00ERP/SMB0V/VK11_O001_A78/SMB0V/VK11_I001_A78SMB0V_VK11_O001_A78_SAL.TXTVK11XAUTO_DECreating SD Condition records - PR00ERP/SMB0V/VK11_O002_A78/SMB0V/VK11_I002_A78SMB0V_VK11_O002_A78_SAL.TXTVK11XAUTO_DECreating Purchase Info RecordERP/SMB0V/ME11_O001_A59/SMB0V/ME11_I001_A59SMB0V_ME11_O001_A59_A78_SAL.TXTME11XAUTO_DECreating MM Condition records - VA00ERP/SMB0V/MEK1_O001_A78/SMB0V/MEK1_I001_A78SMB0V_MEK1_O001_A78_SAL.TXTMEK1XVMS SettingERPXManual Activity:Checking User ParametersERP/SMB0V/CU3_A76_01CU3XAUTO_MASTERCreating Configuration ProfileERP/SMB0V/CU41_O001_A78/SMB0V/CU41_I001_A78SMB0V_CU41_O001_A78_SAL.TXTCU41XDescriptionAUTO_DECreating Configuration Interface in foregroundERP/SMB0V/CU50_O001_A78/SMB0V/CU50_I001_A78SMB0V_CU50_O001_A78_SAL.TXT/SMB0V/CU50_A78CU50XDescriptionAUTO_DECreating Kownledge-based objectERP/SMB0V/CU31_O001_A78/SMB0V/CU31_I001_A78SMB0V_CU31_O001_A78_SAL.TXTCU31XAUTO_DECreating Runtime versionERP/SMB0V/CU34_O001_A78/SMB0V/CU34_I001_A78SMB0V_CU34_O001_A78_SAL.TXTCU34XAUTO_DECreating User for VMSERP/SMB0V/SU01_O001_A01/SMB0V/SU01_I001_A01SMB0V_SU01_O001_A01_A78_SAL.TXTSU01XAUTO_MASTERAssigning Vehicle ModelERP/SMB0V/VELORM_O001_A78/SMB0V/VELORM_I001_A78SMB0V_VELORM_O001_A78_SAL.TXTVELORMXAUTO_MASTERAssigning VMS Roles to UserERP/SMB0V/VELORU_O001_A78/SMB0V/VELORU_I001_A78SMB0V_VELORU_O001_A78_SAL.TXTVELORUXAUTO_DEAssigning Organizational DataERP/SMB0V/VELORO_O001_A23/SMB0V/VELORO_I001_A23SMB0V_VELORO_O001_A23_A78_SAL.TXTVELOROXAUTO_MASTERSetting Determination of Action ControlERP/SMB0V/VELOS_O001_A78/SMB0V/VELOS_I001_A78SMB0V_VELOS_O001_A78_SAL.TXTVELOSXAUTO_DEDetermining Message Condition RecordsERP/SMB0V/VELOK_O001_A78/SMB0V/VELOK_I001_A78SMB0V_VELOK_O001_A78_SAL.TXTVELOKXAdding ImagesERP/SMB0V/SAPDIICIMGMANT_B001_A78/SMB0V/SAPDIICIMGMANT_O001_A78/SMB0V/SAPDIICIMGMANT_I001_A78SMB0V_SAPDIICIMGMANT_O001_A78_SAL.TXTSPROXManual Activity:Maintaining Picture for Vehicle in Dealer PortalERP/SMB0V/SE80_A78SE80XManual Activity: Maintain the smart formsERP/SMB0V/SMARTFORM_A78SMARTFORMSXTest/Evaluation/TrainingBusiness Application Testing
&L&"Helvetica,Bold"&16SAP Best Practices: Development Master List
&LCopyright 2005 SAP AG All rights reserved
Description 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/ Evaluation
Technical name linked to component library
Print forms / Smart Forms
For 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 localization
Here, you can enter important remarks, such as " BC Set has to be activated twice"
Add status details: - Responsible team: e.g. US- Date: DD.MM.YYYY
This status field has to be filled as follows:- NEW (if a new activity is added)- CHANGED (if activity was changed)- DELETED (if activity is 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 cases
CS= country start CE = country enddo not delete these flags - required for autmatic creation of BPIA file.
CS= country start CE = country enddo not delete these flags - required for autmatic creation of BPIA file.
do not delete this cell - text for validation
do not delete this cell - text for validation
'R' means released with the latest editiond. 'NR' means not yet releasedNote: Release Country before creating the BPIA BB file.
do not delete this cell - text for validation
do not delete this cell - text for validation
do not delete this cell - text for validation
do not delete this cell - text for validation
Enter 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, backgroundX:M:F = in scope, documentation object in column "Technical name of docu object in BPIA", mandatory, foregroundX:O:F = in scope, documentation object in column "Technical name of docu object in BPIA", optional, foregroundName of documentation object = implies manual step which is always mandatory and in the foreground
Hide column if not requiredDescription or name of another building block if an activity is linked to a different building block
C5057141:Loading Configuraiton in the IPC, In this project, we don't need IPC, But in next verison, maybe use it.
C5057141:Loading Configuraiton in the IPC, In this project, we don't need IPC, But in next verison, maybe use it.
Technical name of a BC Set used in a building block. Please follow the naming convention for technical objects.
C5057141:Enhance, release the variant
C5057141:Run it in foreground
&L&"Helvetica,Bold"&16SAP Best Practices: Development Master List
&LCopyright 2005 SAP AG All rights reserved
&L&"Helvetica,Bold"&16SAP Best Practices: Development Master List
&LCopyright 2005 SAP AG All rights reserved
&L&"Helvetica,Bold"&16SAP Best Practices: Development Master List
&LCopyright 2005 SAP AG All rights reserved
&L&"Helvetica,Bold"&16SAP Best Practices: Development Master List
&LCopyright 2005 SAP AG All rights reserved
&L&"Helvetica,Bold"&16SAP Best Practices: Development Master List
&LCopyright 2005 SAP AG All rights reserved
&L&"Helvetica,Bold"&16SAP Best Practices: Development Master List
&LCopyright 2005 SAP AG All rights reserved
&L&"Helvetica,Bold"&16SAP Best Practices: Development Master List
&LCopyright 2005 SAP AG All rights reserved