customer extention

[Former Member]

hi,

in my business scenario i want to allow the user only to extend the customer as we are creating customer outside of SAP and want to only extend the customer in SAP. have checked with BASIS there is no any separate authorization object to do so. can anyone help me on this.

Thanks

Ashwini

[Former Member]

Hi SRK,

don't want to create Z development.

Thanks

Ashwini

[VeselinaPeykova]

Since you pointed out that you do not wish to use any custom developments, I will skip the most obvious solution to the problem .

I do not think that you can achieve this functionality only with customizing settings.

An alternative is to establish an approval process for customer master data maintenance and create the customer views only after the change is approved.

You can establish the approval either via a ready-to use workflow (there are some solutions available by extrenal vendors that can do what you ask) or use mail communication of some sort to receive the approval out of SAP.

In case of out-of-the-system approval - the customer master extension should be perfromed not by an end user, but by a master data specialist who uploads a validated template filled by the requestor.

[Former Member]

thank you for your valuable reply...can you suggest any userexit for this.

[VeselinaPeykova]

My understanding so far was that you do not wish to go with the developmet approach.

My suggestion was not exacttly to use a user exit, but to craft a z-transaction, that calls VD01, where you have a different selection screen.

The user should specify the customer number that he wants to extend and he should also specify the sales area to create. The program should execute a check upon user entry in KNB1 to get the list of company codes for the customer. Then can check in TVKO what are the assigned sales organizations and get a list of allowed sales areas by cross-check in TVTA. If the user presses F4, he can get the list for selection, if he enters the sales area manually, the program should check if he entered allowed sales area. If all checks are ok, the user can proceed with the normal screen processing that you get from VD01. Creation with reference to a different customer can also be supported.

Then you give authorization only for this program, but not for VD01 to the users.

It does not seem a really complicated development, but still requires some ABAP effort and minor testing.

Regarding the user exit for additional checks at customer creation - you can try to use SAPMF02D I guess and build your logic there, but I think that it is executed at save, which is a disadvantage compared to checks at the selection screen.

[VeselinaPeykova]

What do you mean precisely by customer extension - please specify the views and fields that the user should be allowed to update.

[Former Member]

hi,

user should not have access to create new customer in XD01 only extension. ex- if customer 10002 having account group XYZ is defined for sales area 10002 - 01 - 02 in company code 100 then system should allow to extend for sales area 10002-01-03 in same company code. but if user is trying to create new customer then system should throw an error msg. like u r not allowed to do so or something like that.

regarding the fields and screen everything will be the same as v have for the customer master.

Thanks

Ashwini

[ravi_kumar100]

Hi,

In SHD0 create a transaction/screen variant making the reference Customer / Company code/ Sales Org, Distribution channel & Reference Division as required field .

Regards,

SRK

[VeselinaPeykova]

It is a bit more complicated, because he should specify the same customer and company code as reference. Also it is important if the user has authorization only for the sales organizations assigned to a single company code - otherwise nothing would stop him from creating sales area data for the same customer without having the corresponding company code view.