天天看點

component set load logic - why coms_pcat_bob is accessed during product search

During product search POC test, I found the following COM table is accessed.

component set load logic - why coms_pcat_bob is accessed during product search

The reason is, in my test code, I use component set PROD_ALL:

component set load logic - why coms_pcat_bob is accessed during product search

You can define component set in this customizing:

component set load logic - why coms_pcat_bob is accessed during product search

Here we can find that PROD_ALL contains lots of other component like BP and obsolete component like CRMPME:

component set load logic - why coms_pcat_bob is accessed during product search

One order WebUI application has used another component set ONEORDER:

component set load logic - why coms_pcat_bob is accessed during product search

Where PROD component is included.

component set load logic - why coms_pcat_bob is accessed during product search

As a result, in the future in our unit test code, we should always use the same component set as used in one order application: ONEORDER. The component set PROD_ALL should never be used any more for current scope.

繼續閱讀