Making Settings for Global Outline Agreements 

Use

This section describes the steps for configuring global outline agreements.

In the standard the transaction type determines whether the system creates a global outline agreement (GOA) instead of an operational purchase contract (local contract in SRM).

As of SRM 4.0 you do not need Business Add-In BBP_DOC_CHANGE_BADI and its BBP_CTR_CHANGE method for this purpose. However, if you were using this BAdI in Releases lower than SRM 4.0 to determine the creation of global outline agreements, you can continue to do so.

You can distribute a global outline agreement to one or more SAP backend systems. The transferred data can be used to create one of the following documents:

·        A backend purchase contract

·        A scheduling agreement

The SRM system only transfers material items from a global outline agreement to a backend scheduling agreement, no service items.

For information on how you can configure contract management across the SRM and backend system(s) and what logic the system uses when creating a contract from the sourcing application of SAP Enterprise Buyer or from SAP Bidding Engine, see Configuration Options.

Prerequisites

SRM system

·        Backend system

You have defined an RFC destination for the backend system and you have defined the backend system in which you want to create contracts or scheduling agreements. See Defining the RFC Destination and Backend System. If you have already defined an R/3 system (FI) as a destination in another business scenario, you can use this destination for backend contracts or scheduling agreements also.

·        Transaction type

You have made sure to use the correct transaction type for global outline agreements, such as GCTR , and that for this transaction type you use the subtype Global outline agreement. Observe that in the standard transaction type PCTR is used for operational contracts in SRM. This transaction type is not meant to be used for global outline agreements and it is not meant to be used with the subtype Global outline agreement.

We recommend that you use the same transaction types in the SRM system and in the backend system.

See Defining Transaction Types for Sourcing. If you do not use the same transaction type in the SRM and backend systems, you must map this data. Refer to Step 4 of the “Setting Up and Mapping (Master) Data” procedure in this section.

·        Number range

We recommend that you use an internal number range in the SRM system for the global outline agreement transaction type that is the same as the external number range in the backend system for the corresponding document type (purchase contract or scheduling agreement).

If you want to change the standard settings in the backend system, you can use the BAdI BBP_CTR.

See the Plug-In IMG path: Integration with Other mySAP Components  ®  Supplier Relationship Management  ®  Business Add-Ins (BAdIs)  ®  Contracts and Conditions  ®  Change Contracts and Conditions.

·        Condition types

You have created the appropriate condition types (for pricing conditions) if you want to use the same ones as in the backend system. If you used a different technical name in SAP Enterprise Buyer, you have made sure that all other settings are identical to those in the backend system.

See path in the Implementation guide (IMG) of SAP Supplier Relationship Management: SRM Server  ®  Cross-Application Basic Settings  ® Pricing.

The BAdI CTR_BE_CREATE can be used for mapping the condition types of SRM and the backend system as well.

 

·        Version Control

You have activated version control for purchasing documents.

See path in the Implementation guide (IMG) of SAP Supplier Relationship Management: SRM Server ® Cross-Application Basic Settings ® Switch On Version Control for Purchasing Documents.

 

Backend System

You have ensured that the following is true:

·        The backend system is of Release 4.6B or higher with Plug-In 2004.1.

·        You have set up an external number range for the document types referring to purchase contracts and scheduling agreements

·        You have implemented the number range for the number range object BBP_SRV with internal number assignment for service items.

·        You have implemented SAP Note 641919, BLAREL: values in service segment E1RDSV1.

·        You have set up the IDoc customizing.

·        You have implemented BAdI BBP_CTR to enable product category items with product type service in a contract. In the item structure you have entered (in the UNIT_ISO field) the unit of measurement for the product category item as ISO code.

You are using synchronous IDs and settings in the SRM and backend systems for:

§         Master data, such as products, product categories and vendors

§         Other data, such as currencies, payment terms, text IDs, and transaction types, condition types.

For further information regarding condition types refer to “Prerequisites” in section Making Settings for Backend Purchase Contracts.

We recommend that you replicate master data such as products, product categories and vendors from the backend system. See Downloading Business Objects

Procedure in the SRM System

Setting Up Organizational Data and Mapping (Master) Data

...

       1.      Check that the Purchasing Organization and Purchasing Group of the backend system exist in the organizational plan, using transaction PPOMA_BBP.

                            a.      Link the SRM purchasing organization to the purchasing organization you use for contracts in the backend system: On the Function tab page under section Local

§         Select the Purch. Organization indicator

§         Enter the key of the backend purchasing organization

§         Enter the key of the logical system (backend)

                            b.      Link the SRM purchasing organization to the purchasing group you use for contracts in the backend system: On the Function tab page under section Local

§         Select the Purch. Group indicator

§         Enter the key of the backend purchasing group

§         Enter the key of the logical system (backend)

       2.      Make sure, the following data exists in your system:

·         Table VENMAP contains vendor data with identical GUID, backend vendor number and logical system

·         Table BBP_LOCMAP contains location data with mapping for business partner and logical system

       3.      Map the corresponding data if you are not using identical data in the SRM and backend systems for:

¡        Product categories

¡        Products

¡        Condition types for normal items

¡        Condition types for service items

¡        Text IDs

¡        Transaction types

To map this data use one of the following Business Add-Ins:

¡        If you want to map the data in the SRM system, use BAdI BBP_CTR_BE_CREATE.

We recommend that you map the data there.

See IMG path: SRM Server ® Business Add-Ins (BAdIs)  ®  Follow-on Document Generation in the Backend-System ® Create Contract in Backend System.

¡        Alternatively, if you want to map this data in the backend system, use BAdI BBP_CTR which is only available in the backend system.

See Plug-In IMG path: Integration with other mySAP.com Components  ®  Supplier Relationship Management  ®  Business Add-Ins (BAdIs)  ®  Contracts and Conditions ®  Change Contracts and Conditions.

 

Enabling Global Outline Agreements

The system checks whether the CT_PROC_TY attribute is maintained in the organizational plan. If so, the attribute determines the transaction type, for example, GCTR for global outline agreements. If no attribute exists, the system checks the transaction type settings for follow-on documents. See path in the Implementation guide (IMG) of SAP Supplier Relationship Management: SRM Server  ®  Cross-Application Basic Settings  ®   Define Transaction Types.

As of SRM 4.0 you do not need BAdI BBP_DOC_CHANGE_BADI and its method BBP_CTR_CHANGE for this purpose. However, if you were using this BAdI in Releases lower than SRM 4.0 to determine the creation of global outline agreements, you can continue to do so.

Transaction Code	SPRO
IMG Path	SRM Server  ®  Business Add-Ins (BAdIs)  ®  Change Data of Purchasing Documents

...

       1.      (Optional) Implement BAdI BBP_DOC_CHANGE_BADI to enable the creation of global outline agreements from SAP Bidding Engine or from the sourcing application of SAP Enterprise Buyer. If you want to create a global outline agreement directly from a bid, specify the subtype Global outline agreement in method BBP_CTR_CHANGE.

 

Setting Up the User Interface

Transaction Code	SPRO
IMG Path	SRM Server→ Business Add-Ins (BAdIs) → Interface Configuration → Input Helps and Search Helps

...

       1.      (Optional) Implement the BAdI BBP_UI_CONTROL_BADI to control the visibility and ready-for-input status of user interface objects in the application.

 

Setting Up the Purchasing Organization Notification

Transaction Code	SPRO
IMG Path	SRM Server  ®  Business Add-Ins (BAdIs)  ®  Control E-Mail in Global Outline Agreement

...

       1.      (Optional) Implement BAdI BBP_CTR_MAIL_BADI to control, for example, the receiver list and the content of e-mails sent to the purchasing organizations authorized for contract release orders.

 

Changing the Transfer Data of Global Outline Agreements

Transaction Code	SPRO
IMG Path	SRM Server ® Business Add-Ins (BAdIs) ® Follow-On Document Generation in the Backend System ® Create Contract in Backend System

...

       1.      Implement BAdI BBP_CTR_BE_CREATE to change, for example, product master data, such as the product ID, before transferring the data of the global outline agreement to the backend system.

 

Setting Up the IDoc Inbound Processing of Contract Release Order Data

The SRM system uses the IDoc BLAREL02 for receiving update data of contract release orders (accumulated data of contract release orders in the backend system).

Area Code

WEDI

       1.      Using transaction WE21, create a port of type tRFC (transactional RFC).

                            a.      Assign the RFC destination, for example, of the logical system that refers to backend system.

       2.      Using transaction WE20, create a Partner profile.

                            a.      Under Partner type LS, choose the logical system that refers to backend system.

                            b.      Under Inbound Parameters, create a new entry selecting message type BLAREL.

                            c.      Under Inbound Options, select process code BLAR and set the Trigger immediately indicator.

       3.      Choose Save.

 

Procedure in the Backend System

Setting Up Multiple Contracts/Scheduling Agreements with Reference to One SRM Global Outline Agreement

The BAdI Change Contracts and Conditions (BBP_CTR) is part of the plug-in in the backend system.

Transaction Code	SPRO
IMG Path	Integration with Other mySAP Components  ®  Supplier Relationship Management  ®  Business Add-Ins (BAdIs)  ®  Contracts and Conditions  ®  Change Contracts and Conditions

...

       1.      Implement BAdI BBP_CTR to create several contracts/scheduling agreements in one backend system on the basis of one global outline agreement. For example, individual contracts for different purchasing organizations or company codes.

§         If you want to use number ranges that differ from those used in the SRM global outline agreement, refer to the sample coding provided with BAdI BBP_CTR.

§         For further information regarding the use of multiple contracts in one backend system, refer to SAP Note 646903.

 

Setting Up the IDoc Outbound Processing of Contract Release Order Data

The backend system uses the IDoc BLAREL02 for sending update data of contract release orders to the SRM system.

This section is not relevant, when you create scheduling agreements from a global outline agreement.

...

...

...

Area Code

WEDI

       1.      Using transaction WE21, create a port of type tRFC (transactional RFC)

                            a.      Assign the RFC destination, for example, of the logical system that refers to SRM system.

       3.      Using transaction WE20, create a Partner profile.

                            a.      Under Partner type LS, choose the logical system that refers to the SRM system.

                            b.      Under Outbound Parameters, create a new entry selecting message type BLAREL.

                            c.      Under Outbound Options, select the receiver port that refers to the SRM system.

§         Select the IDoc basic type BLAREL02

§         Select Transfer IDoc immediately.

       4.      Choose Save.

 

Setting Up the IDoc Inbound Processing of Contract and Condition Data

R/3 inbound processing uses different IDocs for creating contracts/scheduling agreements and for creating conditions.

Transaction Code	WE42
Menu Path	Tools  ®  ALE  ®  ALE Development  ®  IDoc  ®  Inbound Processing  ®  Define Process Code

...

       1.      Start transaction WE42.

                            a.      Assign the inbound processing code BLAO for purchasing contracts to message type BLAORD.

                            b.      Assign the inbound processing code COND for conditions to message type COND_A.

 

Creating the ALE Partner Settings

Transaction Code	WE20
Menu Path	Tools  ®  Business Communication  ®  IDoc  ®  Partner Profile

...

       1.      Create a partner profile for Partner type LS (logical system of sending SRM system) with the following entries and settings under Inbound parameters:

                            a.      Message type BLAORD (for purchasing contracts), Process Code BLAO and Transfer IDoc immediately activated.

                            b.      Message type COND_A (master conditions, for price determination), Process Code COND and Transfer IDoc immediately activated.

       2.      Choose Save.

 

Specifying Document Types for Backend Contracts

Transaction Code	SPRO
IMG Path	Materials Management  ®  Purchasing  ®  Contract  ®  Define Document Types

...

       1.      Choose the document type for backend contracts.

       2.      Enter a number range for external number assignment that is identical to the internal number range you specified in the SRM system for backend contracts.

 

Specifying Document Types for Scheduling Agreements

Transaction Code	SPRO
IMG Path	Materials Management  ®  Purchasing  ®  Scheduling Agreement ®  Define Document Types

...

       1.      Choose the document type for scheduling agreements.

       2.      Enter a number range for external number assignment that is identical to the internal number range you specified in the SRM system for scheduling agreements.

 

Specifying Number Ranges for Backend Contracts

Transaction Code	SPRO
IMG Path	Materials Management  ®  Purchasing  ®  Contract  ®  Define Number Ranges

...

       1.      Enter a number range for external number assignment that is identical to the internal number range you specified in the SRM system for backend contracts.

 

Specifying Number Ranges for Scheduling Agreements

Transaction Code	SPRO
IMG Path	Materials Management  ®  Purchasing  ®  Scheduling Agreement ®  Define Number Ranges

...

       1.      Enter a number range for external number assignment that is identical to the internal number range you specified in the SRM system for scheduling agreements.

 

See also:

Making Settings for Backend Purchase Contracts