Ansicht
Dokumentation

Business Add-Ins (Changed) ( RELNEBP_50_BADI )

BAL_S_LOG - Application Log: Log header data   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Short text

Business Add-Ins (Changed)

Use

SAP Enterprise Buyer Release 5.0 provides a whole range of new BAdIs.

You can find the BAdIs and BAdI documentation in the Implementation Guide for Supplier Relationship Management -> SRM Server-> Business Add-Ins (BAdIs).

The following new BAdIs are available in the IMG structure:

• Archive SRM Documents
  You can use this BAdI to override the standard settings for archiving.

• Upload/Download SRM Documents
  You can use this BAdI to select document data for uploading and downloading, and to arrange this data in the file that you wish to upload or download.

• Further Authorization Check for SRM Documents
  You can use this BAdI to set up additional authorization checks if the standard checks do not fully meet your needs.

• Activation of Vendor Monitor
  You can use this BAdI to monitor how changes to vendor data in Enterprise Buyer are updated if they are relevant to the R/3 back-end system. The changes are actually updated in the Vendor Monitor transaction.

• Create Skills Profile
  You can use this BAdI to specify the individual skills that users can select when they create a skills profile for requesting third-party services. You can also specify in which situations it is possible to create a skills profile.

• Shopping Carts and Requirement Items -> Change Display in Shopping Cart
  You can use this BAdI to override the standard settings for the Wizard, Simplified Form, and Extended Form interfaces, and to customize them to meet your requirements.

• Bid Invitation -> Determine Bid Invitation Transaction Type
  You can use this BAdI to determine the transaction type of bid invitations for external staff or services. You can only call this BAdI as part of the process for requesting external staff or services, and not for specifying the transaction type of a bid invitation.

• Bid Invitation -> Control for Collaboration Folders
  You can use this BAdI to specify that, in addition to the standard settings and functions for Collaboration Folders, the system should also run customer-specific functions. For example, you can influence how authorizations are assigned.

• SAP Business Workflow -> Permit Approver Changes
  You can use this BAdI to specify whether or not it is possible to create and change approvers in the workflow approval preview.

• SAP Business Workflow -> Select Users when Creating/Changing Approvers
  You can use this BAdI to implement a method for determining at runtime which users can be selected when you change/add approvers in the workflow approval preview.

• Customer Fields -> Customer Field Control
  You can use this BAdI to specify that the system should use customer-specific dynamic programs for displaying customer fields instead of the standard display.

• Customer Fields -> Customer Fields with Standard Table Control
  You can use this BAdI to override the standard system reaction for displaying and changing customer fields.

• SAP XML Interfaces -> Change SAP XML Inbound Mapping
  You can use this BAdI to override the standard settings for mapping from an SAP XML interface to internal SRM structures (for example, to write data to customer fields). If the customer fields in the SRM structure have the same names as the fields in the SAP XML message, you do not need to use this BAdI.

• SAP XML Interfaces -> Change SAP XML Outbound Mapping
  You can use this BAdI to override the standard settings for mapping frominternal SRM structures to SAP XML outbound interfaces (for example, to write data to customer fields). If the customer fields in the SRM structure have the same names as the fields in the SAP XML message, you do not need to use this BAdI.

• Document Output -> Output Shopping Cart with Customer Form
  You can use this BAdI to specify which form the system should use instead of the standard form for printing out the shopping cart.

• Document Output -> Output Contract with Customer Form
  You can use this BAdI to specify which form the system should use instead of the standard form for outputting contracts.

• Document Output -> Print Preview for Comparison of Purchase Order Versions
  You can use this BAdI to specify which form the system should use instead of the standard form for displaying the print preview for purchase order version comparisons.

The following BAdIs were moved within the IMG for SAP Enterprise Buyer Release 4.0:

• The BAdI Change Smart Form for E-Mails Relating to Bids has now been moved to the node entitled Document Output.

The following BAdIs have either been deleted for SAP Enterprise Buyer 5.0, or have been removed from the IMG structure:

• Pricing -> Product Master Maintenance: Switch Off Buffer Refreshin IPC

• Direct Material and Plan-Driven Procurement -> Check Items for APO Relevance

The following BAdIs have been changed for Enterprise Buyer Release 5.0

• The BAdI (Follow-On Document Generation in the Backend System -> ) Determine Number Ranges and Groupings in Backend Documents now contains an extra method that you can use to specify whether you wish to make another grouping after you have made the standard grouping for purchase orders.

• The BAdIs (Follow-On Document Generation in the Backend System -> ) Purchase Order in Backend System and Reservation in Backend System now have extra parameters for transferring attachments to the backend system.

• The BAdI (Sourcing -> ) Find and Check Sources of Supply now has extra parameters where you can specify whether or not the system should ignore secondary criteria for sourcing, and whether or not the system should output extra customer-specific messages in the sourcing application.

Effects on Existing Data

Effects on Data Transfer

Effects on System Administration

Effects on Customizing

Further Information

Release Note Changes in the IMG Structure for SRM Server

CPI1466 during Backup   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 8700 Date: 20240520 Time: 224153     sap01-206 ( 115 ms )