Help required on BP-ERP603V5

[Former Member]

Hi Gurus,

I have upgraded Dev, Qua from ECC 6.0 to EHP5 successfully, but problem is after upgrade i came to know that below two components are installed in dev (before upgrade) but not installed in Qua, Prod systems.

Now when i import transport request into Qua am recieving error as components mismatch.

BP-ERP603V5, BP-INSTASS600V6

what should i do now, shall i install these components in Qua (now it is at EHP5 SP08), Prod(ECC 6.0)?

how do i go ahead? please suggest me.

Thanks,

Venkat

[paul_power · Accepted solution]

Hi Venkat,

With SAP Best Practices, SAP provides configuration packages for defined
scenarios. The configuration can be implemented automatically
via the Solution builder tool, which is delivered via the Add-On
BP-SOLBLD. This tool runs the eCATTs and BC-Sets (which are in the
BP-ERP Add-On) to transfer the prepared configration into the according
ERP tables. In parallel the system writes the transport requests
as it would do if one would implement the same configuration manually
calling the transactions and IMG nodes as described in the configuration
guides.
This is the reason, why the BP* Add-Ons are not required on systems
that are connected via transport routes. After import, the tool and
the "carriers" (BC-Sets and eCATTs) become obsolete.

The Business Functions in all involved system need to be activated
as defined in the Quickguide per solution, as they activate the ERP
functionality required in the defined scenarios.

The transports that are created during the activation procedure, use the
ERP standard functionality. This does not include some objects like e.g.
calendards and number range objects. Such objects need to be transferred
manually, if required. Master data is not transported via customizing
or workbench requested. For this, other distribution channels exist, e.g
via ALE. Please find details e.g. in
http://help.sap.com/saphelp_nw70/helpdata/en/0b/2a6196507d11d18ee90000e8366fc2/frameset.htm

When the transport is triggered using the Transport Management System
(STMS), the system does not only call a "TP IMPORT ..."; some other
things are done. For example, when the component check option is active
a "TP IMPORTPREVIEW SUBSET..." is called before the "TP IMPORT ...".
With this "TP IMPORTPREVIEW SUBSET..." command, the component check is
performed, and if it fails, the "TP IMPORT..." is not triggered and the
pop-up with the "request do not match the component version of the
target system" is displayed (unless the umode for "Ignore Invalid
Component Version" has been selected. If this is the case, the
component check is not performed and the "TP IMPORT ..." is triggered).

Please see the KBA note 1688610. In this note, there explain more
details on the setting for your requirement.

The component version check feature will check all the components
(include application and SAP_BASIS versions, etc.). So if on part of
them are in different versions, the check will not be passed.
That means there is unable to make it "specific" to check for a
particular component.

Thus, you would still keep getting this entry and need to judge whether to ignore the component version check and or whether it is necessary to install the BP* Add-Ons other
systems(beside DEV system).

Hope this is of some help.

Regards,

Paul

[Former Member · Accepted solution]

Hi Paul,

Thanks a lot for detailed explanation.

If i want to install BP* addons on QA, Prd which version do i need to install?

because Dev is having BP-ERP603V5, BP-INSTASS600V6. So shell i install new one or old one?

which one is good? if i install new addons is there any version mismatch again?

Thanks in advance.

Venkat

[Former Member · Accepted solution]

Hi,

Any suggestion for this?

Thanks,

Venkat