Building Block Implementation223: Easy Document ManagementCSCENewPhaseActivitySystemChangedXRNRLevel 1Level 2Level 3Level 4Level 5DeletedRNRRRNRRNRRNRRNRNRNRNRNRNRRNRNRRRNRNRRNRRRNRRNRNRNRRNRNRRNRNRRNRNRRNRNRNRRRRRRNRNRReferenced 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)GermanyDiscrete ManufacturingUSAChinaArgentinaAustraliaAustriaBelgiumBrazilCanadaChileColombiaCzechiaDenmarkEstoniaFinlandFranceGreeceHungaryIndiaIndonesiaIsraelItalyJapanLatviaLithuaniaMalaysiaMexicoNetherlandsNorwayPakistanPeruPolandPortugalRomaniaRussiaSaudi ArabiaSerbiaSingaporeSpainSwedenSwitzerlandSlovakiaSloveniaSouth AfricaSouth KoreaThailandTurkeyUKUkraineVenezuelaVietnamPrint FormTesting: Test caseLocalization InformationTranslation InformationPreparationInstallation of Baseline Building Blocks (Layer 0):XXXXXXXXXXXXXXXXXXXXXXXXXXXX100 - SAP BP InstallationECC100XXXXXXXXXXXXXXXXXXXXXXXXXXXX101 - Organizational StructureECC101XXXXXXXXXXXXXXXXXXXXXXXXXXXX102 - External Financial AccountingECC102XXXXXXXXXXXXXXXXXXXXXXXXXXXX103 - Basic Overhead Cost ControllingECC103XXXXXXXXXXXXXXXXXXXXXXXXXXXX104 - Materials ManagementECC104XXXXXXXXXXXXXXXXXXXXXXXXXXXX105 - Sales and DistributionECC105XXXXXXXXXXXXXXXXXXXXXXXXXXXX153 - Printing: FormsECC153XXXXXXXXXXXXXXXXXXXXXXXXXXXXInstallationConfigurationERPXXXXXXXXXXXXXXXXXXXXXXXXXXXSettings for Document ManagementERPXXXXXXXXXXXXXXXXXXXXXXXXXXXDefine Document Type YBO, FOLERPRS5K944107/SMBA0/V_TDWA_1_B1D2_J0B/SMBA0/V_TDWA_1_O1D2_J0B/SMBA0/V_TDWA_1_I1D2_J0BSMBA0_V_TDWA_1_O1D2_J0B_223.txtSMBA0_V_TDWA_1_B1D2_J0B_223.txtSPROXXXXXXXXXXXXXXXXXXXXXXXXXXXxDefine Document Types - Document StatusERP/SMBA0/V_TDWS_1_B1D2_J0G/SMBA0/V_TDWS_1_O1D2_J0G/SMBA0/V_TDWS_1_I1D2_J0GSMBA0_V_TDWS_1_O1D2_J0G_223.txtSMBA0_V_TDWS_1_B1D2_J0G_223.txtSPROXXXXXXXXXXXXXXXXXXXXXXXXXXXDefine Workstation ApplicationERP/SMBA0/V_TDWO_1_B1D2_J0D/SMBA0/V_TDWO_1_O1D2_J0D/SMBA0/V_TDWO_1_I1D2_J0DSMBA0_V_TDWO_1_O1D2_J0D_223.txtSMBA0_V_TDWO_1_B1D2_J0D_223.txtSPROXXXXXXXXXXXXXXXXXXXXXXXXXXXDefining Data CarrierERPNew/SMBA0/V_TDWE_C1_B1D3_J0C/SMBA0/V_TDWE_C1_O1D3_J0C/SMBA0/V_TDWE_C1_I1D3_J0CSMBA0_V_TDWE_C1_O1D3_J0C_223.txtSMBA0_V_TDWE_C1_B1D3_J0C_223.txtSPROXXXXXXXXXXXXXXXXXXXXXXXXXXXDefining Data CarrierERPNew/SMBA0/V_TDWD_C_B1D3_J0B/SMBA0/V_TDWD_C_O1D3_J0B/SMBA0/V_TDWD_C_I1D3_J0BSMBA0_V_TDWD_C_O1D3_J0B_223.txtSMBA0_V_TDWD_C_B1D3_J0B_223.txtSPROXXXXXXXXXXXXXXXXXXXXXXXXXXXDefining Data CarrierERP/SMBA0/V_TDWD_B1_B1D3_J0A/SMBA0/V_TDWD_B1_O1D3_J0A/SMBA0/V_TDWD_B1_I1D3_J0ASMBA0_V_TDWD_B1_O1D3_J0A_223.txtSMBA0_V_TDWD_B1_B1D3_J0A_223.txtSPROXXXXXXXXXXXXXXXXXXXXXXXXXXXxDefining Data CarrierERPNew/SMBA0/V_TDWN_1_B1D3_J0D/SMBA0/V_TDWN_1_O1D3_J0D/SMBA0/V_TDWN_1_I1D3_J0DSMBA0_V_TDWN_1_O1D3_J0D_223.txtSMBA0_V_TDWN_1_B1D3_J0D_223.txtSPROXXXXXXXXXXXXXXXXXXXXXXXXXXXDef. Workstation Application - Def. workstation applicationERPRS5K944135/SMBA0/V_TDWP_1_B1D4_J0A/SMBA0/V_TDWP_1_O1D4_J0A/SMBA0/V_TDWP_1_I1D4_J0ASMBA0_V_TDWP_1_O1D4_J0A_223.txtSMBA0_V_TDWP_1_B1D4_J0A_223.txtSPROXXXXXXXXXXXXXXXXXXXXXXXXXXXxDef. Workstation Application - Def. workstation applicationERP/SMBA0/V_TDWX_1_B1D4_J0B/SMBA0/V_TDWX_1_O1D4_J0B/SMBA0/V_TDWX_1_I1D4_J0BSMBA0_V_TDWX_1_O1D4_J0B_223.txtSMBA0_V_TDWX_1_B1D4_J0B_223.txtSPROXXXXXXXXXXXXXXXXXXXXXXXXXXXDownload and Installation of EasyDMERPXXXXXXXXXXXXXXXXXXXXXXXXXXXDownload of EasyDM (Manual Step)ERP/SMB15/EDM_223_01XXXXXXXXXXXXXXXXXXXXXXXXDownload of EasyDM (Manual Step)(JP)ERP@%DOCFOLDER%SMB17_EDM_223_01.docXXDownload of EasyDM (Manual Step)ERP@%DOCFOLDER%SMB15_EDM_223_01.docXXXDownload of EasyDM (Manual Step)ERP@%DOCUMENTATION%Download_of_EasyDM_223.docXXDownload of EasyDM (Manual Step)ERP/SMB38/EDM_223_01X/SMB38/EDM_223_01XXDownload of EasyDM (Manual Step)ERP/SMBMY/EDM_223_01X/SMBMY/EDM_223_01XInstallation of EasyDM (Manual Step)ERP/SMB15/EDM_223_02XXXXXXXXXXXXXXXXXXXXXXInstallation of EasyDM (Manual Step)(JP)ERP@%DOCFOLDER%SMB17_EDM_223_02.docXXInstallation of EasyDM (Manual Step)ERP@%DOCFOLDER%SMB15_EDM_223_02.docXXXInstallation of EasyDM (Manual Step)ERP@%DOCUMENTATION%Installation_of_EasyDM_223.docXXInstallation of EasyDM (Manual Step)ERP/SMB38/EDM_223_02X/SMB38/EDM_223_02XXInstallation of EasyDM (Manual Step)ERP/SMBMY/EDM_223_02X/SMBMY/EDM_223_02XTrouble ShootingERPXXXXXXXXXXXXXXXXXXXXXXXXXReferred SAP NotesERP/SMB15/EDM_223_03XXXXXXXXXXXXXXXXXXXXXXReferred SAP Notes(JP)ERP@%DOCFOLDER%SMB17_EDM_223_03.docXXReferred SAP NotesERP@%DOCFOLDER%SMB15_EDM_223_03.docXXXReferred SAP NotesERP@%DOCUMENTATION%Referred_SAP_Notes_223.docXXReferred SAP NotesERP/SMB38/EDM_223_03X/SMB38/EDM_223_03XXReferred SAP NotesERP/SMBMY/EDM_223_03X/SMBMY/EDM_223_03XTest/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, enter what specifically needs to be localized.

Comment: localization teams can use this to communicate with each other and within a localizationHere, 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 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- XIUse this column to flag demo data nnd any configuration activities that have demo data as a prerequisiteFlag activities that are relevant for Kayak implementationFor 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&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