0% found this document useful (0 votes)
542 views

Adapt and Extend Functionality of Apps

This document discusses how to adapt and extend the functionality of apps in SAP S/4HANA Cloud. It describes how key users can add custom fields and logic using business add-ins (BAdIs) without changing code. BAdIs allow influencing app behavior, and examples of relevant BAdIs for purchase requisitions are provided.

Uploaded by

maazsz111
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
542 views

Adapt and Extend Functionality of Apps

This document discusses how to adapt and extend the functionality of apps in SAP S/4HANA Cloud. It describes how key users can add custom fields and logic using business add-ins (BAdIs) without changing code. BAdIs allow influencing app behavior, and examples of relevant BAdIs for purchase requisitions are provided.

Uploaded by

maazsz111
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 68

10/12/2023

Sourcing and Procurement


Generated on: 2023-10-12 05:13:15 GMT+0000

SAP S/4HANA Cloud | 2308.1

PUBLIC

Original content: https://help.sap.com/docs/SAP_S4HANA_CLOUD/0e602d466b99490187fcbb30d1dc897c?locale=en-


US&state=PRODUCTION&version=2308.501

Warning

This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.

For more information, please visit the https://help.sap.com/docs/disclaimer.

This is custom documentation. For more information, please visit the SAP Help Portal 1
10/12/2023

Adapt and Extend Functionality of Apps (Extensibility)


With SAP S/4HANA Cloud, SAP delivers a standard product with standard functionality. You can build additions to the standard
functionality to signi cantly increase the reach and the scope of the system and make the solution tailor- t to your speci c
business processes. With the so called in-app extensibility the key users can add new elds to the business documents (custom
elds) or in uence the behaviour of the apps (custom logic).

 Note
A key user is a member of a functional team that adapts the software to the needs of his or her business department - being
either a direct employee or an external person, such as a consultant. as this person typically has some level of technical
knowledge but no in-depth knowledge like a developer, all extension steps need to be covered by tools that hide complexity
and technical details.

In-system extensions inherit such properties as performance, availability and resilience from SAP S/4HANA Cloud. It is
important to identify extensions that are mission critical, because any failure in such extensions would have a severe impact on
business operations.

Please note that image maps are not interactive in PDF output.

Quick Navigation
This image is interactive. Hover over each area for a description. Click highlighted areas for more information.

This is custom documentation. For more information, please visit the SAP Help Portal 2
10/12/2023

Please note that image maps are not interactive in PDF output.

Adaptation of App Behavior

In uence behavior of the apps


To enable you to in uence the behavior of the apps, SAP provides business add-ins (BAdIs) for multiple business objects. A BAdI
allows you to change a function in an SAP system without changing the delivered code. BAdIs usually consist of two parts:

De nition

BAdI de nition is an interface provided by SAP.

Implementation

BAdI implementation is the coding that de nes what should happen when the BAdI is called.

There are two ways of accessing the BAdIs:

Key users can work with BAdIs in the Custom Logic app.

Developers can work with BAdIs in the SAP S/4HANA Cloud ABAP Environment.

This is custom documentation. For more information, please visit the SAP Help Portal 3
10/12/2023
In the Custom Logic app, you can create custom logic for the BAdIs, for example, you can implement additional checks, set
default values, or create mappings in combination with custom elds

Available BAdIs
BAdIs Available in Sourcing and Procurement

Business Object BAdI ID and Description Short Description Related Links

Purchase Requisition Check of Purchase Requisition Item Check or validate values of standard
(MM_PUR_S4_PR_CHECK) and extension elds in purchase App Extensibility:
requisitions at item level Create Purchase
Requisition

App Extensibility:
Create Purchase
Requisition -
Advanced

App Extensibility:
My Purchase
Requisitions

App Extensibility:
Manage Purchase
Requisitions -
Professional

App Extensibility:
My Purchase
Requisitions - New

Purchase Requisition Change of Purchase Requisition Item Set or change values of standard and
(MM_PUR_S4_PR_MODIFY_ITEM) extension elds in purchase App Extensibility:
requisitions at item level. Create Purchase
Requisition

App Extensibility:
Create Purchase
Requisition -
Advanced

App Extensibility:
My Purchase
Requisitions

App Extensibility:
Manage Purchase
Requisitions -
Professional

App Extensibility:
My Purchase
Requisitions - New

This is custom documentation. For more information, please visit the SAP Help Portal 4
10/12/2023

Business Object BAdI ID and Description Short Description Related Links

Purchase Requisition Change of OCI 4.0 Outbound Parameters Modify the outbound parameters
for Purchase Requisitions that are sent to the catalog provider App Extensibility:
(MMPUR_OCI_OUTBOUND_PARAMETERS ) using the open catalog web service. Create Purchase
Requisition

App Extensibility:
My Purchase
Requisitions

App Extensibility:
Manage Purchase
Requisitions -
Professional

App Extensibility:
My Purchase
Requisitions - New

Purchase Requisition Change of Header of a Purchase Requisition Set or change values of standard and
(MM_PUR_S4_PR_MODIFY_HEADER ) extension elds in purchase App Extensibility:
requisitions at header level. Create Purchase
Requisition

App Extensibility:
Create Purchase
Requisition -
Advanced

App Extensibility:
My Purchase
Requisitions

App Extensibility:
Manage Purchase
Requisitions -
Professional

App Extensibility:
My Purchase
Requisitions - New

Purchase Requisition Change of Self Service Purchase Modify extension elds and check
Requisition in Central Procurement header and item level information of App Extensibility:
(MM_PUR_S4_SSP_HUB_PR_MODIFY) self-service purchase requisitions Create Purchase
during simulation and replication Requisition
from hub system to connected
App Extensibility:
system.
My Purchase
Requisitions

App Extensibility:
My Purchase
Requisitions - New

This is custom documentation. For more information, please visit the SAP Help Portal 5
10/12/2023

Business Object BAdI ID and Description Short Description Related Links

Purchase Requisition Speci cation of Proxy Server During OCI Specify proxy server settings to
Validation (MMPUR_CAT_PROXY_INFO) access internet during catalog App Extensibility:
extraction. Create Purchase
Requisition

App Extensibility:
My Purchase
Requisitions

App Extensibility:
Manage Purchase
Requisitions -
Professional

App Extensibility:
My Purchase
Requisitions - New

Purchase Requisition De nition of Conditions to Restart Flexible Enable or disable the restart of the
Work ow in Purchase Requisitions approval work ow in purchase App Extensibility:
(MM_PUR_S4_PR_WFL_RESTART) requisitions. Also, overwrite the Create Purchase
con gurations de ned in Requisition
con guration step Manage
App Extensibility:
Conditions to Restart Flexible
Create Purchase
Work ow.
Requisition -
Advanced

App Extensibility:
My Purchase
Requisitions

App Extensibility:
Manage Purchase
Requisitions -
Professional

App Extensibility:
My Purchase
Requisitions - New

This is custom documentation. For more information, please visit the SAP Help Portal 6
10/12/2023

Business Object BAdI ID and Description Short Description Related Links

Purchase Requisition Enhancement of Flexible Work ow Based on the context in which it is


Properties invoked, you can use this BAdI for App Extensibility:
(MMPUR_WFL_CONTEXT_ENHANCE) the following purposes: Create Purchase
Requisition
Set agents that need to be
App Extensibility:
excluded
Create Purchase
Set a maximum of ve Requisition -
custom attributes Advanced

Set the priority of a work ow App Extensibility:


step or task My Purchase
Requisitions

App Extensibility:
Manage Purchase
Requisitions -
Professional

App Extensibility:
My Purchase
Requisitions - New

Purchase Requisition Work ow: get agents for forwarding by Filter the list of recipients that is
customer shown in the My Inbox app when you App Extensibility:
(SWF_FORWARD_AGENTS_GET_CUSTOM) want to forward a task to another Create Purchase
user. Requisition

App Extensibility:
Create Purchase
Requisition -
Advanced

App Extensibility:
My Purchase
Requisitions

App Extensibility:
Manage Purchase
Requisitions -
Professional

App Extensibility:
My Purchase
Requisitions - New

Purchase Requisition Setting of Default Delivery Address of Self- Maintain the default delivery
Service Purchase Requisition address of a self-service purchase App Extensibility:
(MM_PUR_SSP_DEF_DEL_ADRS_SIMPLE) requisition item. Create Purchase
Requisition

App Extensibility:
My Purchase
Requisitions

App Extensibility:
My Purchase
Requisitions - New

This is custom documentation. For more information, please visit the SAP Help Portal 7
10/12/2023

Business Object BAdI ID and Description Short Description Related Links

Purchase Requisition Change of Draft Item of a Self-Service Set prede ned values for elds
Purchase Requisition during the creation of self-service App Extensibility:
(MM_PUR_S4_SSPPR_MOD_DRAFT_ITEM) purchase requisition. Create Purchase
Requisition

App Extensibility:
My Purchase
Requisitions

Purchase Requisition Check of Draft Item of a Self-Service Check the data entered in various
Purchase Requisition elds, while a purchase requisition is App Extensibility:
(MM_PUR_S4_SSPPR_CHK_DRAFT_ITEM) being created and is in draft state. Create Purchase
Requisition

App Extensibility:
My Purchase
Requisitions

Purchase Requisition Change of OCI 4.0 Data When Mapping to Modify data when mapping OCI 4.0
Draft Item of Self-Service Purchase data to draft items in self-service App Extensibility:
Requisition purchase requisition. Create Purchase
(MMPUR_OCI_TO_DRAFT_ITM_MAPPING) Requisition

App Extensibility:
My Purchase
Requisitions

App Extensibility:
My Purchase
Requisitions - New

Purchase Requisition Change of OCI 4.0 Data When Mapping to a Access the master data of a catalog
Purchase Requisition Item provider, and add or remove items App Extensibility:
(MMPUR_OCI_ITEM_TRANSFER_DATA) automatically from a catalog during Create Purchase
the transfer of data. Requisition

App Extensibility:
My Purchase
Requisitions

App Extensibility:
Manage Purchase
Requisitions -
Professional

App Extensibility:
My Purchase
Requisitions - New

This is custom documentation. For more information, please visit the SAP Help Portal 8
10/12/2023

Business Object BAdI ID and Description Short Description Related Links

Purchase Requisition Change of Field Control for Purchase Modify the properties of different
Requisitions elds that appear on the user App Extensibility:
(MM_PUR_S4_PR_FLDCNTRL_SIMPLE) interface of purchase requisition Create Purchase
apps. Requisition

App Extensibility:
Create Purchase
Requisition -
Advanced

App Extensibility:
My Purchase
Requisitions

App Extensibility:
Manage Purchase
Requisitions -
Professional

App Extensibility:
My Purchase
Requisitions - New

Purchase Requisition Calculation of Transient Custom Fields in Maintain the custom logic to
Manage Purchase Requisitions - calculate transient custom elds App Extensibility:
Professional using the values of the standard Manage Purchase
(MMPUR_PR_PROFNL_ITM_CTF) elds and custom elds in a Requisitions -
purchase requisition item. Professional

Purchase Requisition Calculation of Transient Custom Fields in Maintain the custom logic to
Self-Service Procurement calculate transient custom elds App Extensibility:
(MMPUR_SSPPR_ITM_CALC_FIELDS) using the values of the standard My Purchase
elds and custom elds in a Requisitions - New
purchase requisition item.

Purchase Requisition Calculation of Transient Custom Fields in Maintain the custom logic to
PR FactSheet calculate transient custom elds App Extensibility:
(MMPUR_PRFS_ITM_CALC_FIELDS) using the values of the standard Purchase
elds and custom elds in a Requisition Object
purchase requisition item. Page

App Extensibility:
Purchase
Requisition Item
Object Page

Purchase Order Change of Field Control for Purchase Order Change the eld control in purchase
Header order apps by modifying the Extensibility for
(MM_PUR_S4_PO_FLDCNTRL_SIMPLE_H) properties of speci c elds. These Purchase Order
elds can be made hidden, read- Apps
only, mandatory, or optional on
App Extensibility:
header level.
Manage Purchase
Orders

This is custom documentation. For more information, please visit the SAP Help Portal 9
10/12/2023

Business Object BAdI ID and Description Short Description Related Links

Purchase Order Change of Field Control for Purchase Order Change the eld control in purchase
Item order apps by modifying the Extensibility for
(MM_PUR_S4_PO_FLDCNTRL_SIMPLE) properties of speci c elds. These Purchase Order
elds can be made hidden, read- Apps
only, mandatory, or optional on item
App Extensibility:
level.
Manage Purchase
Orders

Purchase Order Close Purchase Order Reset your own programs.


(MM_PUR_S4_PO_CLOSE) Extensibility for
Purchase Order
Apps

App Extensibility:
Manage Purchase
Orders

Purchase Order Final Check before Saving Purchase Order With this BAdI, you can
(BD_MMPUR_FINAL_CHECK_PO) Extensibility for
Implement own checks before a Purchase Order
purchase order is saved. Apps

App Extensibility:
Manage Purchase
Orders

This is custom documentation. For more information, please visit the SAP Help Portal 10
10/12/2023

Business Object BAdI ID and Description Short Description Related Links

Purchase Order Control of Pricing Type: Additional Fields With this BAdI, you can
(MM_PUR_S4_PO_DEFINE_CNDNCTRL) Extensibility for
Control the price determination Purchase Order
process when creating or changing a Apps
purchase order. When a purchase
App Extensibility:
order is created or changed, the
Manage Purchase
system carries out a price
Orders
determination process at various
points in the process. The type of
price determination (pricing type)
depends on the relevant status of
the ordering transcations. Among
others, the following types are
possible:

Pricing type B (Carry out new


pricing): Always invoked
when you create a new PO
item

Pricing type C (Copy manual


pricing elements and
redetermine the others):
Invoked when you change
data that can in uence the
price determination process
at item level, for example
when you change the account
assignment category)

Using this BAdI, you can de ne the


conditions for triggering a price
determination process that differ
from those of the standard system.
You can specify the pricing type in
this case. This is of interest, when
you determine prices via conditions
and, in the process, make use of
elds that are not taken into account
in the condition tables supplied.

Purchase Order Final Check Before Saving Purchase Order Implement own checks before a
(BD_MMPUR_FINAL_CHECK_PO) purchase order is saved. Extensibility for
Purchase Order
Apps

App Extensibility:
Manage Purchase
Orders

Purchase Order Initialize Purchase Order Initialize data when starting to work
(MM_PUR_S4_PO_INITIALIZE) with a purchase order. Extensibility for
Purchase Order
Apps

App Extensibility:
Manage Purchase
Orders

This is custom documentation. For more information, please visit the SAP Help Portal 11
10/12/2023

Business Object BAdI ID and Description Short Description Related Links

Purchase Order Modify Purchase Order Account Make changes to elds on account
Assignment Data assignment level and perform your Extensibility for
(MM_PUR_S4_PO_MODIFY_ACCOUNT) own checks and issue corresponding Purchase Order
messages. Changes are possible for Apps
the following elds:
App Extensibility:
Manage Purchase
GLACCOUNT, COSTCENTER,
Orders
PROFITCENTER,
PROJECTNETWORK,
WBSELEMENTINTERNALID,
MASTERFIXEDASSET,
SALESORDER, SALESORDERITEM,
UNLOADINGPOINT,
CONTROLLINGAREA,
FUNCTIONALAREA,
SERVICEDOCUMENTTYPE,
SERVICEDOCUMENTID,
SERVICEDOCUMENTITEMID,
GOODSRECIPIENTNAME

Purchase Order Modify Purchase Order Header Set or change values of custom
(MM_PUR_S4_PO_MODIFY_HEADER) elds in purchase orders on header Extensibility for
level. Purchase Order
Apps

App Extensibility:
Manage Purchase
Orders

Purchase Order Modify Purchase Order Item Set or change values of custom
(MM_PUR_S4_PO_MODIFY_ITEM) elds in purchase orders on item Extensibility for
level and make changes to the Purchase Order
following elds: Apps

App Extensibility:
TAXCODE, TAXCOUNTRY,
Manage Purchase
INCOTERMSCLASSIFICATION,
Orders
INCOTERMSTRANSFERLOCATION,
INCOTERMSLOCATION1,
INCOTERMSLOCATION2

Purchase Order Modify Purchase Order Item Delivery In uence the delivery address on
Address item level by setting the delivery Extensibility for
(MM_PUR_S4_PO_MODIFY_DELIV_ADDR) address number. You can change the Purchase Order
following eld: Apps
REFERENCEDELIVERYADDRESSID
App Extensibility:
Manage Purchase
Orders

Purchase Order Modify Purchase Order Schedule Line Data Make changes to date elds on
( MM_PUR_S4_PO_MODIFY_SCHEDULE) schedule line level and implement Extensibility for
own checks with corresponding Purchase Order
messages. Changes are possible for Apps
the following elds:
App Extensibility:
Manage Purchase
SCHEDULELINEDELIVERYDATE,
Orders
PERFORMANCEPERIODSTARTDATE,
PERFOMANCEPERIODENDDATE,
SCHEDULELINEDELIVERYTIME

This is custom documentation. For more information, please visit the SAP Help Portal 12
10/12/2023

Business Object BAdI ID and Description Short Description Related Links

Purchase Order Modify Tax Jurisdiction Code of Purchase Determine the tax jurisdiction code
Order Item in purchase orders and use it, for Extensibility for
(MM_PUR_S4_PO_MODIFY_TAXJURCODE) example, on item level for tax Purchase Order
calculation purposes if the tax Apps
jurisdiction code is maintained in the
App Extensibility:
delivery address.
Manage Purchase
Orders

Purchase Order Open Purchase Order Put a purchase order in display


mode and prevent processing of the Extensibility for
(MM_PUR_S4_PO_OPEN) purchase order. Purchase Order
Apps

App Extensibility:
Manage Purchase
Orders

Purchase Order PO Check All Items Check the entire docurment.


(MM_PUR_S4_PO_CHECK_ALL_ITEMS) Extensibility for
Purchase Order
Apps

App Extensibility:
Manage Purchase
Orders

Purchase Order Post Purchase Order Post your own data.


(MM_PUR_S4_PO_POST) Extensibility for
Purchase Order
Apps

App Extensibility:
Manage Purchase
Orders

Purchase Order Purchase Order Hold Allowed Specify if a purchase order can be
(MM_PUR_S4_PO_HOLD_ALLOWED) put on hold. Extensibility for
Purchase Order
Apps

App Extensibility:
Manage Purchase
Orders

Purchase Order De ne Conditions to Restart Work ow in Enable or disable the restart of the Extensibility for Purchase
Purchase Orders approval work ow in purchase Order Apps
MMPUR_PO_WORKFLOW_RESTART orders. Also, overwrite the
con gurations de ned in
con guration step Manage
Conditions to Restart Flexible
Work ows in Purchase Orders.

Purchase Contract Check of Purchase Contract Before Saving Validates values of standard and App Extensibility: Manage
(MM_PUR_S4_CTR_CHECK) custom elds of the purchase Purchase Contracts
contract

Purchase Contract Change of Purchase Contract Before Saving Modify values of standard and App Extensibility: Manage
(MM_PUR_S4_CTR_MODIFY_HEADER) custom elds at the header level of Purchase Contracts
the purchase contract.

This is custom documentation. For more information, please visit the SAP Help Portal 13
10/12/2023

Business Object BAdI ID and Description Short Description Related Links

Purchase Contract Change of Purchase Contract Item Before Modi es values of standard and App Extensibility: Manage
Saving MM_PUR_S4_CTR_MODIFY_ITEM) custom elds at the item level of the Purchase Contracts
purchase contract

Supplier Quotation Check of Supplier Quotation Header and Check values of standard and App Extensibility: Manage
Item (MM_PUR_S4_QTN_CHECK) custom elds in supplier quotations. Supplier Quotations

Supplier Quotation Change of Supplier Quotation Header Set or changes values of custom App Extensibility: Manage
(MM_PUR_S4_QTN_MODIFY_HEADER) elds in supplier quotations at the Supplier Quotations
header level.

Supplier Quotation Change of Supplier Quotation Item Set or changes values of custom App Extensibility: Manage
(MM_PUR_S4_QTN_MODIFY_ITEM) elds in supplier quotations on item Supplier Quotations
level.

Request for Quotation Check of RFQ Header and Item Check values of standard and App Extensibility: Manage
(RFQ) (MM_PUR_S4_RFQ_CHECK) custom elds in RFQs. RFQs

Request for Quotation Change of RFQ Header Set or change values of custom App Extensibility: Manage
(RFQ) (MM_PUR_S4_RFQ_MODIFY_HEADER) elds in RFQs on header level. RFQs

Request for Quotation Change of RFQ Item Set or change values of custom App Extensibility: Manage
(RFQ) (MM_PUR_S4_RFQ_MODIFY_ITEM) elds in RFQs on item level. RFQs

Request for Quotation Change of Header in RFQ Output Set RFQ header values for custom App Extensibility: Manage
(RFQ) (MM_PUR_S4_RFQ_MODIFY_PRINT_HDR) elds in form templates, if these RFQs
values are not included in the RFQ
data set. This enhancement option is
only available for Request for Price.

Request for Quotation Change of Item in RFQ Output Set RFQ header values for custom App Extensibility: Manage
(RFQ) (MM_PUR_S4_RFQ_MODIFY_PRINT_ITM) elds in form templates, if these RFQs
values are not included in the RFQ
data set. This enhancement option is
only available for Request for Price.

Purchase Scheduling Check of Scheduling Agreement Validates values of standard and App Extensibility: Manage
Agreement (MM_PUR_S4_SA_CHECK) extension elds of the purchase Purchase Scheduling
scheduling agreement Agreements

Purchase Scheduling Change of Scheduling Agreement Header Modi es values of standard and App Extensibility: Manage
Agreement (MM_PUR_S4_SA_MODIFY_HEADER) extension elds at the header level Purchase Scheduling
of the purchase scheduling Agreements
agreement

Purchase Scheduling Change of Scheduling Agreement Item Modi es values of standard and App Extensibility: Manage
Agreement (MM_PUR_S4_SA_MODIFY_ITEM) extension elds at the item level of Purchase Scheduling
the purchase scheduling agreement Agreements

Purchase Scheduling Change of Header in Scheduling Agreement Modi es values of standard and App Extensibility: Manage
Agreement Header Output extension elds of the output Purchase Scheduling
(MM_PUR_SA_MODIFY_HDR_OUTPFORM) template form at the header level of Agreements
the purchase scheduling agreement

Purchase Scheduling Change of Item in Scheduling Agreement Modi es values of standard and App Extensibility: Manage
Agreement Item Output extension elds of the output Purchase Scheduling
(MM_PUR_SA_MODIFY_ITM_OUTPFORM) template form at the item level of Agreements
the purchase scheduling agreement

This is custom documentation. For more information, please visit the SAP Help Portal 14
10/12/2023

Business Object BAdI ID and Description Short Description Related Links

Central Purchase Change of Field Controls for Central Controls eld properties at the App Extensibility: Manage
Contract Purchase Contracts header, item, and distribution levels Central Purchase
(MM_PUR_S4_CCTR_FLDCTRL_SIMPLE) of central purchase contracts or Contracts
central purchase contract
hierarchies.

Central Purchase Check of Central Purchase Contract Before Validates values of standard and App Extensibility: Manage
Contract Saving (MM_PUR_S4_CCTR_CHECK) extension elds at the header, item, Central Purchase
and distribution levels of central Contracts
purchase contracts or central
purchase contract hierarchies before
the contract is saved.

Central Purchase Change of Central Purchase Contract Modi es values of standard and App Extensibility: Manage
Contract Before Saving extension elds at the header level Central Purchase
(MM_PUR_S4_CCTR_MODIFY_HEADER) of central purchase contracts or Contracts
central purchase contract
hierarchies.

Central Purchase Change of Central Purchase Contract Item Modi es values of standard and App Extensibility: Manage
Contract Before Saving extension elds at the item level of Central Purchase
(MM_PUR_S4_CCTR_MODIFY_ITEM) central purchase contracts or central Contracts
purchase contract hierarchies.

Central Purchase Change of Purchase OAs Created from Modi es data, such as header data, App Extensibility: Manage
Contract Central Purchase Contracts Before item data, or item conditions, in the Central Purchase
Distribution purchase outline agreements to be Contracts
(MM_PUR_S4_CCTR_MOD_DISTR_OA) distributed to a particular connected
system after the central purchase
contract is approved.

Central Purchase Formation of Outline Agreements from In uences the formation of purchase App Extensibility: Manage
Contract Central Purchase Contracts outline agreements based on the Central Purchase
(MM_PUR_S4_CCTR_MAP_TO_OA) central purchase contact data, Contracts
during the split of the central
purchase contact.

Central Purchase Retrieval of Output Form Details for Print Retrieves template details for the App Extensibility: Manage
Contract Preview in Central Purchase Contracts output form for the Print Preview Central Purchase
(MM_PUR_S4_CCTR_PRINT_PREVIEW) feature in central purchase Contracts
contracts.

Central Purchase Mapping of Header Extension Details to Maps the header extension elds App Extensibility: Manage
Contract Distributed Outline Agreements from the Enterprise Service Oriented Central Purchase
(MM_PUR_S4_MAP_DISTR_OA_HEADER) Architecture (ESOA) service Contracts
interface to the header extension
elds of the distributed outline
agreements in the connected
system.

Central Purchase Mapping of Item Extension Details to Maps the item extension elds from App Extensibility: Manage
Contract Distributed Outline Agreements the Enterprise Service Oriented Central Purchase
(MM_PUR_S4_MAP_DISTR_OA_ITEM) Architecture (ESOA) service Contracts
interface to the item extension elds
of the distributed outline agreements
in the connected system.

This is custom documentation. For more information, please visit the SAP Help Portal 15
10/12/2023

Business Object BAdI ID and Description Short Description Related Links

Central Purchase De ne Criteria for Editability of Central De ne criteria for the editability of App Extensibility: Manage
Contract Contracts in SAP S/4HANA System, central contracts created from SAP Central Purchase
created from External Systems Ariba in SAP S/4HANA Cloud. Once Contracts
(MM_PUR_S4_CCTR_EXT_EDITABILITY) you implement this BAdI, the
purchase contract in SAP S/4HANA
Cloud gets decoupled from the
contract in SAP Ariba.

By default, you cannot edit a central


contract in SAP S/4HANA Cloud that
is created from SAP Ariba. However,
with the implementation of this BAdI,
you can edit central contracts in SAP
S/4HANA Cloud.

 Note
Once a central contract is edited
in SAP S/4HANA Cloud, you will
not be able to make any
modi cations from SAP Ariba.

Supplier Invoice Change Data of Consignment Settlement Change supplier invoice data if you Business Add-Ins (BAdIs)
(MMIV_CONSIGNMENT_DATA_MODIFY) use Logistics Consignment and for Invoice Processing
Pipeline Settlement.

Supplier Invoice Change Evaluated Receipt Settlement Change supplier invoice data if you Business Add-Ins (BAdIs)
(ERS) Data use Evaluated Receipt Settlement for Invoice Processing
(MRM_ERS_DATA_Modify_CE) (ERS).

Supplier Invoice Change Invoicing Plan Settlement Data Change supplier invoice data if you Business Add-Ins (BAdIs)
(MRM_MRIS_DATA_MODIFY_CE) settle invoicing plans. for Invoice Processing

Supplier Invoice Change Revaluation Data Change supplier invoice data if you Business Add-Ins (BAdIs)
(MRM_RAP_DATA_MODIFY_CE) use the revaluation function. for Invoice Processing

Supplier Invoice Check of Creating Attachments in Display De ne customer-speci c checks for Business Add-Ins (BAdIs)
Mode parked or posted invoices (both in for Invoice Processing
(MRM_ATTACH_TO_READ_ONLY_CLOUD) display and edit mode). These
checks allow you to prevent
attachments being created and to
prevent attachments being deleted.

Supplier Invoice EDI: Change Invoice Data After Standard This BAdI is called within the Business Add-Ins (BAdIs)
Mapping execution of the SOAP service for Invoice Processing
(LOG_EDI_MM_INVOICE_CE_MAP) Supplier Invoice - Create (B2B,
Inbound, Asynchronous).

Supplier Invoice Intercompany: Change Invoice Data After This BAdI is called within the Business Add-Ins (BAdIs)
Standard Mapping (MMIV_IC_MAPPING) processes of intercompany sales for Invoice Processing
and intercompany stock transfer.

Purchase Requisition, Check of Documents in Business Process Implement checks for various Documentation availabe
Purchase Order Automation documents, such as, purchase within the activity
(MMPUR_BUSPROC_AUTMN_ACTION_CHK) requisitions or purchase orders, in
business process automation.

This is custom documentation. For more information, please visit the SAP Help Portal 16
10/12/2023

Business Object BAdI ID and Description Short Description Related Links

Purchase Requisition, Change of Documents in Business Process Modify various documents, such as, Documentation availabe
Purchase Order Automation purchase requisitions or purchase within the activity
(MMPUR_BUSPROC_AUTMN_ACTION_SET) orders in business process
automation.

Purchase Requisition Change of Self Service Purchase Change the extracted information of Documentation availabe
Requisition in Central Procurement purchase requisitions during their within the activity
(MM_PUR_S4_SSP_HUB_PR_MODIFY) extraction from the connected
systems to the hub system.

Purchase Requisition Change of Purchase Requisitions During Modify the extracted information of App Extensibility: Process
Extraction purchase requisitions during their Purchase Requisitions
(MM_PUR_S4_MODIFY_EXTRACTED_PR) extraction from the connected Centrally
systems to the hub system.

Purchase Order Change of Purchase Order Data During Check the information about the App Extensibility: Manage
Extraction header and item elds of purchase Purchase Orders Centrally
(MM_PUR_S4_MODIFY_EXTRACTED_PR) orders. Additionally, you can also
modify this information based on the
implementation of the BAdI.

Purchase Requisition Determining Work ow Agents for Centrally Determine approvers for the App Extensibility: Process
Managed Purchase Requisitions ( centrally managed purchase Purchase Requisitions
MMPUR_PR_RPL_WORKFLOW_AGENTS) requisitions. You can de ne a list of Centrally
approvers based on this data.

Purchase Order Determining Work ow Agents for Centrally Determine approvers for the App Extensibility: Manage
Managed Purchase Orders ( centrally managed purchase orders. Purchase Orders Centrally
MMPUR_CPO_WORKFLOW_AGENTS) You can de ne a list of approvers
based on this data.

Purchase Order Assigning of Default Values to Search Fields Modify the default values in the Documentation availabe
for Proxy Purchase Orders ( search elds for proxy purchase within the activity
MMPUR_PROXY_PO_SEARCH_FLDS_DEF) orders. Based on the search eld
values, a list of purchase orders is
displayed.

Purchase Requisition Change of Grouping Criteria of Extracted Disable the supplier eld during App Extensibility: Process
PRs During PO Creation ( grouping criteria of extracted Purchase Requisitions
MM_PUR_EXT_PURREQN_GRP_CHANGE) purchase requisitions to create Centrally
purchase orders and enable the
editing of the supplier eld.

Central Purchase Assigning of Default Values to Search Fields Add purchase requisitions to an Documentation availabe
Contracts for Central Purchase Contracts ( existing central purchase contract. within the activity
MMPUR_CCTR_SEARCH_FIELDS_DEF) Also, modify the default values in the
search elds for central purchase
contracts.

Centrally Managed Mapping of Extensible Fields for Centrally Map the elds of the connected App Extensibility: Process
Purchase Requisition Managed Purchase Requisitions system to the hub system. This Purchase Requisitions
(MM_PUR_HUB_PR_FIELD_MAPPING enables the extraction of the Centrally
extensible elds from the connected
system to the hub system.

Centrally Managed Mapping of Extensible Fields for Centrally Map the elds of the connected App Extensibility: Manage
Purchase Order Managed Purchase Orders system to the hub system. This Purchase Orders Centrally
(MM_PUR_HUB_PO_FIELD_MAPPING enables the extraction of the
extensible elds from the connected
system to the hub system.

This is custom documentation. For more information, please visit the SAP Help Portal 17
10/12/2023

Business Object BAdI ID and Description Short Description Related Links

Service Entry Sheet Check of Service Entry Sheet Header Check or validate values of standard App Extensibility: Manage
(M_PUR_S4_SES_CHECK_HEADER) and custom elds in service entry Service Entry Sheets -
sheets on header level. Lean Services

Service Entry Sheet Change of Service Entry Sheet Header Set or change values of standard and App Extensibility: Manage
(M_PUR_S4_SES_MODIFY_HEADER) custom elds in service entry sheets Service Entry Sheets -
on header level. Lean Services

Service Entry Sheet Check of Service Entry Sheet Check or validate values of standard App Extensibility: Manage
ItemMM_PUR_S4_SES_CHECK_ITEM) and custom elds in service entry Service Entry Sheets -
sheets on item level. Lean Services

Service Entry Sheet Change of Service Entry Sheet Item Set or change values of custom App Extensibility: Manage
(MM_PUR_S4_SES_MODIFY_ITEM) elds in service entry sheets on item Service Entry Sheets -
level. Lean Services

Service Entry Sheet Determination of Account Assignment for If you change or add an account App Extensibility: Manage
Commitment Reduction assignment in a service entry sheet, Service Entry Sheets -
(MM_PUR_S4_SES_REDUCE_COMMITMNT) you can use this BAdI to de ne for Lean Services
which account assignment of the
referenced purchase order item the
commitment should be reduced
when the goods receipt is posted.

Service Entry Sheet Determination of Work ow Agents for De ne your own rules for the Work ow Features for
Purchasing Documents determination of recipients in Service Entry Sheets -
(MMPUR_WORKLFOW_AGENTS_V2) work ow steps. You can also exclude Lean Services
restricted agents from being
approvers of service entry sheets.

Service Entry Sheet Providing additional conditions for For a work ow scenario for service Work ow Features for
scenarios entry sheets a list of prede ned Service Entry Sheets -
conditions is delivered. In case you Lean Services
(SWF_WORKFLOW_CONDITION_DEF) need to extend this list, you can
extend the condition list with
additional conditions.

Service Entry Sheet Value evaluation of additional conditions for If you provided additional conditions Work ow Features for
scenarios for a work ow scenario using the Service Entry Sheets -
BAdI Lean Services
(SWF_WORKFLOW_CONDITION_EVAL) SWF_WORKFLOW_CONDITION_DEF,
you must evaluate the values of
these additional conditions using
this BAdI. This gives you control that
depending on your condition,
process instances are started or
steps are created.

Source of Supply Check Source of Supply During Source Determine if a speci c source of n/a
Determination supply can be allowed for a source
(ME_CHK_SRC_DURING_SEARCH) list. You can implement these checks
based on Supplier, Purchasing
Organization, Purchasing Info
Record, or any other combination of
the elds that are available in the
BAdI structure.

This is custom documentation. For more information, please visit the SAP Help Portal 18
10/12/2023

Business Object BAdI ID and Description Short Description Related Links

Source of Supply Additional Checks During Source of Supply Determine if a speci c source of n/a
Check supply must be allowed for a source
(ME_CHK_SRC_DURING_STD_CHECK) list. You can implement the checks
based on Supplier, Purchasing
Organization, Purchasing Info
Record, or any other combination of
the elds available in the BAdI
structure. You can raise an error
message based on the check
condition.

Purchase Contract Change of Field Control for Purchase Change the eld control properties App Extensibility: Manage
Contract Header and Item - of speci c elds in the FIORI user Purchase Contracts
MM_PUR_S4_CTR_MODIFY_FLDCTRL interface at the header and item
levels of the purchase contract.

Purchase Contract Change of Account Assignment in Purchase Modify values of the account App Extensibility: Manage
Contract Item Before Saving - assignment elds at the item level of Purchase Contracts
MM_PUR_S4_CTR_MODIFY_ACCOUNT a purchase contract.

Flexible Work ow Enhancement of Flexible Work ow Based on the context in which it is n/a
(MMPUR_WFL_CONTEXT_ENHANCE) invoked, you can use this BAdI for
the following purposes:

Set agents that need to be


excluded

Set a maximum of ve
custom attributes

Set the priority of a work ow


step or task

Purchase Contract De nition of Conditions to Restart Work ow Enable or disable the restart of the App Extensibility: Manage
in Purchase Contracts approval work ow in purchase Purchase Contracts
(MM_PUR_S4_CTR_WFL_RESTART) contracts. Also, overwrite the
con gurations de ned in
con guration step Manage
Conditions to Restart Flexible
Work ow for Purchase Contracts.

Purchase Contract De nition of Criteria for the Editability of Enables you to edit purchase Contract Management
Purchase Contracts in SAP S/4HANA contracts (in SAP S/4HANA Cloud) with SAP Ariba Contracts
created from External Systems created from SAP Ariba Contracts. (4AZ)
(MM_PUR_S4_CTR_CTRL_EDITABILITY) Once such a purchase contract is
edited in SAP S/4HANA Cloud, it
gets decoupled from SAP Ariba
Contracts.

Purchase Scheduling Handling of Data Change Before Creation of Changes data before the creation of App Extensibility: Manage
Agreement Release Documents for Purchase release documents for purchase Purchase Scheduling
Scheduling Agreements scheduling agreements. Agreements
(MM_PUR_S4_SA_REL_CREATE_BEFORE)

Purchase Scheduling Handling of Data Change After Creation of Changes data after the creation of App Extensibility: Manage
Agreement Release Documents for Purchase release documents for purchase Purchase Scheduling
Scheduling Agreements scheduling agreements. Agreements
(MM_PUR_S4_SA_REL_CREATE_AFTER)

This is custom documentation. For more information, please visit the SAP Help Portal 19
10/12/2023

Business Object BAdI ID and Description Short Description Related Links

Central Purchase Restart of Flexible Work ow for Central Restarts the exible work ow when App Extensibility: Manage
Contract Purchase Contracts central purchase contracts are Central Purchase
(MM_PUR_S4_CCTR_WF_TRGGR) modi ed. It provides the capability Contracts
to overwrite the con guration item
De ne Conditions to Restart
Central Purchase Contract
Processes in the con guration
environment to restart the exible
work ow for central purchase
contracts.

Implementing a Business Add-in (BAdI): Check a Purchase


Requisition
Implementing a Business Add-in (BAdI) to check a purchase requisition.

Implementing a BAdI
A Business Add-In (BAdI) enables you to implement enhancements to standard SAP applications without modifying the original
code. The following scenario demonstrates the implementation of a BAdI to perform custom checks on custom elds and
selected standard elds in purchase requisitions, such as the quantity of items ordered.

Prerequisites
You have installed SAP ABAP Development Tools (ADT), version 3.16 or later, and have created an ABAP Cloud project for
your SAP S/4HANA Cloud system in it.

You must have the business role SAP_BR_PURCHASER assigned to you for the app Manage Purchase Requisitions -
Professional.

Creating a Package
To create a BAdI implementation, you rst have to create a package for your development objects. To create a package,
complete the following steps.

1. Right click on your project and choose New ABAP Package from the menu.

This is custom documentation. For more information, please visit the SAP Help Portal 20
10/12/2023
2. Enter a name and a description for your package and select Add to favorite packages. Note the package name and
description in the below image is for example purposes only.

3. Select Next.

4. The transport dialogue opens automatically when you select next. If you already have an open transport request for your
project, you can select it from the list displayed. If no transport request exists, select Create a new request, enter a
description for your request and select Finish.

This is custom documentation. For more information, please visit the SAP Help Portal 21
10/12/2023

Creating an Enhancement Implementation


To create an enhancement implementation, you need a container within the enhancement spot (MM_PUR_S4_PR ) for your BAdI
implementations.

Find the enhancement spot you want to create the container in by expanding the project and navigating to enhancement spots
and further expanding. In this example, the enhancement spot used is MM_PUR_S4_PR for purchase requisitions as shown in
the following images.

This is custom documentation. For more information, please visit the SAP Help Portal 22
10/12/2023

The following describes the process for creating the enhancement implementation:

1. Select your package and choose New Other ABAP Repository Object from the context menu.

This is custom documentation. For more information, please visit the SAP Help Portal 23
10/12/2023

2. Filter by BAdI and choose BAdI Enhancement Implementation, then choose Next.

3. In the New BAdI Enhancement Implementation editor, enter the name for your enhancement implementation, a
description, and the name of the enhancement spot.

This is custom documentation. For more information, please visit the SAP Help Portal 24
10/12/2023

4. Choose Next, select the required transport request and choose Finish.

Your BAdI enhancement implementation appears in a new editor and implements the enhancement spot
MM_PUR_S4_PR.

Adding the BAdI Implementation


This is custom documentation. For more information, please visit the SAP Help Portal 25
10/12/2023
1. In the BAdI enhancement implementation editor, choose Add BAdI.

2. Add the BAdI de nition by selecting Browse and then add the BAdI implementation name and choose Add.

This is custom documentation. For more information, please visit the SAP Help Portal 26
10/12/2023

 Note
The system generates an error message, you can ignore this message as it is recti ed in the following steps.

This is custom documentation. For more information, please visit the SAP Help Portal 27
10/12/2023

Creating an Implementing Class


1. In the BAdi enhancement implementation editor, choose Implementing Class.

2. In the editor that appears, add the name and description for your implementing class and choose Next. The interface is
added automatically.

This is custom documentation. For more information, please visit the SAP Help Portal 28
10/12/2023
3. Select the required transport request and choose Finish. The implementation class appears in a new editor with skeleton
code.

4. Format, save, and activate your class, you will also need to activate the BAdi implementation to resolve the previous
error.

Implementing Code
To complete the enhancement implementation, you need to add code to the method implementation.

Add the following code to the method implementation, then format, save, and activate your code.

This is custom documentation. For more information, please visit the SAP Help Portal 29
10/12/2023

Testing the BAdI


You can test the BAdI using the app Manage Purchase Requisitions (Professional).

1. Open the app Manage Purchase Requisitions (Professional).

2. Select Create.

This is custom documentation. For more information, please visit the SAP Help Portal 30
10/12/2023

3. In the Items tab, select Create Material .

4. Enter the required plant and material and then enter an incorrect quantity greater than the quantity limit speci ed in
the entered code.

This is custom documentation. For more information, please visit the SAP Help Portal 31
10/12/2023

5. If the implementation is being called correctly, you receive an error message with the quantity limit.

Implementing Field Control Using a Business Add-in (BAdI)


Implementing a Business Add-in (BAdI) to hide a eld by changing the eld control status.

Implementing a BAdI
A Business Add-In (BAdI) enables you to implement enhancements to standard SAP applications without modifying the original
code. The following scenario demonstrates the implementation of a BAdI to hide a selected price eld by changing the eld
control status.

Prerequisites

This is custom documentation. For more information, please visit the SAP Help Portal 32
10/12/2023
You have installed SAP ABAP Development Tools (ADT), version 3.16 or later, and have created an ABAP Cloud project for
your SAP S/4HANA Cloud system in it.

You must have the business role SAP_BR_PURCHASER assigned to you for the app Manage Purchase Requisitions -
Professional.

Creating a Package
To create a BAdI implementation, you rst have to create a package for your development objects. To create a package,
complete the following steps.

1. Right click on your project and choose New ABAP Package from the menu.

2. Enter a name and a description for your package and select Add to favorite packages.

This is custom documentation. For more information, please visit the SAP Help Portal 33
10/12/2023

3. Select Next.

4. The transport dialogue opens automatically when you select next. If you already have an open transport request for your
project, you can select it from the list displayed. If no transport request exists, select Create a new request, enter a
description for your request and select Finish.

This is custom documentation. For more information, please visit the SAP Help Portal 34
10/12/2023

Creating an Enhancement Implementation


To create an enhancement implementation, you need a container within the enhancement spot for your BAdI implementations.

Find the enhancement spot you want to create the container in by expanding the project and navigating to the enhancement
spots and further expanding. In this example, the enhancement spot used is MM_PUR_S4_PR_FLDCNTRL_SIMPLE for purchase
requisition eld control as shown in the following images.

This is custom documentation. For more information, please visit the SAP Help Portal 35
10/12/2023

The following describes the process for creating the enhancement implementation:

1. Select your package and choose New Other ABAP Repository Object from the context menu.

2. Filter by BAdI and choose BAdI Enhancement Implementation, then choose Next.

This is custom documentation. For more information, please visit the SAP Help Portal 36
10/12/2023

3. In the New BAdI Enhancement Implementation editor, enter the name for your enhancement implementation, a
description, and the name of the enhancement spot.

This is custom documentation. For more information, please visit the SAP Help Portal 37
10/12/2023

4. Choose Next, select the required transport request and choose Finish.

Your BAdI enhancement implementation appears in a new editor and implements the enhancement spot
MM_PUR_S4_PR_FLDCNTRL_SIMPLE.

Adding the BAdI Implementation


This is custom documentation. For more information, please visit the SAP Help Portal 38
10/12/2023
1. In the BAdI enhancement implementation editor, choose Add BAdI.

2. Add the BAdI de nition by selecting Browse, select the BAdI, enter the BAdI implementation name and choose Add.

 Note
The system generates an error message, you can ignore this message as it is recti ed in the following steps.

Creating an Implementing Class


1. In the BAdi enhancement implementation editor, choose Implementing Class.

This is custom documentation. For more information, please visit the SAP Help Portal 39
10/12/2023

2. In the editor that appears, add the name and description for your implementing class and choose Next. The interface is
added automatically.

This is custom documentation. For more information, please visit the SAP Help Portal 40
10/12/2023
3. Select the required transport request and choose Finish. The implementation class appears in a new editor with skeleton
code.

4. Format, save, and activate your class, you will also need to activate the BAdi implementation to resolve the previous
error.

Implementing Code
To complete the enhancement implementation, you need to add code to the method implementation.

Add the following code to the method implementation, then format, save, and activate your code.

This is custom documentation. For more information, please visit the SAP Help Portal 41
10/12/2023

Extensibility for Purchase Requisition Apps


You can extend the following apps according to your business needs:

Change Purchase Requisitions

Display Purchase Requisitions

Features
Key users can extend the apps in the Custom Fields app using the business context Procurement: Purchase Requisition Item.

You can enable usage of your custom elds for the data source Purchase Requisition Item GUI in the UIs and Reports section of
the custom eld maintenance and publish your custom elds.

Business users can display elds that you have enabled in the Custom Fields app. The elds that you enable for this app are
included in the personalization options for business users for the following UI elements:

UI Element Business Context

Item Details Custom Fields Procurement: Purchase Requisition Item

Related Information
This is custom documentation. For more information, please visit the SAP Help Portal 42
10/12/2023
Custom Fields App and Custom Logic App
Key User Extensibility

App Extensibility: Create Purchase Requisition

Use
You can extend the Create Purchase Requisition app according to your business needs.

Features
Key users can extend the app in the Custom Fields app and the Custom Logic app using the business context Procurement:
Purchase Requisition Item.

You can enable usage of your custom elds for the data source Purchase Requisition Item GUI in the UIs and Reports section of
the custom eld maintenance and publish your custom elds.

You can add elds to the following UI elements using UI adaption at runtime:

UI Element Business Context

Create Own Item General Data Procurement: Purchase Requisition


Item

For more information about how to adapt an SAP Fiori UI at runtime, see Making UI Changes (Object Pages).

In the Custom Logic app, you can implement logic for the following Business Add-Ins (BAdIs):

Business Add-Ins (BAdIs) Business Context Business Use

Check of Purchase Requisition Item Procurement: Purchase Requisition Item Check or validate values of standard and
(MM_PUR_S4_PR_CHECK) extension elds in purchase requisitions at
item level.

Change of Purchase Requisition Item Procurement: Purchase Requisition Item Set or change values of standard and
(MM_PUR_S4_PR_MODIFY_ITEM) extension elds in purchase requisitions at
item level.

Change of OCI 4.0 Outbound Parameters for Procurement: Purchasing Catalogs and Modify the outbound parameters that are
Purchase Requisitions Catalog Interfaces sent to the catalog provider using the open
(MMPUR_OCI_OUTBOUND_PARAMETERS) catalog web service.

Change of Field Control for Purchase Procurement: Purchase Requisition Item Modify the properties of different elds
Requisitions that appear on the user interface of
(MM_PUR_S4_PR_FLDCNTRL_SIMPLE) purchase requisition apps.

Change of Self Service Purchase Requisition Procurement: Purchase Requisition Item Modify extension elds and check header
in Central Procurement and item level information of self-service
(MM_PUR_S4_SSP_HUB_PR_MODIFY) purchase requisitions during simulation and
replication from hub system to connected
system.

Speci cation of Proxy Server During OCI Procurement: Purchase Requisition Item Specify proxy server settings to access
Validation (MMPUR_CAT_PROXY_INFO) internet during catalog extraction.

This is custom documentation. For more information, please visit the SAP Help Portal 43
10/12/2023

Business Add-Ins (BAdIs) Business Context Business Use

De nition of Conditions to Restart Flexible Procurement: Purchase Requisition Item Enable or disable the restart of the
Work ow in Purchase Requisitions approval work ow in purchase requisitions.
(MM_PUR_S4_PR_WFL_RESTART) Also, overwrite the con gurations de ned in
con guration step Manage Conditions to
Restart Flexible Work ow.

Determination of Work ow Agents for Procurement: Flexible Work ow Implement your own work ow agent
Purchasing Documents determination. Based on the document
(MMPUR_WORKFLOW_AGENTS_V2) data, you can de ne a list of approvers.

Enhancement of Flexible Work ow Procurement: Flexible Work ow Based on the context in which it is invoked,
Properties you can use this BAdI for the following
(MMPUR_WFL_CONTEXT_ENHANCE) purposes:

Set agents that need to be excluded

Set a maximum of ve custom


attributes

Set the priority of a work ow step or


task

Setting of Default Delivery Address of Self- Procurement: Purchase Requisition Item Maintain the default delivery address of a
Service Purchase Requisition self-service purchase requisition item.
(MM_PUR_SSP_DEF_DEL_ADRS_SIMPLE)

Change of Draft Item of a Self-Service Procurement: Purchase Requisition Item Set prede ned values for elds during the
Purchase Requisition creation of self-service purchase
(MM_PUR_S4_SSPPR_MOD_DRAFT_ITEM) requisition.

Check of Draft Item of a Self-Service Procurement: Purchase Requisition Item Check the data entered in various elds,
Purchase Requisition while a purchase requisition is being
(MM_PUR_S4_SSPPR_CHK_DRAFT_ITEM) created and is in draft state.

Change of OCI 4.0 Data When Mapping to Procurement: Purchasing Catalogs and Modify data when mapping OCI 4.0 data to
Draft Item of Self-Service Purchase Catalog Interfaces draft items in self-service purchase
Requisition requisition.
(MMPUR_OCI_TO_DRAFT_ITM_MAPPING)

Change of OCI 4.0 Data When Mapping to a Procurement: Purchasing Catalogs and Access the master data of a catalog
Purchase Requisition Item Catalog Interfaces provider, and add or remove items
(MMPUR_OCI_ITEM_TRANSFER_DATA) automatically from a catalog during the
transfer of data.

Change of Header of a Purchase Requisition Procurement: Purchase Requisition Item Set or change values of standard and
(MM_PUR_S4_PR_MODIFY_HEADER) extension elds in purchase requisitions at
header level.

Related Information
Creating Implementations
Custom Fields App and Custom Logic App
Key User Extensibility

App Extensibility: My Purchase Requisitions

Use
This is custom documentation. For more information, please visit the SAP Help Portal 44
10/12/2023
You can extend the My Purchase Requisitions app according to your business needs.

Features
Key users can extend the app in the Custom Fields app and the Custom Logic app using the business context Procurement:
Purchase Requisition Item.

You can enable usage of your custom elds for the app in the UIs and Reports section of the custom eld maintenance and
publish your custom elds.

You can add elds to the following UI elements using UI adaption at runtime:

UI Element Business Context

General Data Procurement: Purchase Requisition Item

For more information about how to adapt an SAP Fiori UI at runtime, see Making UI Changes (Object Pages).

In the Custom Logic app, you can implement logic for the following Business Add-Ins (BAdIs):

Business Add-Ins (BAdIs) Business Context Business Use

Check of Purchase Requisition Item Procurement: Purchase Requisition Item Check or validate values of standard and
(MM_PUR_S4_PR_CHECK) extension elds in purchase requisitions at
item level.

Change of Purchase Requisition Item Procurement: Purchase Requisition Item Set or change values of standard and
(MM_PUR_S4_PR_MODIFY_ITEM) extension elds in purchase requisitions at
item level.

Change of OCI 4.0 Outbound Parameters Procurement: Purchasing Catalogs and Modify the outbound parameters that are
(MMPUR_OCI_OUTBOUND_PARAMETERS) Catalog Interfaces sent to the catalog provider using the open
catalog web service.

Change of Field Control for Purchase Procurement: Purchase Requisition Item Modify the properties of different elds
Requisitions that appear on the user interface of
(MM_PUR_S4_PR_FLDCNTRL_SIMPLE) purchase requisition apps.

Change of Self Service Purchase Requisition Procurement: Purchase Requisition Item Modify extension elds and check header
in Central Procurement and item level information of self-service
(MM_PUR_S4_SSP_HUB_PR_MODIFY) purchase requisitions during simulation and
replication from hub system to connected
system.

Speci cation of Proxy Server During OCI Procurement: Purchase Requisition Item Specify proxy server settings to access
Validation (MMPUR_CAT_PROXY_INFO) internet during catalog extraction.

De ne Conditions to Restart Flexible Procurement: Purchase Requisition Item Enable or disable the restart of the
Work ow in Purchase Requisitions approval work ow in purchase requisitions.
(MM_PUR_S4_PR_WFL_RESTART) Also, overwrite the con gurations de ned in
con guration step Manage Conditions to
Restart Flexible Work ow.

Determination of Work ow Agents for Procurement: Flexible Work ow Implement your own work ow agent
Purchasing Documents determination. Based on the document
(MMPUR_WORKFLOW_AGENTS_V2) data, you can de ne a list of approvers.

Determination of Factory Calendar for Procurement: Flexible Work ow Determine the factory calendar that can be
Work ow Deadline used for deadline calculation in exible
(MMPUR_PROC_WF_FACTORY_CALENDAR) work ows.

This is custom documentation. For more information, please visit the SAP Help Portal 45
10/12/2023

Business Add-Ins (BAdIs) Business Context Business Use

Enhancement of Flexible Work ow Procurement: Flexible Work ow Based on the context in which it is invoked,
Properties you can use this BAdI for the following
(MMPUR_WFL_CONTEXT_ENHANCE) purposes:

Set agents that need to be excluded

Set a maximum of ve custom


attributes

Set the priority of a work ow step or


task

Setting of Default Delivery Address of Self- Procurement: Purchase Requisition Item Maintain the default delivery address of a
Service Purchase Requisition self-service purchase requisition item.
(MM_PUR_SSP_DEF_DEL_ADRS_SIMPLE)

Change of Draft Item of a Self-Service Procurement: Purchase Requisition Item Set prede ned values for elds during the
Purchase Requisition creation of self-service purchase
(MM_PUR_S4_SSPPR_MOD_DRAFT_ITEM) requisition.

Check of Draft Item of a Self-Service Procurement: Purchase Requisition Item Check the data entered in various elds,
Purchase Requisition while a purchase requisition is being
(MM_PUR_S4_SSPPR_CHK_DRAFT_ITEM) created and is in draft state.

Change of OCI 4.0 Data When Mapping to Procurement: Purchasing Catalogs and Modify data when mapping OCI 4.0 data to
Draft Item of Self-Service Purchase Catalog Interfaces draft items in self-service purchase
Requisition requisition.
(MMPUR_OCI_TO_DRAFT_ITM_MAPPING)

Change of OCI 4.0 Data When Mapping to a Procurement: Purchasing Catalogs and Access the master data of a catalog
Purchase Requisition Item Catalog Interfaces provider, and add or remove items
(MMPUR_OCI_ITEM_TRANSFER_DATA) automatically from a catalog during the
transfer of data.

Change of Header of a Purchase Requisition Procurement: Purchase Requisition Item Set or change values of standard and
(MM_PUR_S4_PR_MODIFY_HEADER) extension elds in purchase requisitions at
header level.

Related Information
Custom Fields App and Custom Logic App
Key User Extensibility

App Extensibility: My Purchase Requisitions - New


As a key user, you can extend the My Purchase Requisitions - New app according to your business needs.

Custom Fields
With the Custom Fields app, you can create and maintain custom elds that you can use to enhance applications. You can add
elds to the following UI elements using key user adaptation:

Business Context UI Technology Navigation Path

Procurement: Purchase Requisition Item SAP Fiori Purchase Requisition Item > General
Information

This is custom documentation. For more information, please visit the SAP Help Portal 46
10/12/2023

For more information, see:

Custom Fields

Adding Extension Fields to Apps with Different UI Technologies

Custom Logic
With the Custom Logic app, you can create and maintain implementations of custom logic that can be used to enhance
applications and change application behavior. You can implement custom logic for the following Business Add-Ins (BAdIs):

Business Add-Ins (BAdIs) Business Context Business Use

Check of Purchase Requisition Item Procurement: Purchase Requisition Item Check or validate values of standard and
(MM_PUR_S4_PR_CHECK) extension elds in purchase requisitions at
item level.

Change of Purchase Requisition Item Procurement: Purchase Requisition Item Set or change values of standard and
(MM_PUR_S4_PR_MODIFY_ITEM) extension elds in purchase requisitions at
item level.

Change of OCI 4.0 Outbound Parameters Procurement: Purchasing Catalogs and Modify the outbound parameters that are
(MMPUR_OCI_OUTBOUND_PARAMETERS) Catalog Interfaces sent to the catalog provider using the open
catalog web service.

Change of Field Control for Purchase Procurement: Purchase Requisition Item Modify the properties of different elds
Requisitions that appear on the user interface of
(MM_PUR_S4_PR_FLDCNTRL_SIMPLE) purchase requisition apps.

Change of Self Service Purchase Requisition Procurement: Purchase Requisition Item Modify extension elds and check header
in Central Procurement and item level information of self-service
(MM_PUR_S4_SSP_HUB_PR_MODIFY) purchase requisitions during simulation and
replication from hub system to connected
system.

Speci cation of Proxy Server During OCI Procurement: Purchase Requisition Item Specify proxy server settings to access
Validation (MMPUR_CAT_PROXY_INFO) internet during catalog extraction.

De ne Conditions to Restart Flexible Procurement: Purchase Requisition Item Enable or disable the restart of the
Work ow in Purchase Requisitions approval work ow in purchase requisitions.
(MM_PUR_S4_PR_WFL_RESTART) Also, overwrite the con gurations de ned in
con guration step Manage Conditions to
Restart Flexible Work ow.

Determination of Work ow Agents for Procurement: Flexible Work ow Implement your own work ow agent
Purchasing Documents determination. Based on the document
(MMPUR_WORKFLOW_AGENTS_V2) data, you can de ne a list of approvers.

Determination of Factory Calendar for Procurement: Flexible Work ow Determine the factory calendar that can be
Work ow Deadline used for deadline calculation in exible
(MMPUR_PROC_WF_FACTORY_CALENDAR) work ows.

This is custom documentation. For more information, please visit the SAP Help Portal 47
10/12/2023

Business Add-Ins (BAdIs) Business Context Business Use

Enhancement of Flexible Work ow Procurement: Flexible Work ow Based on the context in which it is invoked,
Properties you can use this BAdI for the following
(MMPUR_WFL_CONTEXT_ENHANCE) purposes:

Set agents that need to be excluded

Set a maximum of ve custom


attributes

Set the priority of a work ow step or


task

Setting of Default Delivery Address of Self- Procurement: Purchase Requisition Item Maintain the default delivery address of a
Service Purchase Requisition self-service purchase requisition item.
(MM_PUR_SSP_DEF_DEL_ADRS_SIMPLE)

Change of OCI 4.0 Data When Mapping to Procurement: Purchasing Catalogs and Modify data when mapping OCI 4.0 data to
Draft Item of Self-Service Purchase Catalog Interfaces draft items in self-service purchase
Requisition requisition.
(MMPUR_OCI_TO_DRAFT_ITM_MAPPING)

Change of OCI 4.0 Data When Mapping to a Procurement: Purchasing Catalogs and Access the master data of a catalog
Purchase Requisition Item Catalog Interfaces provider, and add or remove items
(MMPUR_OCI_ITEM_TRANSFER_DATA) automatically from a catalog during the
transfer of data.

Change of Header of a Purchase Requisition Procurement: Purchase Requisition Item Set or change values of standard and
(MM_PUR_S4_PR_MODIFY_HEADER) extension elds in purchase requisitions at
header level.

Calculation of Transient Custom Fields in Procurement: Purchase Requisition Item Calculate transient custom elds using the
'Manage Purchase Requisitions - values of the standard elds and custom
Professional' elds in a purchase requisition item.
(MMPUR_SSPPR_ITM_CALC_FIELDS)

For more information, see:

Custom Logic

For more information about the individual BAdIs, check the BAdI-speci c documentation: Custom Logic <your
implementation > BAdI Documentation View BAdI Documentation

Related Information
Extensibility

App Extensibility: Manage Purchase Requisitions - Professional


You can extend the Manage Purchase Requisitions - Professional app according to your business needs.

Features
Key users can extend the app in the Custom Fields app and the Custom Logic app using the business context Procurement:
Purchase Requisition Item.

This is custom documentation. For more information, please visit the SAP Help Portal 48
10/12/2023
You can enable usage of your custom elds for the data sources Maintain Purchase Requisition Extensibility Model and
Purchase Requisition Basic Item View in the UIs and Reports section of the custom eld maintenance and publish your custom
elds.

You can add elds to the following UI elements using UI adaptation at runtime:

UI Element Business Context

Purchase Requisition Items Procurement: Purchase Requisition Item

For more information about how to adapt an SAP Fiori UI at runtime, see Making UI Changes (Object Pages).

In the Custom Logic app, You can implement logic for the following Business Add-Ins (BAdIs):

Business Add-Ins (BAdIs) Business Context Business Use

Check of Purchase Requisition Item Procurement: Purchase Requisition Item Check or validate values of standard and
(MM_PUR_S4_PR_CHECK) extension elds in purchase requisitions at
item level.

Change of Purchase Requisition Item Procurement: Purchase Requisition Item Set or change values of standard and
(MM_PUR_S4_PR_MODIFY_ITEM) extension elds in purchase requisitions at
item level.

Change of OCI 4.0 Outbound Parameters Procurement: Purchasing Catalogs and Modify the outbound parameters that are
(MMPUR_OCI_OUTBOUND_PARAMETERS) Catalog Interfaces sent to the catalog provider using the open
catalog web service.

Change of Field Control for Purchase Procurement: Purchase Requisition Item Modify the properties of different elds
Requisitions that appear on the user interface of
(MM_PUR_S4_PR_FLDCNTRL_SIMPLE) purchase requisition apps.

Speci cation of Proxy Server During OCI Procurement: Purchase Requisition Item Specify proxy server settings to access
Validation (MMPUR_CAT_PROXY_INFO) internet during catalog extraction.

De nition of Conditions to Restart Flexible Procurement: Purchase Requisition Item Enable or disable the restart of the
Work ow in Purchase Requisitions approval work ow in purchase requisitions.
(MM_PUR_S4_PR_WFL_RESTART) Also, overwrite the con gurations de ned in
con guration step Manage Conditions to
Restart Flexible Work ow.

Determination of Work ow Agents for Procurement: Flexible Work ow Implement your own work ow agent
Purchasing Documents determination. Based on the document
(MMPUR_WORKFLOW_AGENTS_V2) data, you can de ne a list of approvers.

Determination of Factory Calendar for Procurement: Flexible Work ow Determine the factory calendar that can be
Work ow Deadline used for deadline calculation in exible
(MMPUR_PROC_WF_FACTORY_CALENDAR) work ows.

Enhancement of Flexible Work ow Procurement: Flexible Work ow Based on the context in which it is invoked,
Properties you can use this BAdI for the following
(MMPUR_WFL_CONTEXT_ENHANCE) purposes:

Set agents that need to be excluded

Set a maximum of ve custom


attributes

Set the priority of a work ow step or


task

This is custom documentation. For more information, please visit the SAP Help Portal 49
10/12/2023

Business Add-Ins (BAdIs) Business Context Business Use

Change of OCI 4.0 Data When Mapping to a Procurement: Purchasing Catalogs and Access the master data of a catalog
Purchase Requisition Item Catalog Interfaces provider, and add or remove items
(MMPUR_OCI_ITEM_TRANSFER_DATA) automatically from a catalog during the
transfer of data.

Change of Header of a Purchase Requisition Procurement: Purchase Requisition Item Set or change values of standard and
(MM_PUR_S4_PR_MODIFY_HEADER) extension elds in purchase requisitions at
header level.

Calculation of Transient Custom Fields in Procurement: Purchase Requisition Item Calculate transient custom elds using the
'Manage Purchase Requisitions - values of the standard elds and custom
Professional' elds in a purchase requisition item.
(MMPUR_PR_PROFNL_ITM_CTF)

Related Information
Custom Fields App and Custom Logic App
Key User Extensibility

App Extensibility: Create Purchase Requisition - Advanced


You can extend the Create Purchase Requisition - Advanced app according to your business needs.

Features
Key users can extend the app in the Custom Fields app and the Custom Logic app using the business context Procurement:
Purchase Requisition Item.

You can enable usage of your custom elds for the data source Purchase Requisition Item GUI in the UIs and Reports section of
the custom eld maintenance and publish your custom elds.

Business users can display elds that you have enabled in the Custom Fields app. The elds that you enable for this app are
included in the personalization options for business users for the following UI elements:

UI Element Business Context

Item Details Custom Fields Procurement: Purchase Requisition Item

In the Custom Logic app, you can implement logic for the following Business Add-Ins (BAdIs):

Business Add-Ins (BAdIs) Business Context Business Use

Check of Purchase Requisition Item Procurement: Purchase Requisition Item Check or validate values of standard and
(MM_PUR_S4_PR_CHECK) extension elds in purchase requisitions at
item level.

Change of Purchase Requisition Item Procurement: Purchase Requisition Item Set or change values of standard and
(MM_PUR_S4_PR_MODIFY_ITEM) extension elds in purchase requisitions at
item level.

Change of OCI 4.0 Outbound Parameters Procurement: Purchasing Catalogs and Modify the outbound parameters that are
(MMPUR_OCI_OUTBOUND_PARAMETERS) Catalog Interfaces sent to the catalog provider using the open
catalog web service.

This is custom documentation. For more information, please visit the SAP Help Portal 50
10/12/2023

Business Add-Ins (BAdIs) Business Context Business Use

Change of Field Control for Purchase Procurement: Purchase Requisition Item Modify the properties of different elds
Requisitions that appear on the user interface of
(MM_PUR_S4_PR_FLDCNTRL_SIMPLE) purchase requisition apps.

De nition of Conditions to Restart Flexible Procurement: Purchase Requisition Item Enable or disable the restart of the
Work ow in Purchase Requisitions approval work ow in purchase requisitions.
(MM_PUR_S4_PR_WFL_RESTART) Also, overwrite the con gurations de ned in
con guration step Manage Conditions to
Restart Flexible Work ow.

Determination of Work ow Agents for Procurement: Flexible Work ow Implement your own work ow agent
Purchasing Documents determination. Based on the document
(MMPUR_WORKFLOW_AGENTS_V2) data, you can de ne a list of approvers.

Determination of Factory Calendar for Procurement: Flexible Work ow Determine the factory calendar that can be
Work ow Deadline used for deadline calculation in exible
(MMPUR_PROC_WF_FACTORY_CALENDAR) work ows.

Enhancement of Flexible Work ow Procurement: Flexible Work ow Based on the context in which it is invoked,
Properties you can use this BAdI for the following
(MMPUR_WFL_CONTEXT_ENHANCE) purposes:

Set agents that need to be excluded

Set a maximum of ve custom


attributes

Set the priority of a work ow step or


task

Change of OCI 4.0 Data When Mapping to a Procurement: Purchasing Catalogs and Access the master data of a catalog
Purchase Requisition Item Catalog Interfaces provider, and add or remove items
(MMPUR_OCI_ITEM_TRANSFER_DATA) automatically from a catalog during the
transfer of data.

Change of Header of a Purchase Requisition Procurement: Purchase Requisition Item Set or change values of standard and
(MM_PUR_S4_PR_MODIFY_HEADER) extension elds in purchase requisitions at
header level.

Related Information
Custom Fields App and Custom Logic App
Key User Extensibility

App Extensibility: Purchase Requisition Object Page


As a key user, you can extend the Purchase Requisition object page according to your business needs.

Custom Fields
With the Custom Fields app, you can create and maintain custom elds that you can use to enhance applications. You can add
elds to the following UI elements using key user adaptation:

Business Context UI Technology Navigation Path UI Element Type

This is custom documentation. For more information, please visit the SAP Help Portal 51
10/12/2023

Business Context UI Technology Navigation Path UI Element Type

Procurement: Purchase SAP Fiori Purchase Requisition > Items Table


Requisition Item

Procurement: Purchase SAP Fiori Purchase Requisition > Limit Table


Requisition Item Items

For more information, see:

Custom Fields

Adding Extension Fields to Apps with Different UI Technologies

Custom Logic
With the Custom Logic app, you can create and maintain implementations of custom logic that can be used to enhance
applications and change application behavior. You can implement custom logic for the following Business Add-Ins (BAdIs):

Business Add-Ins (BAdIs) Business Context Business Use

Calculation of Transient Custom Fields in Procurement: Purchase Requisition Item Calculate transient custom elds using the
PR FactSheet values of the standard elds and custom
(MMPUR_PRFS_ITM_CALC_FIELDS) elds in a purchase requisition item.

Related Information
Extensibility

App Extensibility: Purchase Requisition Item Object Page


As a key user, you can extend the Purchase Requisition Item object app according to your business needs.

Custom Fields
With the Custom Fields app, you can create and maintain custom elds that you can use to enhance applications. You can add
elds to the following UI elements using key user adaptation:

Business Context UI Technology Navigation Path UI Element Type

Procurement: Purchase SAP Fiori Purchase Requisition > Items Table


Requisition Item

Procurement: Purchase SAP Fiori Purchase Requisition > Limit Table


Requisition Item Items

For more information, see:

Custom Fields

Adding Extension Fields to Apps with Different UI Technologies

Custom Logic

This is custom documentation. For more information, please visit the SAP Help Portal 52
10/12/2023
With the Custom Logic app, you can create and maintain implementations of custom logic that can be used to enhance
applications and change application behavior. You can implement custom logic for the following Business Add-Ins (BAdIs):

Business Add-Ins (BAdIs) Business Context Business Use

Calculation of Transient Custom Fields in Procurement: Purchase Requisition Item Calculate transient custom elds using the
PR FactSheet values of the standard elds and custom
(MMPUR_PRFS_ITM_CALC_FIELDS) elds in a purchase requisition item.

Related Information
Extensibility

App Extensibility: Edit and Approve Purchase Requisition


As a key user, you can extend the Edit and Approve Purchase Requisition app according to your business needs.

Custom Fields
With the Custom Fields app, you can create and maintain custom elds that you can use to enhance applications. You can add
elds to the following UI elements using key user adaptation:

Business Context UI Technology Navigation Path UI Element Type

Procurement: Purchase SAP Fiori Purchase Requisition > Items Table


Requisition Item

Procurement: Purchase SAP Fiori Purchase Requisition > Limit Table


Requisition Item Items

For more information, see:

Custom Fields

Adding Extension Fields to Apps with Different UI Technologies

Custom Logic
With the Custom Logic app, you can create and maintain implementations of custom logic that can be used to enhance
applications and change application behavior. You can implement custom logic for the following Business Add-Ins (BAdIs):

Business Add-Ins (BAdIs) Business Context Business Use

Check of Purchase Requisition Item Procurement: Purchase Requisition Item Check or validate values of standard and
(MM_PUR_S4_PR_CHECK) extension elds in purchase requisitions at
item level.

Change of Purchase Requisition Item Procurement: Purchase Requisition Item Set or change values of standard and
(MM_PUR_S4_PR_MODIFY_ITEM) extension elds in purchase requisitions at
item level.

This is custom documentation. For more information, please visit the SAP Help Portal 53
10/12/2023

Business Add-Ins (BAdIs) Business Context Business Use

De nition of Conditions to Restart Flexible Procurement: Purchase Requisition Item Enable or disable the restart of the
Work ow in Purchase Requisitions approval work ow in purchase requisitions.
(MM_PUR_S4_PR_WFL_RESTART) Also, overwrite the con gurations de ned in
con guration step Manage Conditions to
Restart Flexible Work ow.

Determination of Work ow Agents for Procurement: Flexible Work ow Implement your own work ow agent
Purchasing Documents determination. Based on the document
(MMPUR_WORKFLOW_AGENTS_V2) data, you can de ne a list of approvers.

Determination of Factory Calendar for Procurement: Flexible Work ow Determine the factory calendar that can be
Work ow Deadline used for deadline calculation in exible
(MMPUR_PROC_WF_FACTORY_CALENDAR) work ows.

Enhancement of Flexible Work ow Procurement: Flexible Work ow Based on the context in which it is invoked,
Properties you can use this BAdI for the following
(MMPUR_WFL_CONTEXT_ENHANCE) purposes:

Set agents that need to be excluded

Set a maximum of ve custom


attributes

Set the priority of a work ow step or


task

Change of Header of a Purchase Requisition Procurement: Purchase Requisition Item Set or change values of standard and
(MM_PUR_S4_PR_MODIFY_HEADER) extension elds in purchase requisitions at
header level.

For more information, see:

Custom Logic

For more information about the individual BAdIs, check the BAdI-speci c documentation: Custom Logic <your
implementation > BAdI Documentation View BAdI Documentation

Related Information
Extensibility

App Extensibility: Assign and Process Purchase Requisitions


You can extend the Assign and Process Purchase Requisitions app according to your business needs.

Features
Key users can extend the app in the Custom Fields app using the business context Procurement: Purchase Requisition Item.

You can enable usage of your custom elds for the data source Purchase Requisition Item GUI for purchase requisitions and for
the data source Purchase Order Item GUI for purchase orders in the UIs and Reports section of the custom eld maintenance
and publish your custom elds.

Key users can also make custom elds available in several apps including handing over data by using business scenarios. After
enabling the custom eld for a business scenario, the value of this eld will be copied between the corresponding documents.

This is custom documentation. For more information, please visit the SAP Help Portal 54
10/12/2023
For the business context Procurement: Purchase Requisition Item, the following business scenarios are available:

Purchase Requisition Item to Purchasing Document Item on item level

Business users can display elds that you have enabled in the Custom Fields app. The elds that you enable for this app are
included in the personalization options for business users for the following UI elements:

UI Element Business Context

Item Details Custom Fields Procurement: Purchase Requisition Item

Restrictions
The number of custom elds to be displayed in the Custom Fields section on either header or item level is limited to 170.

Related Information
Custom Fields App and Custom Logic App
Key User Extensibility

Extensibility for Purchase Order Apps


You can extend the following advanced apps according to your business needs:

Create Purchase Order - Advanced

Change Purchase Order - Advanced

Display Purchase Order

Features
Key users can extend the apps using the following business contexts:

Procurement: Purchasing Document

Procurement: Purchasing Document Item

After enabling the custom elds for the data source Purchase Order GUI Application or Purchase Order Item GUI in the UIs and
Reports section of the custom eld maintenance in the Custom Fields app, the custom elds will show up in the Custom Fields
section in the header or item details of the purchase order .

You can add elds to the following UI elements using UI adaptation at runtime:

UI Element Business Context

Header Custom Fields Procurement: Purchasing Document

Item Detail Custom Fields Procurement: Purchasing Document Item

 Note
Please note that the section Custom Fields will only appear onscreen if there are custom elds enabled for the current app.

This is custom documentation. For more information, please visit the SAP Help Portal 55
10/12/2023
For more information about how to adapt an SAP Fiori UI at runtime, see Making UI Changes (Object Pages).

For the above apps, you can implement logic for the following Business Add-Ins (BAdIs) in the Custom Logic app:

Business Add-Ins (BAdIs) for Purchase Orders

BAdI ID and Description Short Description

Change of Field Control for Purchase Order Header With this BAdI, you can
(MM_PUR_S4_PO_FLDCNTRL_SIMPLE_H)
Change the eld control in purchase order apps by modifying the
properties of speci c elds on header level. These elds can be
made hidden, read-only, mandatory, or optional.

Change of Field Control for Purchase Order Item With this BAdI, you can
(MM_PUR_S4_PO_FLDCNTRL_SIMPLE)
Change the eld control in purchase order apps by modifying the
properties of speci c elds on item level. These elds can be
made hidden, read-only, mandatory, or optional.

Close Purchase Order (MM_PUR_S4_PO_CLOSE) With this BAdI, you can

Reset your own programs.

Final Check before Saving Purchase Order With this BAdI, you can
(BD_MMPUR_FINAL_CHECK_PO)
Implement own checks before a purchase order is saved.

Control of Pricing Type: Additional Fields With this BAdI, you can
(MM_PUR_S4_PO_DEFINE_CNDNCTRL)
Control the price determination process when creating or changing
a purchase order. When a purchase order is created or changed, the
system carries out a price determination process at various points
in the process. The type of price determination (pricing type)
depends on the relevant status of the ordering transcations. Among
others, the following types are possible:

Pricing type B (Carry out new pricing): Always invoked


when you create a new PO item

Pricing type C (Copy manual pricing elements and


redetermine the others): Invoked when you change data that
can in uence the price determination process at item level,
for example when you change the account assignment
category)

Using this BAdI, you can de ne the conditions for triggering a price
determination process that differ from those of the standard
system. You can specify the pricing type in this case. This is of
interest, when you determine prices via conditions and, in the
process, make use of elds that are not taken into account in the
condition tables supplied.

Final Check before Saving Purchase Order With this BAdI, you can
(BD_MMPUR_FINAL_CHECK_PO)
Implement own checks before a purchase order is saved.

Initialize Purchase Order (MM_PUR_S4_PO_INITIALIZE) With this BAdI, you can

Initialize data when starting to work with a purchase order.

This is custom documentation. For more information, please visit the SAP Help Portal 56
10/12/2023

BAdI ID and Description Short Description

Modify Purchase Order Account Assignment Data With this BAdI, you can
(MM_PUR_S4_PO_MODIFY_ACCOUNT)
Implement own checks and raise messages by lling the
changing parameter table MESSAGES.

Make changes to elds on account assignment level.


Changes to the following elds are possible:

GLACCOUNT, COSTCENTER, PROFITCENTER,


PROJECTNETWORK, WBSELEMENTINTERNALID,
MASTERFIXEDASSET, SALESORDER, SALESORDERITEM,
UNLOADINGPOINT, CONTROLLINGAREA,
FUNCTIONALAREA, SERVICEDOCUMENTTYPE,
SERVICEDOCUMENTID, SERVICEDOCUMENTITEMID,
GOODSRECIPIENTNAME, ORDERID

Modify Purchase Order Header With this BAdI, you can


(MM_PUR_S4_PO_MODIFY_HEADER)
Set or change values of custom elds in purchase orders on header
level.

Modify Purchase Order Item (MM_PUR_S4_PO_MODIFY_ITEM) With this BAdI, you can

Set or change values of custom elds in purchase orders on


item level and make changes to the following elds:

TAXCODE, TAXCOUNTRY, INCOTERMSCLASSIFICATION,


INCOTERMSTRANSFERLOCATION,
INCOTERMSLOCATION1, INCOTERMSLOCATION2,
SHIPPINGTYPE, PURCHASINGINFORECORDUPDATECODE

 Note
PURCHASINGINFORECORDUPDATECODE is an optional
parameter and the available values are:

Fixed Short Description

No update

A Update with or without


plant

B Update with plant (if no


plant ban)

C Update without plant (if


no plant requirement)

Use the optional importing parameter:


PURCHASEORDERITEM_OLD. This parameter contains the
item data of the previous roundtrip, for example, the data
before the last change was done.

Raise messages by lling the changing parameter table


MESSAGES

This is custom documentation. For more information, please visit the SAP Help Portal 57
10/12/2023

BAdI ID and Description Short Description

Modify Purchase Order Item Delivery Address With this BAdI, you can
(MM_PUR_S4_PO_MODIFY_DELIV_ADDR)
In uence the delivery address on item level by setting the
delivery address number.

You can change the following eld:


REFERENCEDELIVERYADDRESSID.

Use the optional importing parameter:


PURCHASEORDERITEM_OLD. This parameter contains the
item data of the previous roundtrip, for example, the data
before the last change was done.

Modify Purchase Order Schedule Line Data ( With this BAdI, you can
MM_PUR_S4_PO_MODIFY_SCHEDULE)
Implement own checks and raise messages by lling the
changing parameter table MESSAGES.

Make changes to the following elds:

SCHEDULELINEDELIVERYDATE,
PERFORMANCEPERIODSTARTDATE,
PERFOMANCEPERIODENDDATE,
SCHEDULELINEDELIVERYTIME

Modify Tax Jurisdiction Code of Purchase Order Item With this BAdI, you can
(MM_PUR_S4_PO_MODIFY_TAXJURCODE)
Determine the tax jurisdiction code in purchase order items
and use it, for example, on item level for tax calculation
purposes if the tax jurisdiction code is maintained in the
delivery address. In the standard, the system takes the
following sources into account for the jurisdiction code:
reference documents (RFQ, contract), plant table, manual
user input, account assignment object (if a tax jurisdiction
code is maintained here). In the process, the system
overwrites the previous value in this list in each case. If, for
example, you have maintained a tax jurisdiction code for a
purchase order item with account assignment object, this
entry wins over the entry in the plant table.

If you implement the BAdI


MM_PUR_S4_PO_MODIFY_TAXJURCODE and a purchase
order is created, the tax jurisdiction codes previously
determined by the system will be overwritten with the value
provided by the BAdI implementation.

The checks provided in the system (for example, whether


the combination of tax code and tax jurisdiction code in the
system is valid) continue to be run. If you implement the
BAdI you must ensure that a valid tax jurisdiction code is
returned. In addition to returning the tax jurisdiction code of
the delivery address, another option is to use an external
system for tax calculation purposes here. Manual input of
the tax jurisdiction code by the user is taken into account in
all cases.

Use the optional importing parameter:


PURCHASEORDERITEM_OLD. This parameter contains the
item data of the previous roundtrip, for example, the data
before the last change was done.

This is custom documentation. For more information, please visit the SAP Help Portal 58
10/12/2023

BAdI ID and Description Short Description

If you implement the BAdI


MM_PUR_S4_PO_MODIFY_TAXJURCODE the following data is
available to control the system behavior in determining the tax
jurisdiction code:

Purchasing document header (PURCHASEORDER)

Purchasing document item


(PURCHASEORDERITEM/PURCHASEORDERITEM_OLD) -
old and new status

Account assignment data for the item


(PURORDERACCTASSIGNMT_TABLE)

Tax jurisdiction code from plant table


(TAXJURISDICTION_PLANT)

Tax jurisdiction code from delivery address


(TAXJURISDICTION_DEL_ADDRESS)

In the example implementation supplied for BAdI


MM_PUR_S4_PO_MODIFY_TAXJURCODE the following system
behavior is de ned:

The tax jurisdiction code from the delivery address is set.

If no value is maintained in the delivery address: The value


for the jurisdiction code previously determined by the
system is inserted again.

For the country/region belonging to the plant/company code of the


purchase order item, tax handling with tax jurisdiction codes must
be activated.

Open Purchase Order (MM_PUR_S4_PO_OPEN) With this BAdI, you can

Put a purchase order in display mode and so prevent processing of


the purchase order.

PO Check All Items (MM_PUR_S4_PO_CHECK_ALL_ITEMS) With this BAdI, you can

Check the entire docurment.

Post Purchase Order (MM_PUR_S4_PO_POST) With this BAdI, you can

Post your own data.

Purchase Order Hold Allowed (MM_PUR_S4_PO_HOLD_ALLOWED) With this BAdI, you can

Specify if a purchase order can be put on hold.

 Note
If neither BAdI Modi cation of Purchase Order Header nor BAdI Modi cation of Purchase Order Item is implemented, the
custom elds will be open for input when creating or changing purchase orders and will be in read-only mode when displaying
purchase orders.

For more information see:

Custom Logic

For more information about the individual BAdIs, check the BAdI-speci c documentation: Custom Logic <your
implementation > BAdI Documentation View BAdI Documentation

This is custom documentation. For more information, please visit the SAP Help Portal 59
10/12/2023

Related Information
Custom Fields App and Custom Logic App
Key User Extensibility

App Extensibility: Create Purchase Order via Purchase


Requisition Assignment List
You can extend the Create Purchase Order via Purchase Requisition Assignment List app according to your business needs.

Features
Key users can extend the app in the Custom Fields app using the business context Procurement: Purchase Requisition Item.

You can enable usage of your custom elds for the data source Purchase Requisition Item GUI for purchase requisitions and for
the data source Purchase Order Item GUI for purchase orders in the UIs and Reports section of the custom eld maintenance
and publish your custom elds.

Key users can also make custom elds available in several apps including handing over data by using business scenarios. After
enabling the custom eld for a business scenario, the value of this eld will be copied between the corresponding documents.

For the business context Procurement: Purchase Requisition Item, the following business scenarios are available:

Purchase Requisition Item to Purchasing Document Item on item level

Business users can display elds that you have enabled in the Custom Fields app. The elds that you enable for this app are
included in the personalization options for business users for the following UI elements:

UI Element Business Context

Item Details Custom Fields Procurement: Purchase Requisition Item

Restrictions
The number of custom elds to be displayed in the Custom Fields section on either header or item level is limited to 170.

Related Information
Key User Extensibility
Custom Fields App and Custom Logic App

Extensibility for Purchase Contract Apps


You can extend the following classic apps according to your business needs:

Create Purchase Contract

Change Purchase Contract

Display Purchase Contract

This is custom documentation. For more information, please visit the SAP Help Portal 60
10/12/2023

Features
Key users can extend the apps using the following business contexts:

Procurement: Purchasing Document

Procurement: Purchasing Document Item

You can enable usage of your custom elds for the apps in the UIs and Reports section of the custom eld maintenance in the
Custom Fields app and publish your custom elds.

You can add elds to the following UI elements using UI adaptation at runtime:

UI Element Business Context

Custom Fields (Header Level) Procurement: Purchasing Document

Custom Fields (Item Level) Procurement: Purchasing Document Item

For more information about how to adapt an SAP Fiori UI at runtime, see Making UI Changes (Object Pages).

For the Create Purchase Contract app, you can implement logic for the following Business Add-Ins (BAdIs) in the Custom Logic
app:

Business Add-Ins (BAdIs) Business Context

Cloud BAdI for Contract Check Procurement: Purchasing Document

Cloud BAdI for Contract Check Procurement: Purchasing Document Item

Cloud BAdI for Contract Modify Header Procurement: Purchasing Document

Cloud BAdI for Contract Modify Item Procurement: Purchasing Document Item

The BAdI Cloud BAdI for Contract Check can be used to check or validate values of standard and custom elds in purchase
contracts.

The BAdI Cloud BAdI for Contract Modify Header can be used to set or change values of custom elds in purchase contracts on
header level.

The BAdI Cloud BAdI for Contract Modify Item can be used to set or change values of custom elds in purchase contracts on
item level.

If the BAdI Cloud BAdI for Contract Check is not implemented, the custom elds will be open for input when creating or
changing purchase contracts and will be in read-only mode when displaying purchase contracts.

Related Information
Custom Fields App and Custom Logic App
Key User Extensibility

Extensibility for Scheduling Agreement Apps


You can extend the following classic apps according to your business needs:

This is custom documentation. For more information, please visit the SAP Help Portal 61
10/12/2023
Create Scheduling Agreement

Change Scheduling Agreement

Features
Key users can extend the apps in the Custom Fields app using the following business contexts:

Procurement: Purchasing Document

Procurement: Purchasing Document Item

You can enable usage of your custom elds for the data sources Scheduling Agreement Header GUI Context and Scheduling
Agreement Item GUI Context in the UIs and Reports section of the custom eld maintenance and publish your custom elds.

Business users can display elds that you have enabled in the Custom Fields app. The elds that you enable for these apps are
included in the personalization options for business users for the following UI elements:

UI Element Business Context

Scheduling Agreement Header Details CUSTOM FIELDS Procurement: Purchasing Document

Scheduling Agreement Item Details CUSTOM FIELDS Procurement: Purchasing Document Item

Related Information
Custom Fields App and Custom Logic App
Key User Extensibility

Extensibility for Scheduling Agreement Delivery Schedule Apps


You can extend the following classic apps according to your business needs:

Manage SA Delivery Schedule

Display Scheduling Agreement Schedule

Features
Key users can extend the apps in the Custom Fields app using the following business contexts:

Procurement: Purchasing Document

Procurement: Purchasing Document Item

You can enable usage of your custom elds for the data sources Scheduling Agreement Header GUI Context, Scheduling
Agreement Item GUI Context, and Manage Scheduling Agreement in the UIs and Reports section of the custom eld
maintenance and publish your custom elds.

Business users can display elds that you have enabled in the Custom Fields app. The elds that you enable for these apps are
included in the personalization options for business users for the following UI elements:

UI Element Business Context

This is custom documentation. For more information, please visit the SAP Help Portal 62
10/12/2023

UI Element Business Context

Scheduling Agreement Header Statistics CUSTOM FIELDS Procurement: Purchasing Document

Scheduling Agreement Item Statistics CUSTOM FIELDS Procurement: Purchasing Document Item

Related Information
Custom Fields App and Custom Logic App
Key User Extensibility

App Extensibility: Manage Supplier Invoices

Use
You can extend the Manage Supplier Invoices app according to your business needs.

Features
Key users can extend the app in the Custom Fields app using the following business contexts:

Procurement: Supplier Invoice

Procurement: Supplier Invoice Item with Purchasing Document Ref. / Consignment

You have the following options:

Add additional elds to forms

Change the order of elds

Regroup and rename elds

Save the current layout

You can make settings to exclude elds.

You can add elds to the following UI elements:

UI Elements

UI Element Business Context

Manage Supplier Invoices (Header) Procurement: Supplier Invoice (MM_SI_HEADER)

Data source under UIs and Reports in Custom Fields app:


MM_SUPPLIER_INVOICE_MANAGE
 Note
The following eld types are not supported:

Code List based on CDS View

Association to Business Object

This is custom documentation. For more information, please visit the SAP Help Portal 63
10/12/2023

UI Element Business Context

Manage Supplier Invoices (Item screen for Invoice Item with Procurement: Supplier Invoice Item with Purchasing Document Ref.
Purchasing Document Reference) / Consignment (MM_SI_ITEM)

Data source under UIs and Reports in Custom Fields app:


MM_SUPPLIER_INVOICE_MANAGE
 Note
The following eld types are not supported:

Code List based on CDS View

Association to Business Object

More Information
For more information, see the UI help for Extensibility apps.

Related Information
Key User Extensibility
Custom Fields
Adapting UIs of Coding Block Reuse Components
Making UI Changes (Object Pages)

App Extensibility: Create Supplier Invoice - Advanced


You can extend the Create Supplier Invoice - Advanced app according to your business needs.

Features
Key users can extend the app in the Custom Fields app using the following business context:

Procurement: Supplier Invoice Header

In the Custom Fields app, you can enable usage of your custom elds for the data source SI_HEADER_GUI in the UIs and
Reports section of the custom eld maintenance and publish your custom elds.

 Note
If you link custom elds to the Create Supplier Invoice - Advanced app in the Custom Fields app, a separate tab on header
level contains your elds.

You can add elds to the following UI elements using UI adaptation at runtime:

UI Element Business Context

Custom Fields (Header Level) Procurement: Supplier Invoice Header (MM_SI_HEADER)

Related Information
Key User Extensibility
Custom Fields

This is custom documentation. For more information, please visit the SAP Help Portal 64
10/12/2023
Adapting UIs of SAP GUI Applications

App Extensibility: Supplier Invoices List

Use
You can extend the Supplier Invoices List app according to your business needs.

Features
Key users extend the app in the Custom Fields app using the following business context:

Procurement: Supplier Invoice

You have the following options:

Add previously created elds to the table

Change the order of elds

Rename elds

Save the current layout

You can make settings to exclude elds.

You can add elds to the following UI elements:

UI Elements

UI Element Business Context

Supplier Invoices List (Header) Procurement: Supplier Invoice (MM_SI_HEADER)

Data source under UIs and Reportsin Custom Fields app:


MM_SUPPLIER_INVOICE_LIST_ENH_SRV

More Information
For more information, see the UI help for Extensibility apps.

Related Information
Key User Extensibility
Custom Fields

App Extensibility: Display Supplier Invoice - Advanced


You can extend the Display Supplier Invoice - Advanced app according to your business needs.

Features
Key users can extend the app in the Custom Fields app using the following business context:

This is custom documentation. For more information, please visit the SAP Help Portal 65
10/12/2023
Procurement: Supplier Invoice Header

In the Custom Fields app, you can enable usage of your custom elds for the data source SI_HEADER_GUI in the UIs and
Reports section of the custom eld maintenance and publish your custom elds.

 Note
If you link your custom elds to the Display Supplier Invoice - Advanced app, a separate tab on header level contains your
elds.

You can add elds to the following UI elements using UI adaptation at runtime:

UI Element Business Context

Custom Fields (Header Level) Procurement: Supplier Invoice Header (MM_SI_HEADER)

Related Information
Key User Extensibility
Custom Fields
Adapting UIs of SAP GUI Applications

Process Extensibility for Documents in Procurement


You can extend the following apps according to your business needs:

Manage Purchase Orders

Create Purchase Order - Advanced

Change Purchase Order - Advanced

Create Purchase Order via Purchase Requisition

Features
You can make custom elds available in several apps including handing over data by using business scenarios. After enabling the
extension eld for a business scenario, the value of this eld will be copied between the corresponding documents.

For the business context Procurement: Purchasing Document, the following business scenarios are available:

Purchase Order to Delivery on header level

For the business context Procurement: Purchasing Document Item, the following business scenarios are available:

Purchase Order to Delivery on item level

For the business context Procurement: Purchase Requisition Item, the following business scenarios are available:

Purchase Requisition Item to Purchasing Document Header

Purchase Requisition Item to Purchasing Document Item

Restrictions
This is custom documentation. For more information, please visit the SAP Help Portal 66
10/12/2023
The number of extension elds to be displayed in the Custom Fields section of the purchasing document on either header or
item level is limited to 170.

Related Information
Custom Fields App and Custom Logic App
Key User Extensibility
Process Extensibility for Delivery Documents

Extensibility for Adobe Output Forms of Documents in


Procurement

Use
You can extend the Adobe ® output forms of the following documents according to your business needs:

ERS and Invoicing Plan Settlement

Invoice Veri cation Complaint

Scheduling Agreement Form

Form Template Purchase Contract

Form Template Purchase Order

Features
Key users can extend the custom form templates (that is, copies of the predelivered form templates) in the Adobe LiveCycle
Designer® with custom elds created in the Custom Fields app for the following business contexts:

Form Template Business Context

ERS and Invoicing Plan Settlement Procurement: Supplier Invoice

ERS and Invoicing Plan Settlement Procurement: Supplier Invoice Item with Purchase Order Ref.

Invoice Veri cation Complaint Procurement: Supplier Invoice

Invoice Veri cation Complaint Procurement: Supplier Invoice Item with Purchase Order Ref.

Scheduling Agreement Form Procurement: Purchasing Document

Scheduling Agreement Form Procurement: Purchasing Document Item

Form Template Purchase Contract Procurement: Purchasing Document

Form Template Purchase Contract Procurement: Purchasing Document Item

Form Template Purchase Order Procurement: Purchasing Document

Form Template Purchase Order Procurement: Purchasing Document Item

After enabling usage of the custom elds for the respective form templates in the Form Templates section in the custom eld
maintenance of the Custom Fields app, you can publish your custom elds.

This is custom documentation. For more information, please visit the SAP Help Portal 67
10/12/2023

More Information
For more information about how to edit form layouts with the Adobe LiveCycle Designer®, see https://help.sap.com/ SAP
NetWeaver 7.5 UI Technologies in SAP NetWeaver SAP Interactive Forms by Adobe Enabling Form-Based Processing of
Business Data Providing Output Forms and Interactive Offline Forms De ning Form Templates De ning the Layout of a
Form Template Creating Layouts with Adobe LiveCycle Designer .

Related Information
Custom Fields App and Custom Logic App
Key User Extensibility
Maintain Form Templates

Extensibility for Search Models in Procurement


Extend search models using the Custom Fields app.

The enterprise search for speci c business object data can be accessed directly from the Fiori launchpad in a simple-to-use
search function. The searches allow you to get an overview of the business object data, navigate to additional information, and
navigate to apps with additional functions. As a key user, you can use the Custom Fields app to extend search models according
to your business needs.

The following table contains the business contexts under which you can enable the respective search model for your custom
elds in the Custom Fields app. You con gure your custom elds for the respective search model in the Manage Search Model
app:

Business Context Search Model User Interfaces

Procurement: Supplier Invoice Supplier Invoices Extension for ESH_S_INC_INVOICE (


(MM_SI_HEADER) ESH_S_INC_INVOICE)

Procurement: Awarding Scenario Awarding Scenarios Extension for


(MM_PUR_SRCGPROJAWD_HEADER) ESH_S_SRCGPROJAWARDINGSCENARIO
(E_SRCGPROJECTAWARDINGSCENARIO)

For information about how to extend an business object search by your own elds, see the following:

Manage Search Models

Custom Fields App and Custom Logic App and Custom Fields

Key User Extensibility

This is custom documentation. For more information, please visit the SAP Help Portal 68

You might also like