S/4 HANA 1511 Best Practice installation

First of all need to follow to SAP note

2246714 - SAP S/4HANA, on-premise edition 1511 - SAP S/4HANA ON-PREMISE 1511 FP stack 01 (02/2016) content activation note

1. transport the latest data files and cofiles

1. Run tcode /SMB/BBI import XML

1. Choose USV2

1. After import XML, check the items

1. Import installation data

1. Import failure, try import via local zip file

1. Import failure.

Conclusion: Version mis-match. Will need to patch S/4 first then re-do the BP installation.

Tried to install USV1 version, still got errors

Follow SAP note

   2292425 - Removal of Language-dependent SAP Best Practice content

Upload SAP note

Delete language

As per note

 2248019 - SAP S/4HANA On-Premise 1511 - SAP S/4HANA Server SPS00 (11/2015) content activation note

It highlighted the following

Please select one of the referenced SAP notes for further details and latest information about the DE and US localizations:

    2231568 - SAP Best Practices for S/4HANA, on premise edition U.S.A (USV1)
    2211113 - SAP Best Practices for S/4HANA, on premise edition Germany (DEV1)

In the above mentioned SAP notes you will find the "Software and Delivery Requirements documentation" and the "Administration Guide for SAP S/4HANA OP Solution Implementation".

Please check the Administration Guide, there you will find all steps and procedures needed for activating the SAP best practices content.

Please apply the following SAP notes before content activation takes place in your system:

2257369 - Missing entries in table T160M leads to activation errors during solution builder content activation

2269628 - Unjustified error message in settlement

Please find here an overview of the known issues regarding the SAP S/4HANA On-Premise 1511 - SAP S/4HANA Server SPS00 (11/2015) content activation (the related workaround documents can be found attached either to this note or the package version notes that are reference to this note):
Type     Countries     Building Block / Scope Item     Description     activity type     activity / transaction     error     solution
Building Block     XX     JA2, J88, BN6, BN5,BMA, BN8, BN9, BRC, BLI     All BBs dealing with the creation of Business Partner Sample Data     eCATT     /SMB99/CL_MD_BP_XD01_O001_J01
/SMB99/CL_MD_BP_XK01_O001_J01     Error in eCATT command FUN BAPI_TRANSACTION_COMMIT
DQM Error Code: T034 Locacation Code: 018     see manual workaround document: 1511_OP_ALL_XX.docx
Building Block     XX     BJW     Production Planning and Control, Global Setting     IMG     SIMG_CFMENUOLMSOMT0     (Warning Message) Check whether a corresponding database index exists     When the activation stops, hit the Enter key on your keyboard and it will continue.
Building Block     XX     BMX     Procurement Contract     IMG     SIMG_CFMENUOLMEOMEF     @8O@ Table/View V_T161A: No higher-level entry for 212     see manual workaround documentation
Building Block     XX     J90     Globalization Content from Client 000     IMG     SIMG_CFMENUSAPCOY17     Enter field with a maximum length of 000011
Object Name =V_005_B
Table Key =<Your Client ID>CA
Entry 226CA from V_005_B of the Business Configuration Set was not added
Object Name =V_005_B
Table Key =<Your Client ID> CA
Activation of customizing object V_005_B with errors     see manual workaround documentation
Building Block     XX     JA2       Sample Master Data Business Partners, Local     eCATT     /SMB99/CL_MD_BP_XD01_O001_J01     V_LOGTEXT = /SMB99/CL_MD_BP_MAINTAIN_I001: Required entry field KONDA is blank in table KNVV     see manual workaround documentation
Scope Item     DE, US     BJ5     Make-to-Stock Production - Discrete Industry     process step     CO03     Display production order using transaction CO03, and select the menu entry "Goto --> Costs --> Itemization" (or "Goto --> Costs --> Cost Component Split") - a runtime error will occur.     see manual workaround documentation
Building Block     XX     J10     Materials Management - Central Settings     IMG     OLMEOMGS_2     OLMEOMGS_2        Define Release Procedure for Purchase Orders - Release Strategy Entry S1 MA  does not exist in T16FC (check entry)     see manual workaround documentation
Building Block     XX     BD7     Credit Management     IMG     SCMG_CASETYPE     When activating this activity, screen Area ID might appear with 3 options.     see manual workaround documentation
Building Block     XX     J22     Dispute Management     IMG     DM_SCMGV_CASETYPE     When activating this activity, screen Area ID might appear with 3 options.     see manual workaround documentation
Building Block     XX     J25     Collections Management     IMG     COL_SCMGV_CASETYPE     When activating this activity, screen Area ID might appear with 3 options.     see manual workaround documentation
Building Block     XX     J02     External Financial Accounting     IMG     SIMG_CFMENUORFBOBY9     This is neither an activation error nor a testing error. This is about correcting wrong content.
All S4/HANA standard material groups except E001, E002, E003 and E004 have no valuation class assigned.     see manual workaround documentation
Scope Item     all     J13     Service & Material Procurement for Project Based Services     n.a.     App Manage PO     Open app Manage PO -> search for an existing PO -> NO ATTACHMENT available in this purchase order     see manual workaround documentation

 Workaround documents:

All workaround documents for cross country Scope items/Building blocks are attached to this note. Please see attachments section of this note.

All workaround documents for country specific Scope items/Building blocks are attached to the respective country specific notes given at the beginning of this note in ‘Solution’ area and also here:
2231568           SAP Best Practices for S/4HANA, on premise edition U.S.A (USV1)
2211113           SAP Best Practices for S/4HANA, on premise edition Germany (DEV1)

Activated the following business functions

Try to activate the implementation again, errors about eCATT. These eCATT should have come with the transport in the very first step. However, again, because of version mismatch, the error occurs. We'll have to find the proper transport, let say, for example, contain object /SMB99/HRRP_REP_O001_J01