Characteristics Compatible with Drag&Relate (SAP Library

Characteristics Compatible with Drag&Relate

Definition

Characteristics delivered with Business Content that have Business Object Repository (BOR)object types assigned.

By default you can only use the Drag&Relate function for InfoObjects with assigned BOR object types, in which, among other things, the keys match exactly Objects that are compatible with Drag&Relate are now listed.

InfoObjects and BOR objects that are not listed are not compatible with Drag&Relate.

Note

However if you do want to use InfoObjects that are not listed for Drag&Relate scenarios first check whether you are build the scenarios using the report-report interface. If this is not possible then you can go into the metadata modeling in SAP BW and make these InfoObjects compatible with Drag&Relate. See Working with BOR Objects and BW-InfoObjects.

Structure

The following characteristics are compatible with Drag&Relate:

Basic Characteristic	Description	BOR Object Type	Characteristics that reference the basic characteristic
0ABCPROCESS	Business process number	BUS1036	0ABC, 0ABCPROCESS, 0PART_ABCPR, 0RECV_PROCS, 0SEND_PROC
0APPLICANT	Applicants	APPLICANT	0APPLICANT
0APPR_REQU	Appropriation request	BUS2204	0APPR_REQU
0ASSET	Asset subnumber	BUS1022	0ASSET
0BPARTNER1	Business partner	BUS1006	0BBP_APPROV, 0BBP_BIDDER, 0BBP_RECIPT, 0BBP_REQSTR, 0BBP_VENDOR, 0BE_BILLORG, 0BP_ACTIVIT, 0BP_CONS, 0BP_CONTPER, 0BP_EMPLO, 0BP_RESPPER, 0BPARTNER, 0BPARTNER1, 0BPARTNER2, 0CFM_BP_CON, 0CFM_BP_DBK, 0CFM_BP_GUA, 0CFM_BP_ISS, 0CRM_AGNT, 0CRM_AGNT2, 0CRM_BILLTO, 0CRM_CAGNTB, 0CRM_COMPET, 0CRM_EXC_CC, 0CRM_PAYERP, 0CRM_PLANTP, 0CRM_PROSPE, 0CRM_SALESP, 0CRM_SALPAR, 0CRM_SHIPTO, 0CRM_SND_PT, 0CRM_SOLDTO, 0CRM_VENDOR, 0FS_BP_LO, 0FS_BP_RSK, 0IS_CLAIMNT, 0IS_PAYE, 0IS_POLHOL, 0IS_REPSHOP, 0MA_OPPINBP, 0MA_RSPBP, 0MSTRTENANT, 0PH_BPARTNE, 0PRCA_RESP, 0REQUESTER, 0STAKEHOLD
0COORDER	Order number	BUS2075 BOR super type: _ORDER	0COORDER, 0CRET_ORDER, 0DEBT_ORDER, 0INVORDER, 0PART_COORD, 0RECV_ORDER, 0SEND_ORDER
0COSTCENTER	Cost center	BUS0012	0CCT, 0COSTCENTER, 0CRET_CCTR, 0DEBT_CCTR, 0HC_COSTPER, 0HC_COSTREQ, 0HC_COSTREV, 0MAST_CCTR, 0PART_CCTR, 0RECV_CCTR, 0REQU_CCTR, 0RESP_CCTR, 0SEND_CCTR
0CS_ORDER	Service order	BUS2088 BOR super type: _ORDER	0CS_ORDER
0CUSTOMER	Customer Number	KNA1	0AU_ENDCU, 0AU_VHORD, 0BILLTOPRTY, 0COMPETITOR, 0CUST_HIE01, 0CUST_HIE02, 0CUST_HIE03, 0CUSTOMER, 0DEBITOR, 0HT_INRSPTN, 0HT_PARTNER, 0HT_PRTBRCH, 0HT_RESCUST, 0INT_CUST, 0PAYER, 0RT_CUSTPL, 0SHIP_TO, 0SOLD_TO
0DOC_NUMBER	Sales document	BUS2032 BOR super type: _SALESDOC	0DOC_NUMBER
0EMPLOYEE	Responsible Employee	BUS1065	0CNTCTEMPL, 0CP_EMPLOY, 0EMPL_ACCNT, 0EMPLOYEE, 0REFEMPL, 0TRAVELER, 0UC_WEMPL1, 0UC_WEMPL2, 0UC_WEMPL3
0EQUIPMENT	Equipment number	EQUI	0EQUIPMENT, 0UC_VEHICL1, 0UC_VEHICL2
0FUNCT_LOC	Functional location	BUS0010	0FUNCT_LOC
0INSP_LOT	Inspection lot number	BUS2045	0INSP_LOT
0MATERIAL	Article	BUS1001	0ASSEMBLY, 0CNSTR_MAT, 0COMPONENT, 0DM_MATDP, 0DM_MATLD, 0MAT, 0MATERIAL, 0MPN_MATNR, 0PLMPRODUCT, 0RT_GENMAT, 0UC_CONTCAT, 0UC_WCAT, 0UCDEV_CAT
0PLANT	Plant	BUS0008 BOR super type: _PLANT	0MAINTPLANT, 0MCHAR_PLNT, 0ME_PLANTIM, 0MOVE_PLANT, 0P_PLANT, 0PLANPLANT, 0PLANT, 0PLANT_COMP, 0PLANT_P, 0PLANTFROM, 0PLANTTO, 0QMWCPLANT, 0SUPP_PLANT, 0WDRW_PLANT
0WORKCENTER	Work center/ resources	BUS0011	0WORKCENTER

Note

BOR Super Type:

There are data elements that represent different objects depending in their use in an SAP transaction (Screen) For example, a request number can be either an internal request or a customer request. These are two different BOR objects, but the same semantic (request number). So that the screen program (which only knows the data element) also knows which type of request this is, two different objects are assigned to the data element. To identify the object type the screen program writes the super type in the URL. The application has to deliver a dedicated function module that has to be recorded in the super type. The super type groups object types that have the same identifying data element.

You can determine whether a BOR object is assigned to a super type in transaction SPO0 in the ERP system.

To be sure that D&R from a SAP transaction to a BEx Web Application works both for transactions with BOR type and for transactions with the super type, SAP recommends that you carry out mapping in the Structure link Relationship Editor, both between InfoObject and BOR type, and between InfoObject and BOR super type.