Register Login

SAP POS DM Authorization Values For Functional Modules

Updated May 19, 2018

Hello Experts,

I have been trying to use the SAP Customer Activity Repository (SAP POS DM) but have failed to authorize the system for communication with other SAP Modules. Could you tell me the values of the Authorization object S_RFC for the following cases?

1.LPA (Loss Prevention Analytics)
2.DMF (Demand Management Foundation) provided through task processing (e.g. 0050), for sales reporting
3.IM (Inventory Management) for movement of goods to be reported to ERP, provided through task processing (e.g. 0017) 
4.CCS (Credit Card Settlement), provided to processing of tasks (e.g. 0015)
5.Processing of Oil and Gas SSR Payment Card data in ERP, provided through the processing of tasks (e.g. 0101)


Comments

  • 18 Apr 2016 2:01 pm Abhijeet Mudgal Best Answer

    Specific Values of the authorization object S_RFC are required because the values that are inputted into this note need also to be listed in the executing user’s profile in the target system. Here are the values of the mentioned scenarios for the authorization object S_RFC:

    Loss Prevention Analytics (LPA)

    RFC_TYPE: FUNC
    RFC_NAME: RSDRI_INFOPROV_READ_RFC, RSSEM_CHAVL_READ_ALL, RFC_READ_TABLE
    ACTVT: 16
    RFC_TYPE: FUGR
    RFC_NAME: RSAB, RSPLS_ALVL_RFC , RSBAPI_IOBJ, SDTX
    ACTVT: 16

    Demand Management Foundation (DMF)

    RFC_TYPE: FUNC
    RFC_NAME: /DMF/BI_SALES_DATA, FUNCTION_EXISTS

    ACTVT: 16

    Inventory Management (IM)

    RFC_TYPE: FUNC
    RFC_NAME: BAPI_GOODSMVT_CREATE, BAPI_TRANSACTION_COMMIT, BAPI_TRANSACTION_ROLLBACK
    ACTVT: 16

    Forecasting & Replenishment (F&R)

    RFC_TYPE: FUNC
    RFC_NAME: /FRE/BIF_TSD_INBOUND2
    ACTVT: 16

    Credit Card Settlement

    RFC_TYPE: FUNC
    RFC_NAME: TRIGGER_CC_SUBSYSTEM
    ACTVT: 16

    Oil & Gas SSR Payment Card data processing in ERP

    RFC_TYPE: FUNC
    RFC_NAME: BAPI_BLPCP_UPLOAD, BAPI_TRANSACTION_COMMIT
    ACTVT: 16

    It should also be noted that for certain scenarios, it is important to provide the values for these additional authorization objects:

    Values for authorization object S_RS_AUTH:

    Loss Prevention Analytics (LPA)  -  Pattern Lookup within Transaction Viewer & Journal Viewer

    BIAUTH:  (LPA support role defined using transaction RSECADMIN for relevant characteristics/dimensions of LPA InfoProvider, e.g. Characteristic 0LPA_PTRN of InfoProvider 0LPA_C01, etc.)
    Values for authorization object S_TABU_NAM:

    Loss Prevention Analytics (LPA)  -  Cashier Lookup
    TABLE: /BI0/SRPA_OID         (representing characteristic 0RPA_OID)

    ACTVT: 03

    Values for authorization object O_OIRE_DTF:

    Oil & Gas SSR Payment Card data processing in ERP

    ACTVT: 01


×