Вы находитесь на странице: 1из 11

BAdI for Sending Licenses

Use
You can use the Business Add-In (BAdI) for the dispatch of licenses in the following areas of SAP Global Trade Services (SAP
GTS), where the license technical object models several different business objects:

Import/export licenses in SAP Compliance Management

Securities for transit procedures and import customs processing in SAP Customs Management

Authorizations in SAP Customs Management

Securities and export licenses in SAP Risk Management - Restitution

Letters of credit in SAP Risk Management - Letter of Credit Processing

The BAdI lets you use data from the licenses and prepare them for dispatch, because the licenses are integrated with the Post
Processing Framework, and the BAdI is called in this context. You set up your customer-specific communication with external
systems, to dispatch electronic messages, in this BAdI. SAP does not provide any programs for establishing communicator or
sending license data at this juncture. Depending on which form of electronic communication you want to set up for licenses, you
can configure any further processing of the license data provided in this BAdI.
You configure the dependent settings of the PPF actions for sending licenses in the following activities:

Define Technical Medium for Messages (PFF Actions) of Licenses

Define Condition/Output Parameter for Communication of Licenses

Standard settings
In the standard system, there is no activated BAdI implementation.
The BAdI is designed for a single use. The activated implementation is called and executed.
The BAdI is filter-independent.
Activities
See also
The BAdI uses interface /SAPSLL/EX_IF_ECMC_OUT. For more information, display the interface in the Class Builder.

BAdI for Processing Inbound Licenses


Use
You can use the Business Add-In (BAdI) for the inbound processing of licenses in the following areas of SAP Global Trade
Services (SAP GTS), where the license technical object models several different business object:

Import/export licenses in SAP Compliance Management

Securities for transit procedures and import customs processing in SAP Customs Management

Authorizations in SAP Customs Management

Securities and export licenses in SAP Risk Management - Restitution

Letters of credit in SAP Risk Management - Letter of Credit Processing

This BAdI enables you to take the received license data and convert it to the defined structure for saving licenses in the
database. Because you can use various types of electronic communication for transmitting licenses, each of which has a
different technical format, you have to convert all data into the required format for further processing in the system.
To make this possible, you have to receive the data from the inbound licenses in your own programs. You also have to include a
call of RFC module /SAPSLL/LCLIC_ECMS_IN_PRF in these programs, so the system calls the BAdI to map the received data
to the data format for saving the licenses.
Requirements

In the standard system, there is no activated BAdI implementation.

The BAdI is designed for a single use. The activated implementation is called and executed.

The BAdI is filter-independent.

Activities
For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under
BAdIs - Embedding in the Enhancement Framework.
See also
The BAdI uses interface /SAPSLL/EX_IF_ECMC_IN. For more information, display the interface in the Class Builder.
If you want to use electronic communication for inbound licenses, you can configure an e-mail notification to send to a fixed user
group when a license is received. You configure the settings for this notification in the respective IMG activities for defining the
different license types - for example, define types of security or define types of licenses.

BAdI to Create Notification Texts upon License Receipt


Use
This Business Add-In (BAdI) is used in the SLL-LEG component for SAP Global Trade Services (SAP GTS).
This BAdI lets you enter a text and a subject line for the e-mail that the system sends to a defined group of users as a
notification as soon as the system receives a license via electronic communication. To improve clarity, you can add data from the
received license to the e-mail text or the subject line.
Requirements

You have implemented the BAdI for Processing Inbound Licenses.

You have configured the settings for electronic communication for the desired license types. You can configure these
settings for the following license types:
o

Types of import and export licenses

Types of security for the transit procedure and import customs processing

Types of authorizations for the transit procedure, customs processing, the bonded warehouse procedure,
and inward processing

Types of export licenses

Types of security for restitution

Types of letters of credit

Standard settings

In the standard system, there is no activated BAdI implementation.

The BAdI is designed for a single use. The activated implementation is called and executed.

The BAdI is filter-independent.

Activities
For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under
BAdIs - Embedding in the Enhancement Framework.
See also
The BAdI uses interface /SAPSLL/EX_IF_ECMC_IN_EMAIL. For more information, display the interface in the Class Builder.

BAdI: Retransfer Commodity Codes to Feeder Systems


Use
This Business Add-In (BAdI) for alternative retransfer of commodity codes to the feeder system is used in the SAP Customs
Management and SAP Risk Management - Preference Processing areas of SAP Global Trade Services (SAP GTS).
The BAdI lets you integrate your own objects, such as function modules, with which you save the commodity codes in the
relevant places in your feeder system and derive their processing - assuming you do not want the system to save this
information directly in the material master, in the plant data for the material. You can also use the BAdI as a filter to fill the
standard worklist.
Standard settings

In the standard system, there is no activated BAdI implementation.

The BAdI is designed for multiple use. All activated implementations are called and executed.

The BAdI is filter-independent.

Activities
For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under
BAdIs - Embedding in the Enhancement Framework.
See also
The BAdI uses interface /SAPSLL/IF_STAWN_RETRANSFER_R3. For more information, display the interface in the Class
Builder.

BAdI: Business Partner: Prepare Bank Data for Checks

Use
This BAdI allows enhancements to the business partner function in the SAP Global Trade Services area.

BAdI: Business Partner Transfer: Buffer General HCM Data


Use
You can use Business Add-In BUPA_GENERAL_EXPORT to edit the general data of a changed business partner object.
If you use the transfer of HCM master data to SAP Global Trade Services, you should activate the standard implementation of
this BAdI, /SAPSLL/BP_HR_GEN. It lets you buffer the general data for a business partner in the system.
Requirements
Standard Settings
This Business Add-In is an internal SAP BAdI and is not active.
Activities
To activate the standard implementation of this BAdI, run this IMG activity.
Note: In a dialog, the system asks you whether you want to activate the implementation of the BAdI. If you already activated the
implementation at an earlier point in time, the system asks whether you want to deactivate it.
Example

BAdI: Business Partner Transfer: Buffer HCM Bank Data


Use
You can use Business Add-In BUPA_BANK_EXPORT to edit the bank data of a changed business partner object.
If you use the transfer of HCM master data to SAP Global Trade Services, you should activate the standard implementation of
this BAdI, /SAPSLL/BP_HR_BANK. It lets you buffer the bank data for a business partner in the system.
Requirements
Standard Settings
This Business Add-In is an internal SAP BAdI and is not active.
Activities
To activate the standard implementation of this BAdI, run this IMG activity
Note: In a dialog, the system asks you whether you want to activate the implementation of the BAdI for transfers. If you already
activated the implementation at an earlier point in time, the system asks whether you want to deactivate it.
Example

BAdI: Business Partner Transfer: Buffer HCM Partner Roles


Use

You can use Business Add-In BUPA_ROLES_EXPORT to edit the partner roles of a changed business partner object.
If you use the transfer of HCM master data to SAP Global Trade Services, you should activate the standard implementation of
this BAdI, /SAPSLL/BP_HR_ROLES. It lets you buffer the partner roles for a business partner in the system.
Requirements
Standard Settings
This Business Add-In is an internal SAP BAdI and is not active.
Activities
To activate the standard implementation of this BAdI, run this IMG activity.
Note: In a dialog, the system asks you whether you want to activate the implementation of the BAdI. If you already activated the
implementation at an earlier point in time, the system asks whether you want to deactivate it.
Example

BAdI: Business Partner Transfer: HRALE Distribution for IDoc


Use
Business Add-In HRALE00INBOUND_IDOC lets you edit the IDocs of an HRALE distribution.
If you use the transfer of HCM master data to SAP Global Trade Services, you should activate the standard implementation of
this BAdI, /SAPSLL/BP_HR_IDOC.
Requirements
Standard Settings
This Business Add-In is an internal SAP BAdI and is not active.
Activities
To activate the standard implementation of this BAdI, run this IMG activity.
Note: In a dialog, the system asks you whether you want to activate the implementation of the BAdI. If you already activated the
implementation at an earlier point in time, the system asks whether you want to deactivate it.
Example

BAdI: Business Partner Transfer: HRALE Distribution for Info


Use
Business Add-In HRBAS00INFTY lets you edit the infotypes of an HRALE distribution.
If you use the transfer of HCM master data to SAP Global Trade Services, you should activate the standard implementation of
this BAdI, /SAPSLL/BP_HR_INFTY.
Requirements

Standard Settings
This Business Add-In is an internal SAP BAdI and is not active.
Activities
To activate the standard implementation of this BAdI, run this IMG activity.
Note: In a dialog, the system asks you whether you want to activate the implementation of the BAdI. If you already activated the
implementation at an earlier point in time, the system asks whether you want to deactivate it.
Example

BAdI for Additional Criteria for Archiving Relevance of Prod


Use
The Business Add-In (BAdI) for archiving products is used in all areas of the system for Global Trade Services (GTS).
This BAdI lets you exclude products from subsequent archiving, although the system has flagged them as relevant for archiving
in the preparation for archiving program. Accordingly, if you run this BAdI before the archiving run, the system will not archive
the flagged products.
Under the default settings, the system flags all products as relevant for archiving for which the GTS system no longer has any
stocks and that occur only in documents that you have already archived. The archive-relevant products must not be used in
active documents.
If you want to define additional criteria for the system to flag products as relevant for archiving, you can implement the checks for
these criteria in this BAdI. This makes it possible, for example, to flag products that have already been archived in the feeder
system as relevant for archiving in the GTS system.
Note that this BAdI only enables you to define and check additional criteria for archivability.
Standard settings

In the standard system, there is no activated BAdI implementation.

The BAdI is intended for multiple use. All activated implementations are called and executed.

The BAdI is filter independent.

Activities
For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under
BAdIs - Embedding in the Enhancement Framework.
See also
The BAdI uses interface /SAPSLL/IF_BADI_PR_ARCHV_CHCK. For more information, display the interface in the Class
Builder.

TRANSFER EXTERNAL DATA TO CUSTOMS PRODUCT

BAdI to Map External Product Data to Customs Product

Use
The Business Add-In (BAdI) for assigning external data to the customs product master is used in SAP GRC Global Trade
Services.
The BAdI lets you transfer external data to the customs product master during the transfer of materials from the feeder system.
Standard settings

In the standard system, there is no activated BAdI implementation.

The BAdI is designed for multiple use. All activated implementations are called and executed.

The BAdI is filter-independent.

Activities
For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under
BAdIs - Embedding in the Enhancement Framework.
See also
The BAdI uses interface /SAPSLL/IF_BADI_IFMAP_PRD.
For more information, display the interface in the Class Builder.

BAdI to Map Partner-Specific External Product Data to Custom


Use
This Business Add-In (BAdI), which maps external product-related data to information in the customs product master, is used in
the SAP Customs Management area of SAP GRC Global Trade Services.
The BAdI lets you transfer the external data representing your business partners' material names to the customs product master
during the transfer of materials from the feeder system.
Standard settings

In the standard system, there is no activated BAdI implementation.

The BAdI is designed for multiple use. All activated implementations are called and executed.

The BAdI is filter-independent.

Activities
For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under
BAdIs - Embedding in the Enhancement Framework.
See also
The BAdI uses interface /SAPSLL/IF_BADI_IFMAP_PRPAR. For more information, display the interface in the Class Builder.
DISPLAY EXTERNAL DATA IN CUSTOMS PRODUCT MASTER

BAdI for UI Control for Integration of External Applications


Use

The Business Add-In (BAdI) is used for UI control to integrate external applications with the customs product master in SAP
GRC Global Trade Services.
The BAdI lets you display custom screens with data from external applications in the corresponding tab pages in the customs
product master. You can activate up to three tab pages with the corresponding implementations. You can use data from the
external applications to fill specific form fields in printed documents, for example, or for foreign trade analyses based on master
data based on the external applications. You can save the separate data outside of the standard structure for the customs
product master, yet still use it during product processing.
Standard settings

In the standard system, there is no activated BAdI implementation.

The BAdI is designed for multiple use. You can have up to three active implementations, each of which lets you display
a custom tab page in the customs product master. All activated implementations (up to the maximum of three at each
level) are called and executed.

The BAdI is filter-independent.

Activities
For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under
BAdIs - Embedding in the Enhancement Framework.
See also
The BAdI uses interface /SAPSLL/IF_BADI_EXT_UI_PRD. For more information, display the interface in the Class Builder.

BAdI for Saving Data from External Applications in Customer


Use
This Business Add-In (BAdI) is used to integrate external data with the customs product master in SAP GRC Global Trade
Services.
If you integrate external applications in custom tab pages of the customs product master and create or change this data there,
this BAdI lets you update the data in customer tables. If you want to update this data in customer append structures to the
customs product object, you do not need to use this BAdI.
Standard settings

In the standard system, there is no activated BAdI implementation.

The BAdI is designed for multiple use. All activated implementations are called and executed.

The BAdI is filter-independent.

Activities
For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under
BAdIs - Embedding in the Enhancement Framework.
See also
The BAdI uses interface /SAPSLL/IF_BADI_EXT_PRD.
For more information, display the interface in the Class Builder.

BADIS IN CASE MANAGEMENT

BAdI to Determine Process Routes in Case Management


Use
This Business Add-In (BAdI), which lets you use alternative process use models in Case Management, is used in the following
areas of SAP GRC Global Trade Services:

Releasing blocked business partners after SPL screening

Product classification in Customs Management and Compliance Management

Release of customs documents blocked due to blocked business partners, an embargo situation, or a missing license
for a product that requires a license

If you use Case Management for the above areas, you can use this BAdI to define which process use model is used to
determine the next responsible person in a decision case involving a document release, a partner release, or product
classification. In the standard settings, the system determines the process use model for case processing from your default data
settings in Case Management. If you want to use alternative process use models, you can configure this BAdI to do so.
Requirements
You have defined the process use models that the BAdI can determine as alternative process use models in Customizing for
process use models, under Cross-Application Components -> General Application Functions -> Records and Case Management
-> Case -> Process Route.
Standard settings

In the standard system, there is no activated BAdI implementation.

The BAdI is designed for multiple use. All activated implementations are called and executed.

The BAdI is filter-independent.

Activities
For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under
BAdIs - Embedding in the Enhancement Framework.
See also
The BAdI uses interface /SAPSLL/IF_CASE_ROUTE_GET. For more information, display the interface in the Class Builder.

BAdI to Determine the Case Type in Case Management


Use
This Business Add-In (BAdI), which lets you an alternative case type in Case Management, is used in the following areas of SAP
GRC Global Trade Services:

Releasing blocked business partners after SPL screening

Product classification in Customs Management and Compliance Management

Release of customs documents blocked due to blocked business partners, an embargo situation, or a missing license
for a product that requires a license

If you use Case Management for the above areas, you can use this BAdI to define which case type is used in a decision case
involving a document release, a partner release, or product classification. You have assigned general properties to each case
type in Customizing, such as different authorization profiles for each case type. In the standard settings, the system determines
the case type from your default data settings in Case Management. If you want to use more parameters to determine the case
type dependent on the assigned authorizations, you can use this BAdI to determine these parameters.
Requirements
You have defined the case types that the BAdI can determine as alternative case types in Customizing for case types, under
Cross-Application Components -> General Application Functions -> Records and Case Management -> Case -> Case Type.
Standard settings

In the standard system, there is no activated BAdI implementation.

The BAdI is designed for multiple use. All activated implementations are called and executed.

The BAdI is filter-independent.

Activities
For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under
BAdIs - Embedding in the Enhancement Framework.
See also
The BAdI uses interface /SAPSLL/IF_CASE_TYPE_GET. For more information, display the interface in the Class Builder.
AUTHORIZATION MANAGEMENT

Define Authorization Groups for Web Dynpro Application


Use
In this Customizing activity, you can define authorization groups for the Web Dynpro applications. These authorization groups
enable you to group different programs together for common authorization checks. You assign the authorization groups and
programs in the Customizing activity Assign Authorization Groups for Web Dynpro Application to Program Objects.
Activities
Define a name and description of each authorization group.

Assign Authorization Groups for Web Dynpro Application to Pr


Use
In this Customizing activity, you assign the authorization groups for Web Dynpro applications to the program objects in the
standard application.
Requirements
You have already performed the Customizing activity Define Authorization Groups for Web Dynpro Application.

Define Authorizations
Use
Define authorizations and roles
The following roles are relevant in the area of SAP Compliance Management:
/SAPSLL/LEG_ARCH GTS: Archiving
/SAPSLL/LEG_LCE_APP GTS: Legal control export: Specialist
/SAPSLL/LEG_LCI_APP GTS: Legal control import: Specialist
/SAPSLL/LEG_SPL_APP GTS: Sanctioned party list: Specialist
/SAPSLL/LEG_SYS_COMM GTS: (Technical) system communication