Attribute

Description and
Example Value

Definition

System-Dependent

ACS

System alias for accounting systems

Example value: ABCCLNT123

Specifies the backend system where the account assignment is checked. This attribute is required for:

·         Invoices without purchase order reference

·         Local invoices

(In the case of a vendor, the backend system is determined using the attribute VENDOR_ACS).

We recommend that you define this attribute at a high level in your organizational plan.

Prerequisite: You must have defined the backend system during Customizing.

Path in the Implementation Guide (IMG): Supplier Relationship Management ® SRM Server ® Technical Basic Settings ® Define Basic Settings.

ADDR_SHIPT

Ship-to address

Example value: 12345

Default ship-to party address in purchase order.

Enter at least one ship-to address and set it as the default address.

ü

AN1

Asset

Example value: ABCCLNT123\000000001111

Specifies the asset in the backend system. Default value for account assignment when creating shopping cart or lean purchase order.

ü

AN2

Asset subnumber

Example value: Q4CCLNT300\1234

Defines the asset subnumber in the backend system. Default value for account assignment when creating shopping cart or lean purchase order.

ü

ANK

Asset class

Example value: QW4CLNT100\00001000

Defines the asset class in the backend system. Default value for account assignment when creating shopping cart or lean purchase order.

ü

ANR

Order

Example value: ABCCLNT123\000000000040

Defines the order in the backend system. Default value for account assignment when creating shopping cart or lean purchase order.

ü

APO

Sales order item

Example value: Q4CCLNT300\123456

Defines the sales order item in the backend system. Default value for account assignment when creating shopping cart or lean purchase order.

ü

APPRV_LIM

Approval limit

The value up to which a user is allowed to approve.

You define this attribute using tab card Extended attributes.

Menu path in the Implementation Guide (IMG):
Supplier Relationship Management ® SRM Server ® Cross-Application Basic Settings ® Organizational Management ® Change Organizational Plan.

AUN

Sales order

Example value: ABCCLNT123\000000000333

Specifies the sales order in the backend system. Default value for account assignment when creating shopping cart or lean purchase order.

ü

BSA

Transaction type: Shopping cart follow-on document

Example value: ABCCLNT123\ECA3

Defines the transaction type in the respective system for follow-on documents from shopping carts.

The attribute needs to be defined once per system, for the local SRM system and for all connected backend systems.

ü

BUDGET

User budget

Amount available to an employee for purchases. Required for the Purchasing Budget Workflow.

ü

BUK

Company code

Example value: QW4CLNT100\1000

Company code in the backend system.

Generally, the user inherits the company code from his/her company. If you want to overwrite the value inherited from the company you should define the company code via this attribute only.

You define the company code of the company for the organizational unit assigned to the company on the Function tab.

Menu path in the Implementation Guide (IMG):
Supplier Relationship Management ® SRM Server ® Cross-Application Basic Settings ® Organizational Management ® Change Organizational Plan.

ü

BWA

Movement type

Example value: ABCCLNT123\123

Defines the type of goods movement in the backend system. This value is required if reservations are to be created in the backend system.

ü

CAT

Catalog ID

Example value: REQUISITE2.8

Defines the catalogs to which a user has access. This attribute has to be defined in Customizing.

Menu path in the Implementation Guide (IMG): Supplier Relationship Management ® SRM Server ® Master Data ® Define Catalogs.

CNT

Cost center

Example value: ABCCLNT123\0000001000

Defines the cost center in the backend system. Default value for account assignment when creating shopping cart or lean purchase order.

ü

COMPANY

Company

Identifies a legally independent section of the company.

This attribute is simulated. The simulated value contains the number of an organizational unit that is indicated as company in the organizational plan.

It identifies an organizational unit as company on the Function tab.

Menu path in the Implementation Guide (IMG):
Supplier Relationship Management ® SRM Server ® Cross-Application Basic Settings ® Organizational Management ® Change Organizational Plan.

CUR

Local currency

Example value: EUR

Default currency of the user

DP_PROC_TY

Transaction type: Direct material

Example value: ECDP

Specifies the transaction type that is used when purchase orders for direct materials are created via BAPI, shopping cart, or bid invitation/bid. You have to maintain this attribute for the responsible purchasing group (see also the attribute TEND_TYPE). The specified transaction type has to correspond to the document type used in the backend system for direct material purchase orders with external number assignment. The value for this attribute can be inherited. For example, purchasing groups can inherit it from their purchasing organization.

Path in the Implementation Guide (IMG):
Supplier Relationship Management ® SRM Server ® Cross-Application Basic Settings ® Define Transaction Types.

ü

EXT_ITS

Current ITS of an external partner

Example value: http://abc.firma.com/wgate/

Specifies the ITS server for an external business partner (bidder or vendor). For example, an ITS server behind the firewall.

FORWARD_WI

Flag: Forward work item

Example value: X

Indicator: Specifies whether work items are to be forwarded as e-mails.

IS_COMPANY

Indicator: Company

Indicator: Identifies an organizational unit as independent legal entity.

This attribute is simulated. You set this indicator for an organizational unit on the Function tab by selecting Company.

You should define an organizational unit high up in the organizational plan as company by setting this indicator. If you have further organizational units in a lower level of your plan that represent subsidiaries, you also need to set this indicator.

Menu path in the Implementation Guide (IMG):
Supplier Relationship Management ® SRM Server ® Cross-Application Basic Settings ® Organizational Management ® Change Organizational Plan.

ü

IS_PGR

Indicator: Purchasing group

This indicator specifies that an organizational unit is identified as purchasing group.

This attribute is simulated. You set this indicator on the Function tab.

Menu path in the Implementation Guide (IMG):
Supplier Relationship Management ® SRM Server ® Cross-Application Basic Settings ® Organizational Management ® Change Organizational Plan.

IS_POR

Indicator: Purchasing organization

This indicator specifies that an organizational unit is identified as purchasing organization.

This attribute is simulated. You set this indicator on the Function tab.

Menu path in the Implementation Guide (IMG):
Supplier Relationship Management ® SRM Server ® Cross-Application Basic Settings ® Organizational Management ® Change Organizational Plan.

ITS_DEST

Current ITS of a user

Example value: http://abc.firma.com/wgate/

Current address of the user’s Internet access (supplied automatically)

KNT

Account assignment category

Example value: CC

Default value for account assignment when creating shopping cart or lean purchase order.

The default value for the account assignment is determined on the basis of the value for this attribute (for example CC – cost center) in connection with the relevant account assignment object (in this example CNT cost center).

Note: In Customizing, no check occurs to establish whether the value for the relevant account assignment object is maintained.

LAG

Storage location

An organizational unit that allows you to differentiate between different material stocks within a plant.

You define this attribute on the Extended Attributes tab.

NET

Network

Example value: ABCCLNT123\000000600003

Specifies the network in the backend system. Default value for account assignment when creating shopping cart or lean purchase order.

ü

PHOTO

The URL address of a photograph

The URL address of a photograph or graphic for display on the initial screen.

PM_ARWRK

Plant for work center

Example value: ABCCLNT123\1234

Plant in which the executing work center is located.

This attribute is used as a selection criterion when searching for orders in the backend system.

ü

PM_AUART

Order type

Example value: ABCCLNT123\PM01

Order types distinguish orders according to their use, for example, maintenance and service orders.

This attribute is used as a selection criterion when searching for orders in the backend system.

ü

PM_GL_ACCT

PM: Default G/L account

Example value: ABCCLNT123\417000

Default value for the G/L account in the component detail data.

ü

PM_IPHAS

Phase

Example value: ABCCLNT123\0

Phases subdivide the life cycle of an order into several subsections (for example, created and released) and determine which activities are allowed for the order in each section.

This attribute is used as a selection criterion when searching for orders in the backend system.

This is a mandatory attribute.

PM_IWERK

Planning plant

Example value: ABCCLNT123\1234

Plant at which maintenance tasks are planned and prepared.

This attribute is used as a selection criterion when searching for orders in the backend system.

ü

PM_PUR_GRP

PM purchasing group

Example value: ABCCLNT123\001

Number of the organizational unit that is indicated as the purchasing group in the organizational plan. Default value in the component detail data.

ü

PM_PUR_ORG

PM purchasing organization

Example value: ABCCLNT123\1000

Number of an organizational unit that is indicated as the purchasing organization in the organizational plan. Default value in the component detail data.

ü

PM_SWERK

Maintenance plant

Example value: ABCCLNT123\1234

Plant at which the technical objects of a company are installed.

This attribute is used as a selection criterion when searching for orders in the backend system.

ü

PM_VAWRK

Plant for main work center

Example value: ABCCLNT123\1234

Plant at which the main work center entered is located.

This attribute is used as a selection criterion when searching for orders in the backend system.

ü

PM_WGR

PM material group

Example value: ABCCLNT123\000000001

Indicates the key of the material group that unites materials and services with the same properties. Default value in the component detail data.

ü

PM_WRK

Plant of the component

Example value: ABCCLNT123\1000

Plant at which the component required to execute the order (reservation or requirement request) is planned. Default value in the component detail data.

This is a mandatory attribute.

ü

PRCAT

Material group

Defines the product categories for which the user has authorization. We recommend that you define a default value. For example, if a user mainly purchases office materials, it would make sense to specify office materials as the default value.

To improve performance, we recommend that you use wildcards and ranges to restrict the product categories defined as much as possible.

You define this attribute using tab card Extended attributes.

PRI

Default printer

Example value: PRINTER

Printer name

PRO

WBS element

Defines the WBS element The work breakdown structure (WBS) represents the hierarchical organization of a project. WBS elements are the individual structural elements in a work breakdown structure Default value for account assignment when creating shopping cart or lean purchase order.

ü

PURCH_GRP

Purchasing group

Number of an organizational unit that is indicated as local purchasing group in the organizational plan.

This attribute is simulated. You define an organizational unit as purchasing group on the Function tab.

PURCH_GRPX

R/3 purchasing group

Number of the organizational unit that is indicated as the purchasing group in the organizational plan. The value contains the ID and the associated backend system of a backend purchasing group.

This attribute is simulated. You define the ID and the associated system on the Function tab.

ü

PURCH_ORG

Purchasing organization

Number of an organizational unit that is indicated as local purchasing organization in the organizational plan.

This attribute is simulated. You define an organizational unit as purchasing organization on the Function tab.

PURCH_ORGX

R/3 purchasing organization

Number of an organizational unit that is indicated as the purchasing organization in the organizational plan.

This attribute is simulated. You define the ID and the associated system on the Function tab.

ü

REQUESTER

Goods recipient

Example value: See definition

Indicates the organizational units or users for which this employee can create shopping carts, and so on.

A user can select all users in an organizational unit as alternative goods recipients if the attribute is maintained with the following entry, for example: O 50000019.

If a specific user is to be selected as alternative goods recipient, the attribute needs to be maintained as follows: <US><User ID of alternative goods recipient>, for example USMANAGER22.

Before you can order direct materials, you must have defined the necessary plants. You use this attribute to define these plants in the organizational plan. You enter plants as follows: <type_BP><partner_number_for_plant>, for example, BP1195.

For the purposes of the direct materials scenario the business partner number (it can have a maximum of ten positions) defined in this attribute must be linked to a plant in table CRMM_LOCMAP.

Shop on behalf of: You have to maintain this attribute for the buying on behalf of application. You enter all users for whom a secretary can order.

The values defined for the attribute form the basis for the F4 help for the Goods Recipient field available to the secretary or other employee creating shopping carts for other users in the Shop scenario.

RESP_PRGRP

Purchasing group responsible

Number of the organizational unit for which the purchasing group is responsible.

This attribute is simulated. You define the organizational responsibility of a purchasing group on the Responsibility tab.

RESP_PRCAT

Product category responsible

Number of the product category for which the purchasing group is responsible.

This attribute is simulated. You define the product responsibility of a purchasing group on the Responsibility tab.

ROLE

User role

Example value: SAP_EC_BBP_VENDOR

Indicates the role of the user, for example manager, employee, or secretary.

If no approval workflow for new users is in force, a default value must be set for the attribute ROLE, for example SAP_EC_BBP_EMPLOYEE. (If no default value is found, the approval workflow is activated automatically.)

SF_FOOTER

SAP Smart Forms: Footer

Defines the footer to be used when purchase orders or contracts are output. The values are determined using Smart Forms on the basis of the purchasing group. You define the footer using the transaction SE78.

SF_GRAPHIC

SAP Smart Forms: Company logo

Defines the company logo to be used when purchase orders or contracts are output. The values are determined using Smart Forms on the basis of the purchasing group. You define the company logo using transaction SO10.

SF_HEADER

SAP Smart Forms: Header

Example value: BBP_COMPANY

Defines the header to be used when purchase orders or contracts are output. The values are determined using Smart Forms on the basis of the purchasing group. You define the header using the transaction SE78.

SLAPPROVER

Spending limit approver

Example value: USMANAGER1

Specifies the approver used in workflows based on a spending limit.

SPEND_LIM

Spending limit

The value up to which a user is allowed to spend before the spending limit approval workflow is triggered.

You define this attribute using tab card Extended attributes.

SYS

System alias

Example value: ABCCLNT123

Defines the systems to be searched to find purchase orders. This attribute is used to generate worklists for employees that create confirmations or invoices centrally. The attribute can refer both to the local system and backend systems. Generally, several values are defined: The local systems and various backend systems.

The systems have to be defined in Customizing. Path in the Implementation Guide (IMG): Supplier Relationship Management ® SRM Server ® Technical Basic Settings ® Define Basic Settings.

TEND_TYPE

Transaction type: Bid invitation

Example value: BID

Specifies the transaction type for bid invitations created automatically, for example in the PLM (collaborative engineering). You define this attribute for the purchasing group that is responsible for the organizational unit of the entry channel. The value for this attribute can be inherited. For example, purchasing groups can inherit it from their purchasing organization. You define the transaction type in Customizing.

Path in the Implementation Guide (IMG):
Supplier Relationship Management ® SRM Server ® Cross-Application Basic Settings ® Define Transaction Types.

TOG

Tolerance group

Example value: CONF

Defines the tolerance group. Using this attribute, you define for a user group which tolerance checks are used when quantity or value tolerances for deliveries or invoices are exceeded.

ü

VENDOR_ACS

Accounting system for the vendor

Example value: ABCCLNT123

Specifies the backend system where the account assignment is checked. This attribute is required for:

·         Invoices without purchase order reference

·         Local invoices

We recommend that you define this attribute at a high level in your organizational plan.

Prerequisite: You must have defined the backend system during Customizing.

Path in the Implementation Guide (IMG): Supplier Relationship Management ® SRM Server ® Technical Basic Settings ® Define Basic Settings.

VENDOR_SYS

System alias for vendor

Example value: ABCCLNT123

Defines the systems to be searched to find purchase orders to create a worklist for a vendor creating confirmations or invoices centrally. Can refer both to the local system and to the backend system. Generally, multiple values are entered: The local systems and various backend systems.

The systems must have been defined during Customizing. Path in the Implementation Guide (IMG): Supplier Relationship Management ® SRM Server ® Technical Basic Settings ® Define Basic Settings.

WGR

Product category

See attribute PRCAT.

This attribute is simulated. The values of the attribute PRCAT serve as the basis for the simulation.

Whilst you can define single values, masks, and areas for PRCAT, you can only use single values for WGR.

WRK

Plant

Specifies the plant in the R/3 backend system. This attribute is only required if the backend system is an SAP System.

You define this attribute using tab card Extended attributes.

ü