Quantcast
Channel: SCN : Blog List - SAP CRM: Webclient UI - Framework
Viewing all articles
Browse latest Browse all 195

Enhance mass change process for Sales Orders in Web UI

$
0
0

SAP_BASIS SAPKB73105

SAP_ABA    SAPKA73105

WEBCUIF    SAPK-73105INWEBCUIF

BBPCRM     SAPKU70204

 

Hi,

Well I hope everybody knows about what is about the GUI transaction MASS, for the ones who doesn’t know, is a transaction to do mass modification, in CRM we can use it to modify sales orders (header and Item).

Wait! Have you said GUI transaction? GUI is not supported anymore in CRM

MASS in GUI dumps when you try to modify massively sales order items, the dump is caused by a standard error, in a normal situation this will be fixed by SAP, but is not supported so you should go through Web UI yes or yes.

 

soooooo...Where is the MASS alternative in the Web UI? Well… is not very intuitive, you can find it under any Business role which has the following logical Links related:

 

IPM-ACQ-MC

IPM-SLS-MC

MD-IP-MC

SLS-RBM-SR

SLS-SLM-SR

SRV-MCP-SR

 

Business roles:

DETECTIVE

IPMRIGHTSMAN

ITSERVICEPRO

LOY_ADMIN

LOY_PRO

PROFSERVICES

SALESPRO

SERVICEPRO

SPL

TPM_PRO

UTIL_DSM_INP

UTIL_DSM_MGR

UTIL_SALES

 

I’m not going to explain how it works from a “user point of view”, it's very intuitive, I will focus how you can add new fields.

 

To manage the fields which will be updated you should go to the following customizing path( I recommend read the help, it's very complete):

 

image1.png

 

In the sales order scenario you will have to select the structures CRMT_UIU_SLSORD_MASSUPDATE_HDR for the header and CRMT_UIU_SLSORD_MASSUPDATE_ITM for the items, my scenarios are header related so if you check in the dictionary the structure CRMT_UIU_SLSORD_MASSUPDATE_HDR you will see this structre has one customer include CRMT_SALESORD_MASSUPDATE_HEAD2 which also has another CI CRMT_SALESORD_MASSCHNG_HEAD2 I will give you the reason why I’m explaining this in the first scenario, don’t be impatience!

 

First scenario: Add an already existing Standard field Currency

 

The component/view for the Header mass process is the BT115MU_SLSO/ChangeHeaderForm which has the context node NEWVALUES, the context node is bind to the CUCO HeaderMassChangeCuCo context node: NewValues in the method IF_BSP_MODEL~INIT of the cuco context node you have defined which fields will be available in the Web UI configuration.

 

image2.png

 

Do you remember the structure CRMT_SALESORD_MASSCHNG_HEAD2? yes, of course! is included in the structure CRMT_SALESORD_MASSUPDATE_HEAD2, so you can not make available in the Web UI any of the fields of the structure CRMT_SALESORD_MASSUPDATE_HEAD2 because the field will be duplicated so you won’t be able to activate the CI, this is the case of the currency, the solution is add the same filed with the ZZ / YY prefix.

 

image3.png

 

image4.png

image5.png

 

Once the field is in the CI and everything is active we need to enhance the CN NEWVALUES of the view ChangeHeaderForm in order to add the field as attribute:

 

image6.png

 

So now is available in the Web Client, notice that you will need to code the search help in case that you need it (usually yes) via GET_V method.

The final step is make the new field available in the mass changes customizing, we create the following entry:

 

image7.png

 

And that’s it!

 

I was a little upset because I don’t like to duplicate things, so I raised a message to SAP in order to clarify this, they answered “for technical reasons this is the right procedure” so if you want to make available in the Web UI any of the fields which are directly added in the CI CRMT_SALESORD_MASSUPDATE_HEAD2 you must duplicate the field with ZZ / YY prefix in the  CRMT_SALESORD_MASSCHNG_HEAD2 and also duplicate the customizing entry for your field. Nice, isn’t it?

 

Scenario 2: Adding BP which points to a partner function

 

This is a very easy scenario, first you enahance the CRMT_SALESORD_MASSCHNG_HEAD2

image8.png

Then add the field in the customizing:

 

image8.png

 

 

image9.png

In this case the Object Key is the partner function id defined in the partner determination procedure config.

The rest UI related steps are like in scenario 1.

 

I hope you find this useful.

 

Cheers!

 

Luis



Viewing all articles
Browse latest Browse all 195

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>