Page tree
Skip to end of metadata
Go to start of metadata

Purpose

You execute the transaction WB2R_SC and/or WB2R_SV and you would like to know what kind of authority check is performed during the settlement. This document provides information on the authority check logic in CCS area.

Overview

Due to a difference in program logic and the customizing paths, the configuration requirements depend on whether you have an S/4HANA or ERP system. Please refer to one of the below sections („CCS Authority check logic in S/4HANA” or  ”CCS Authority check logic in ERP”) for a description of the program logic, which is relevant for your scenario.

CCS Authority check logic in S/4HANA

In order to ensure that the user is only allowed to settle such condition contract, for which he/she has proper authorization, the program carries out an authority check by verifying the following authority objects and values:

Contract type:

  • W_COCO
    • ACTIVITY
    • CONTR_TYP

SD and MM-sided org. data (if both sales org. and purchase org. was maintained in the condition contract header):

  • W_COCO_ORG
    • ACTIVITY
    • EKORG
    • EKGRP
    • VKORG
    • VTWEG
    • SPART

MM-sided org. data (if only purchasing org. was maintained in the condition contract header):

  • W_COCO_ORG
    • ACTIVITY
    • EKORG
    • EKGRP

SD-sided org. data (if only sales org. was maintained in the condition contract header):

  • W_COCO_ORG
    • ACTIVITY
    • VKORG
    • VTWEG
    • SPART

In WB2R_SC / WB2R_SV transactions for the settlement of the condition contract activity numbers 03 and 84 are being used.

In order to make sure that the user can settle the corresponding condition contract, it has to be ensured that he/she has authorization in accordance with the above logic and the condition contract data. 

CCS Authority check logic in ERP

In order to ensure that the user is only allowed to settle such condition contract, for which he/she has proper authorization the program carries out an authority check by verifying the following authority objects and values:

Contract type:

  • W_COCO
    • ACTIVITY
    • CONTR_TYP

SD and MM-sided org. data* (if both sales org. and purchase org. was maintained in the condition contract header):

  • W_COCO_ORG
    • ACTIVITY
    • EKORG
    • EKGRP
    • VKORG
    • VTWEG
    • SPART

MM-sided org. data* (if only purchasing org. was maintained in the condition contract header):

  • W_COCO_ORG
    • ACTIVITY
    • EKORG
    • EKGRP

SD-sided org. data* (if only sales org. was maintained in the condition contract header):

  • W_COCO_ORG
    • ACTIVITY
    • VKORG
    • VTWEG
    • SPART

*Please note that an authorization check on the organizational data only takes please if the relevant check (’Authority Check On Organisational Level’ flag, technical name: TWCBFEATURES-ORG_AUTH) was set in the Customizing under the following path:

SPRO --> Logistics - General --> Global Trade Management --> Compensation Management --> Activate Functions

If the above field was set with an initial value, then the authority check will only be carried out by checking auth. object W_COCO.

In WB2R_SC / WB2R_SV transactions for the settlement of the condition contract activity numbers 03 and 84 are being used.

In order to make sure that the user can settle the corresponding condition contract, it has to be ensured that he/she has authorization in accordance with the above logic and the condition contract data. 

Relevant program parts

In S/4HANA:

  • method GET_CC_AUTHORITY_WHERE_CLAUSE (CL_WLF_SELECTION_TOOLS)
  • method DO (CL_WCB_AUTHORITY_CHECK)

In ERP:

  • method GET_CC_AUTHORITY_WHERE_CLAUSE (CL_WB2_SELECTION_TOOLS)
  • method DO (CL_WCB_AUTHORITY_CHECK)

Related SAP Notes/KBAs

The current authorization logic was implemented with the following notes:

SAP Note 2571308 - Company code is not always taken into account

SAP Note 2630582 - Condition contracts are not selected

  • No labels